Definition
AI referral trafficAI referral traffic is website visits that arrive when someone clicks a link inside an AI-generated answer, such as a cited source in ChatGPT, Perplexity, Gemini, Claude, or Microsoft Copilot. Analytics tools identify it by the referring domain or by a UTM tag, like the utm_source=chatgpt.com parameter ChatGPT adds to its links.
How AI referral traffic works
When an AI engine answers with live web results, it usually links the sources it drew on. Perplexity numbers them beside the answer, and ChatGPT shows them inline and in a sources panel. Gemini, Claude, and Microsoft Copilot link sources in their own ways.
A click on one of those links sends a visitor to your site, and your analytics tool can tell it came from AI in two ways:
- The referring domain. The browser passes along the address the visitor came from, such as chatgpt.com or perplexity.ai.
- A UTM parameter. ChatGPT adds
utm_source=chatgpt.comto the links it cites (OpenAI's publisher FAQ says so), so the source survives even when the referrer is stripped.
Every AI referral starts with a citation. A brand mentioned without a link can still influence the reader, but it can't send a visit you can track.
How to find AI referral traffic in GA4
In May 2026 Google added an AI Assistant channel to GA4's default channel group. When a session's referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant and files the visit under that channel. Google's documentation names ChatGPT, Gemini, DeepSeek, Copilot, and Grok as examples. To see it:
- Go to Reports → Acquisition → Traffic acquisition.
- Look for the AI Assistant row in the default channel group view.
- Switch the dimension to Session source to split it by engine.
Two gaps remain. The channel isn't retroactive, so visits from before the change still sit under Referral. And the documentation's examples don't include every tool your audience uses, so check Session source for these domains too:
| AI engine | Source to look for |
|---|---|
| ChatGPT | chatgpt.com (older links: chat.openai.com) |
| Perplexity | perplexity.ai |
| Gemini | gemini.google.com |
| Claude | claude.ai |
| Microsoft Copilot | copilot.microsoft.com |
If a source you care about isn't landing in AI Assistant, build a custom channel group under Admin → Data display → Channel groups. GA4 assigns each session to the first channel it matches, so put your AI channel above Referral or those visits get classified as ordinary referrals.
Why AI referral traffic is undercounted
The number in GA4 is a floor. Most of the gap comes from these:
- Lost referrers. Some clicks from AI apps arrive without a referrer, and without a UTM tag they land in Direct.
- Delayed visits. Plenty of people read a recommendation in an AI answer, open a new tab, and search for the brand by name. That visit shows up as branded organic search or direct traffic, with nothing tying it back to the answer.
- Google's AI surfaces. Clicks from AI Overviews and AI Mode come through as Google organic traffic, and GA4's AI Assistant channel leaves them out. Search Console reports them inside its overall Web totals with no separate filter.
On top of that, many AI answers get read with no click at all, which is why zero-click search matters for AI visibility. Track referral traffic next to your AI visibility score and brand mentions, since visibility can grow for months before referrals move.
AI referral traffic vs AI crawler traffic
The two get confused because both involve AI companies reaching your site.
| AI referral traffic | AI crawler traffic | |
|---|---|---|
| Who visits | A person who clicked a link in an AI answer | A bot, such as GPTBot, ClaudeBot, or PerplexityBot |
| Where you see it | GA4 and other analytics tools | Server logs or a crawler analytics tool |
| What it tells you | Whether AI answers send you visitors | Whether AI systems can read your pages |
AI crawlers generally don't run JavaScript analytics tags, so GA4 never sees them. You need both views to know whether AI crawlers are reading your pages and whether that reading turns into visits.
Why AI referral traffic matters
AI referral traffic is usually small next to organic search. It's worth tracking anyway, because these visitors show up after an AI engine has already compared the options and pointed them to you, so they tend to be further into their research than someone clicking a generic search result.
That changes how you judge the channel. Look at value per visit, such as demo requests or revenue from AI-referred sessions, instead of raw session counts. The landing pages that receive AI referrals are worth a look too, because they're the pages AI engines trust enough to cite.
How to track AI referral traffic over time
GA4's AI Assistant channel covers the basics. The harder part is connecting the traffic to its cause, meaning which prompts cited you, which pages AI crawlers read, and which of those pages turned into visits.
Searchable's traffic analytics connects to GA4 and Search Console and classifies AI referrals by referrer domain and UTM source, broken down by engine and landing page. The AI Traffic view puts that next to AI crawler activity, so you can see which pages AI systems read and which ones earn referred visitors.
Frequently asked questions
Start with the AI Assistant channel in the Traffic acquisition report, which Google added to GA4's default channel group in May 2026. It isn't retroactive and doesn't name every assistant, so for older data or missing sources, filter Session source for domains such as chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, and copilot.microsoft.com.
See how AI engines talk about your brand
Get a free report on where ChatGPT, Perplexity, and Google AI name and cite you.