For years, the question “how many visitors is ChatGPT actually sending me?” was almost impossible to answer in Google Analytics 4. AI traffic hid between Referral and Direct – and anyone who wanted to see it had to improvise. With the new AI Assistant channel group, Google has changed that: AI assistants now get a line of their own in the report.
That may sound like a minor technical footnote, but for marketing it is an important step. If you do not measure how much revenue comes from AI answers, you cannot grow that channel either. In this article we set out what the new channel group delivers – and where you need to look closely to make sure the numbers add up.
1. What the AI Assistant channel group is
On 13 May 2026, Google added a new channel to the GA4 default channel group: AI Assistant. Sessions that come from a recognised AI assistant have since been assigned to this group automatically – without you having to configure anything in your property. The channel sits alongside the familiar groups Organic Search, Paid Search, Direct and Referral.
In practice this means: if someone retrieves an answer in ChatGPT that links to your website and clicks through, GA4 now visibly classifies that visit as AI traffic – instead of letting it disappear under “referrals” as before. At launch, the list maintained by Google covered several major assistants such as ChatGPT and Gemini, and it has been extended since. What matters most is what is not on it – more on that shortly.
In short: GA4 has brought AI traffic out of the grey area. The new “AI Assistant” channel shows how many visitors arrive via generative assistants – a signal that keeps growing in importance in the age of AI search.
2. The change at a glance
The comparison below shows what has actually changed for measuring AI traffic – and what remains hidden despite the new channel.
Schematic comparison. Green = clear progress, yellow = limitation that still applies. As at July 2026.
3. How GA4 detects AI traffic automatically
The assignment runs via the referrer header. When a visit comes from a domain that GA4 recognises as an AI assistant, Analytics automatically assigns the medium ai-assistant and files the session under the AI Assistant channel. It is therefore the same mechanism as for Organic Search or Referral – just with a new, predefined list of sources.
3.1 No tag, no code, no setting
For you as a website owner this means: nothing to do. The classification is part of the default channel group and takes effect automatically. You do not need to create a new tag in Google Tag Manager or define any rules. The channel appears by itself as soon as the first AI visits come in.
3.2 The rollout is gradual – and not retroactive
Two points matter here: Google rolled the channel out over several weeks, so it was not immediately visible in every property. And it only counts from launch onwards – historical data is not reclassified after the fact. For now, that rules out a clean year-on-year comparison for AI traffic.
4. How to find the report in GA4
Getting to your AI traffic takes just a few clicks:
- In GA4, open Reports and then Acquisition → Traffic acquisition.
- Set the primary dimension to Session default channel group.
- Look for the AI Assistant row in the table – it appears alongside Organic Search, Direct and Referral, provided AI traffic has been recorded since May 2026.
- A secondary dimension such as Source/medium shows which assistant (chatgpt.com, for example) sent the visits.
Tip: Set up a comparison or your own exploration segment for “AI Assistant”. That keeps the channel permanently in view – and shows you early on whether AI visitors convert better or worse than the rest of your traffic.
5. The three blind spots
Useful as the new channel is, it does not measure all AI traffic. There are three limitations you should know about, otherwise you will significantly underestimate your actual AI share.
5.1 Perplexity is missing
Of all sources, Perplexity – one with particularly strong purchase and research intent – is not currently included in the native channel group. Visits from Perplexity still end up under Referral and do not appear in the AI Assistant channel at all.
5.2 Visits without a referrer disappear into Direct
A large share of AI visits – often well over a third – arrives without a referrer, above all from the assistants' mobile apps. Without a referrer, GA4 cannot identify the origin and the visit is counted as Direct. This AI traffic is therefore real, but invisible.
5.3 No history, no year-on-year comparison
Because the channel only counts from May 2026 and does not work retroactively, you have no past data. Trends can only be read reliably as the time period grows – patience is part of the method here.
6. A custom channel group by rule – the workaround
If you want to capture AI traffic more completely, build a custom channel group in GA4. The advantage: you define which sources count as AI – and close the gaps in the native group.
- Create your own AI group: under Admin → Channel groups, create a custom group and add a channel called “AI assistants”.
- Rule on the referrer: define a condition that checks the source against a pattern (regex) – including the services Google does not capture, such as Perplexity, Grok and DeepSeek.
- Mind the order: place the AI rule before Organic and Referral so that AI sources are not swept into another channel first.
- Accept the limit: referrer-less app visits remain in Direct here too – no rule fixes that; it is a technical hurdle caused by the missing referrer.
For most SMEs, combining the native group (convenient, official) with a custom group (more complete) is the best compromise: minimal effort, maximum visibility.
7. Why AI traffic matters strategically for SMEs
Measurement is not an end in itself. For many people, AI assistants have long been the first port of call for purchase decisions, supplier comparisons and research. Google's AI Overviews alone reach more than 2.5 billion people a month, according to Google. Being mentioned and linked in those answers earns visibility – and that is exactly the effect the new channel makes measurable.
Measurement turns into strategy: if you can see that AI traffic is growing and converting well, investing in Generative Engine Optimization (GEO) pays off – that is, in appearing as a trustworthy source in AI answers. Without figures this remains a gut feeling; with the AI Assistant channel it becomes a verifiable metric in your reporting.
For more on how to become visible in AI answers, read our article on Generative Engine Optimization as well as Is your website visible in ChatGPT?.
8. Checklist: measuring AI traffic properly
Would you like to measure AI traffic properly and derive a GEO strategy from it? Book a free initial consultation with our team.
9. Conclusion: a line of its own – with an asterisk
The AI Assistant channel group is a long overdue step: AI traffic finally gets a visible line of its own in GA4 – with no effort and no code. For SMEs that want to know whether their presence in ChatGPT and similar tools is paying off, that is genuine progress.
But the figure is a lower bound, not the full picture. Perplexity is missing, referrer-less app visits land in Direct, and there is no history. Combine the new native group with your own regex channel group and keep the Direct share in mind, and you will measure AI traffic as accurately as is possible in 2026 – turning a technical change into a real marketing lever.
Our assessment: the new channel is the starting signal, not the finishing line. What counts is measuring AI visibility systematically and converting it into GEO. The companies that build a clean time series now will be the first to understand how much revenue really comes from AI search.
Read also: AI Visibility Score and Cookieless and Consent Mode v2.
10. FAQ: the key questions about AI traffic in GA4
Where do I find AI traffic in Google Analytics 4?
Open Reports, then Acquisition and Traffic acquisition. Set the primary dimension to Session default channel group. Provided AI traffic has been recorded since the launch in May 2026, AI Assistant appears as a line of its own alongside Organic Search, Direct and Referral.
Does the AI Assistant channel group also capture Perplexity?
No. As things stand, Perplexity is not recognised by the native channel group and still ends up under Referral. If you want to measure Perplexity and other assistants such as Grok or DeepSeek in full, you also need a custom channel group with a rule (regex) applied to the referrer.
Why does GA4 show less AI traffic than I expect?
Two reasons: the channel group is not retroactive, it only counts from launch and provides no history. And a considerable share of AI visits arrives without a referrer, above all from mobile apps, and therefore falls under Direct rather than AI Assistant. Both mean that real AI traffic tends to be underestimated in GA4.
Do I need to set anything up for the AI Assistant channel group?
No. The native AI Assistant channel group is active without configuration and classifies recognised AI referrers automatically via the referrer header, using the medium ai-assistant. For complete coverage of all assistants, an additional custom channel group is advisable.
