How to track AI referral traffic, and the AI agents GA4 never sees
Where visits from ChatGPT, Gemini and Copilot show up in GA4, what its AI Assistant channel misses, and how to see the AI agents analytics never records.
By Deni Bunfeld, Co-founder · · 6 min read

Visitors that ChatGPT, Gemini or Copilot send to your store now have their own line in Google Analytics 4 (GA4), the free analytics most online stores already run. It’s worth looking at, but it shows only one of the two ways AI reaches your store.
There are two kinds of AI traffic:
- People sent by an AI assistant. Someone asks ChatGPT for a product, gets a link and clicks it. That’s an AI referral: a person, in a browser, running your analytics tag.
- AI agents visiting on their own. An assistant reads your page to answer a question, or an agent drives a browser through your store to buy something. That’s software, and GA4 was built to leave software out.
This guide covers how to see the first kind in GA4, what that number misses, and how to see the second.
Find AI referrals in GA4
GA4’s default channel group has an AI Assistant channel. A visit lands there when its medium is ai-assistant, which GA4 sets itself when the visitor came from a site on its list of AI assistants. Google names ChatGPT, Gemini, DeepSeek, Copilot and Grok among them.
To see it:
- Open Reports → Acquisition → Traffic acquisition.
- Find the AI Assistant row. Its sessions, engagement and key events are your AI referrals.
- To see which assistant sent them, switch the table to Session source / medium.
If you place links in an AI tool yourself, add utm_medium=ai-assistant to them and they land in the same channel.
What the AI Assistant channel misses
Treat the AI Assistant number as a floor. Three kinds of AI visits land somewhere else.
Clicks that arrive without a referrer. Many clicks from assistants’ apps reach your site with no referrer. With no referrer and no tag on the link, GA4 has nothing to go on and counts the visit as Direct. ChatGPT adds utm_source=chatgpt.com to the links it cites, so a tagged click that lost its referrer still names its source: look for chatgpt.com in the other channels, Unassigned in particular.
Assistants that aren’t on Google’s list. If perplexity.ai or claude.ai shows up under Referral, those visitors came from an AI assistant too. A custom channel group puts them together:
- Go to Admin → Data display → Channel groups and choose Create new channel group.
- Add a channel called “AI assistants” whose Source matches a regular expression such as
.*(chatgpt|chat\.openai|perplexity|claude|gemini|copilot|deepseek|grok|meta\.ai|mistral).* - Move it above Referral, since a visit goes to the first channel whose conditions it meets, and save.
Custom channel groups apply to past data as well, so the new grouping covers your history from day one.
Google’s AI Overviews and AI Mode. Clicks from Google’s own AI answers arrive from google.com like any search result, so GA4 counts them as Organic Search. Search Console includes them in the Performance report’s Web search type, together with ordinary results. Neither tool separates them.
The AI agents GA4 never sees
Everything above is about people. The agents themselves are a different blind spot, for three reasons:
- Most agent visits never run the tag. When an assistant reads your page to answer a question, it fetches the page from its own servers and doesn’t run JavaScript. GA4 is a JavaScript tag, so those visits never reach it. The same goes for search and training crawlers.
- Known bots are filtered out. GA4 automatically excludes traffic from known bots and spiders, using Google’s research and the IAB’s list. You can’t turn this off, and GA4 doesn’t show how much it removed.
- Browser agents can pass as people. Agents that drive a real browser do run the tag, and many send the same user agent as an ordinary copy of Chrome. A visit like that can be counted as a person’s, usually a short one that bought nothing.
| Visitor | Runs GA4’s tag | How GA4 shows it |
|---|---|---|
| A person sent by an AI assistant | Yes | AI Assistant, or Direct, Referral or Unassigned when the source is lost |
An assistant reading a page (ChatGPT-User, Claude-User, Perplexity-User) | No | Not at all |
A search or training crawler (OAI-SearchBot, GPTBot, ClaudeBot) | No | Not at all |
| An agent driving a browser | Yes | Filtered out as a known bot, or counted as a person |
So GA4 can tell you how many people AI sent you. It can’t tell you how often AI read your pages, which products it looked at, or where an agent gave up before anyone clicked.
How to see the agents too
Your server logs. Every fetch reaches your server, so the logs have them: search for the user agents in the table above and see which pages they request. A user agent is only a claim, so check the request’s address against the ranges the AI companies publish (OpenAI’s, for example) before you trust it. Logs show requests, not journeys: they won’t tell you that a browser agent reached the cart and stopped at a CAPTCHA.
Parlox. Parlox sees both halves. Its server part reports the fetchers and crawlers your pages never see, its browser part tells browser agents from people, and every visit carries a label that says what it rests on: verified, declared or inferred. People sent by AI assistants are counted per assistant, with how far each got toward a purchase (People sent by AI assistants). To see what agents run into on your store today, get a free agent audit.
Questions store owners ask
Does Google Analytics track ChatGPT traffic?
It tracks the people who click a link in ChatGPT and arrive with the referrer intact: GA4 puts them in its AI Assistant channel. It doesn’t see ChatGPT reading your pages, because those fetches never run GA4’s tag, and clicks that arrive without a referrer are counted elsewhere, usually as Direct.
Why does AI traffic show up as Direct in GA4?
Because the click arrived without a referrer, which often happens when someone taps a link in an assistant’s app. With no referrer and no tag on the link, GA4 has nothing to go on and counts the visit as Direct.
Can I see traffic from Google’s AI Overviews?
Not on its own. Clicks from AI Overviews and AI Mode arrive from google.com like ordinary search results, so GA4 counts them as Organic Search, and Search Console includes them in the Performance report’s Web search type with everything else.
See which of these affect your store.
We send shopping agents through your store’s public pages the way real ones travel, and show you where they fail, why, and what it’s likely costing you.