# What Is AI Referral Traffic? How to See It in GA4

> What AI referral traffic is, how Google Analytics groups it in its AI Assistant channel, which visits go missing and why AI bots are not visits.

URL: https://clione.ai/glossary/ai-referral-traffic/
Lang: en

"AI traffic" gets used for two things that are worth separating from the start. One is **the people who reach your store from an assistant's answer**: someone asks ChatGPT which backpack to buy, sees a link to your [product page](/glossary/product-page/) and clicks it. The other is the bots from AI companies that request your pages to read them, index them or answer a question, and leave their trace in the server logs. This entry is about the first, referral traffic; the second belongs to the [crawler](/glossary/web-crawler/) and to each agent. For a store, AI referral traffic is **the part of its presence in answers that turns into a visit it can see**.

## How it works

Your analytics does not know where a visit came from: it infers it. For AI referral traffic there are two clues, and either can be missing.

**The referrer.** When someone clicks a link, the browser can send the address it came from in the `Referer` header. With the default policy, on a hop between two HTTPS sites only the origin is sent, the domain without the path; with the `no-referrer` policy, or with a link marked `rel="noreferrer"`, nothing is sent.[^mdn-referrer-policy] At best, your store knows which assistant the visit came from, never which conversation.

**The channel.** Since May 13, 2026, Google Analytics has a channel of its own for these visits. When the referrer matches an AI assistant it recognizes, it assigns the visit the medium `ai-assistant` and the campaign `(ai-assistant)`, and groups it in the **AI Assistant** channel; Google gives ChatGPT, [Gemini](/glossary/gemini/) and Claude as examples.[^ga4-whats-new] The channel definition in its help also names Deepseek, [Copilot](/glossary/copilot/) and Grok.[^ga4-channels] On June 11, 2026 it also added a source group field that, among other things, groups the different source values of sources like ChatGPT (OpenAI) and [Perplexity](/glossary/perplexity/).[^ga4-whats-new]

**What falls outside the channel.** The AI Assistant channel **expressly excludes [AI Overviews](/glossary/ai-overviews/) and [AI Mode](/glossary/google-ai-mode/)**, which Google Analytics counts as organic search.[^ga4-channels] In [Search Console](/glossary/google-search-console/), clicks from those two features are also mixed in with the rest, inside the web search type of the performance report.[^google-ai-features] And a visit that arrives with no referrer and no campaign tags ends up as `(direct) / (none)`, the traffic that, according to Google, has no clear referral source; among the causes it lists are links without `utm_` parameters, redirects that strip them, link shorteners and ad blockers.[^ga4-direct]

**What is not AI referral traffic.** The agents of AI companies also visit your site, but they are not customers. OpenAI uses [ChatGPT-User](/glossary/chatgpt-user/) for some actions a person starts in ChatGPT, and warns that [`robots.txt`](/glossary/robots-txt/) rules may not apply to those requests.[^openai-bots] Perplexity-User visits a page when someone asks Perplexity something, to answer and maybe link it, and generally ignores `robots.txt`.[^perplexity-bots] Those requests are identified by their own [_user agent_](/glossary/user-agent/) and are read in the server logs. Google Analytics, for its part, **automatically excludes known bot traffic**, using its own list and the IAB's, with no option to turn it off and no way to see how much it excluded.[^ga4-bots]

For all those reasons, **AI referral traffic has no standard definition**. The AI Assistant channel is Google Analytics' definition, with its list of assistants and its exclusions; another analytics tool may count other sources, and none of them sees the visits that arrive without a trace.

## In a store

Five ways an AI answer can bring someone, or something, to the same product page of a backpack store, and where each one ends up. It is a **fictional example**: the domains are made up, and the result in each row follows Google Analytics' published rules.[^ga4-channels][^ga4-direct]

| What happens (fictional example)                            | What the store receives                   | Where Google Analytics counts it              |
| ----------------------------------------------------------- | ----------------------------------------- | --------------------------------------------- |
| Click on a cited link in an assistant that sends a referrer | `Referer: https://example-assistant.com/` | AI Assistant, if the assistant is on its list |
| Click on a link in an AI Overview                           | A Google referrer                         | Organic Search                                |
| Click from an app that sends no referrer                    | Nothing                                   | Direct                                        |
| Reads the recommendation, then searches the brand on Google | A Google referrer                         | Organic Search                                |
| An agent requests the page to answer a question             | A request with the agent's _user agent_   | No channel: it is a bot                       |


Only the first row ends up in the AI Assistant channel, and all five start in an AI answer. That is why the channel's figure is **a minimum, not the total**. The last row, by contrast, should never be added in: it is a machine reading the page, even if a person asking a question stands behind it.


**Visits from AI bots are not AI referral traffic.** Seeing thousands of requests from OpenAI or Perplexity agents in the server logs does not mean thousands of people came from ChatGPT: those agents request the page to read it or to answer a question.[^openai-bots][^perplexity-bots] The people who click a link afterward are counted in your analytics, and Google Analytics leaves known bot traffic out on its own.[^ga4-bots]


## How to check it

1. **Open traffic acquisition in Google Analytics by default channel group** and find the AI Assistant row, with dates after May 13, 2026.[^ga4-whats-new]
2. **Break it down by source** to see which assistants the visits come from, and by landing page to see which product pages get that traffic.[^ga4-whats-new]
3. **For Google's AI, go to Search Console**: clicks from AI Overviews and AI Mode are in the performance report, inside the web search type.[^google-ai-features] The [generative AI performance report](/glossary/generative-ai-performance-report/) gives their impressions, not their clicks.
4. **Separate the bots in the server logs.** Filter by the _user agents_ each company documents, such as ChatGPT-User or Perplexity-User, and verify the IPs: Perplexity publishes its ranges as JSON files.[^openai-bots][^perplexity-bots] Those lines are not customer visits.
5. **Look at which deep product pages get a lot of direct traffic.** A long URL nobody would type by hand is a clue of lost referrers, not proof.[^ga4-direct]

## Related concept: LLM attribution

AI referral traffic counts visits; [attribution](/glossary/llm-attribution/) takes the next step: it ties those visits to the orders they produce and says honestly which part cannot be attributed. You can have hundreds of visits from assistants and no orders, or orders that started in an AI answer and arrived as direct. **Traffic says how many arrive; attribution says what they buy and what you cannot see.** And before both comes [AI visibility](/glossary/ai-visibility/): whether you show up in the answers in the first place.

To keep going, the [measurement and verification reading path](/learn/measurement-and-verification/) orders the rest of the terms, and the entry on [assisted conversion](/glossary/assisted-conversion/) explains how credit is split when a sale passes through several channels.