Share This Article
GA4 now sorts visits from recognised AI assistants into their own “AI Assistant” channel automatically. You’ll find it in Reports › Acquisition › Traffic acquisition. But it doesn’t capture everything: Google’s own AI Overviews and AI Mode still count as Organic Search, some assistants aren’t on Google’s list, and AI visits without referrer data land in Direct. A backup custom channel group fills most of the gaps.
For two years, measuring traffic from ChatGPT and other chatbots in Google Analytics meant writing regex filters and hoping you’d caught every domain. In May 2026 Google added a native channel for it. That’s a real improvement, but the numbers it shows are a floor, not the full picture. Here’s how it works, where it falls short and how to set up reporting you can trust.
What is the GA4 AI Assistant channel?
On 13 May 2026, Google added “AI Assistant” to GA4’s Default Channel Group, the list of buckets (Organic Search, Paid Search, Direct, Referral and so on) that every session is sorted into. It reached most properties in early June.
When a visitor arrives from a recognised AI assistant, GA4 now does three things automatically:
- sets the medium to ai-assistant
- sets the campaign to (ai-assistant)
- places the session in the AI Assistant channel
No setup is needed. It works for any property, but only from the date it went live. It doesn’t rewrite your historical data.
Which AI tools does it include?
At the time of writing, Google’s channel definitions name ChatGPT, Gemini, Deepseek, Copilot and Grok as the AI assistants it recognises. The list has already changed once since launch (Google’s original announcement mentioned ChatGPT, Gemini and Claude), so check the current definitions page before you report on it.
What matters is what’s not on the list. If an assistant isn’t recognised, its visits usually show up as Referral, with the assistant’s domain as the source. At the time of writing, that includes traffic from Perplexity and Claude.
What the AI Assistant channel doesn’t capture
| AI traffic type | Where it shows up in GA4 | Why |
|---|---|---|
| ChatGPT, Gemini, Deepseek, Copilot, Grok (with referrer) | AI Assistant | On Google’s recognised list |
| Perplexity, Claude and other unlisted assistants | Referral | Not on the list (yet) |
| Google AI Overviews and AI Mode | Organic Search | Google treats them as part of search results and says so in its definitions |
| AI visits with no referrer (apps, copied links, some in-app browsers) | Direct | GA4 can’t see where they came from |
| Visits before mid-May 2026 | Referral (or Direct) | The channel isn’t retroactive |
The Direct row is the big unknown. When someone copies a link from a chatbot’s desktop app, or the app opens it without passing a referrer, GA4 has nothing to go on. Many site owners have noticed their Direct traffic creeping up since 2025, and some of that is likely AI. There’s no reliable way to measure how much.
How to see your AI Assistant traffic
- In GA4, go to Reports › Acquisition › Traffic acquisition.
- Make sure the table’s primary dimension is Session default channel group.
- Look for the AI Assistant row. If you don’t see it, you may not have had any recognised AI visits in the date range.
- To see which assistants sent the traffic, click the + next to the dimension and add Session source as a secondary dimension.
- Compare engagement rate, average engagement time and key events against Organic Search. Many sites find AI visitors are fewer but more engaged, though your own numbers are what count.
How to build a fuller AI traffic report
To include Perplexity, Claude and newer assistants, create a custom channel group that sits alongside the default one. GA4 lets you have a limited number of custom channel groups per property, so name this one clearly.
- Go to Admin › Data display › Channel groups and click Create new channel group.
- Name it something like “Channels incl. all AI”. GA4 copies the default channels into it.
- Click Add new channel and call it “AI (all)”.
- Add a condition: Source › matches regex, and paste a pattern such as:
.*(chatgpt|openai|perplexity|claude|anthropic|gemini|bard|copilot|deepseek|grok|meta\.ai|mistral|you\.com|phind).* - Add a second condition with OR: Medium › exactly matches › ai-assistant, so anything Google already recognises is included too.
- Reorder the channels so “AI (all)” sits above Referral. GA4 assigns each session to the first channel it matches, so order matters.
- Save, then use this channel group in Traffic acquisition or Explorations.
Update the regex every few months as new assistants appear. Unlike the default channel, custom channel groups can be applied to past data in reports, which helps with before-and-after comparisons.
How to measure Google AI Overviews and AI Mode
GA4 can’t separate these from normal search, because Google counts them as Organic Search. For this part of the picture, use Google Search Console instead. Its Generative AI report shows how often your pages appeared as links in AI Overviews and AI Mode. It shows impressions only, not clicks. We explain how to read it in our Search Console Generative AI report guide.
For Microsoft Copilot citations, Bing Webmaster Tools has its own AI Performance report. See our Bing AI Performance guide.
A simple monthly AI traffic check
| What to check | Where | What it tells you |
|---|---|---|
| AI Assistant sessions and key events | GA4 default channel group | Traffic from recognised assistants |
| “AI (all)” sessions | GA4 custom channel group | A fuller count, including Perplexity and Claude |
| Top landing pages from AI traffic | GA4, Landing page report filtered to AI | Which content AI tools send people to |
| Generative AI impressions | Search Console | Visibility in AI Overviews and AI Mode |
| Copilot citations and grounding queries | Bing Webmaster Tools | Visibility in Microsoft’s AI answers |
| Direct traffic trend | GA4 | A rough signal for AI visits without a referrer |
Common questions
Why is my AI Assistant channel empty?
Either you’ve had no visits from recognised assistants in that date range, or you’re looking at dates before mid-May 2026, when the channel didn’t exist yet. Check Referral for AI domains to confirm.
Why doesn’t Perplexity show in the AI Assistant channel?
At the time of writing, Perplexity isn’t on Google’s recognised list, so its visits land in Referral. Add it to a custom channel group to count it as AI.
Are Google AI Overviews counted as AI traffic in GA4?
No. Google classifies clicks from AI Overviews and AI Mode as Organic Search. Use Search Console’s Generative AI report to see that visibility.
Can I see which ChatGPT prompt sent a visitor?
No. AI assistants don’t pass the user’s question to your site. You can see the landing page, which is often a good clue.
Is AI traffic worth tracking if it’s small?
Yes. It’s small for most sites today, but it’s growing, and it tells you which of your pages AI tools trust enough to link to. That’s useful input for your content plan.
The bottom line
The AI Assistant channel is a good start and costs nothing. Treat its number as the minimum, add a custom channel group for the assistants it misses, and use Search Console and Bing for the AI visibility that never shows up as a click. For the bigger strategy behind getting cited in the first place, read our guide to generative engine optimization.
Sources
- Google Analytics Help, Default channel group
- Search Engine Journal, Google Analytics adds AI Assistant as default channel group (May 2026)
- Google Search Central Blog, Search generative AI performance reports
