GA4 finally has a native "AI Assistant" channel — here's what it still hides

June 14, 2026

If you went looking for your ChatGPT or Gemini traffic in Google Analytics this spring, you finally found it without building anything: on May 13, 2026 Google added a native AI Assistant channel to GA4's default channel group. No custom regex, no setup — sessions referred by recognized AI assistants now roll up into their own channel automatically.

That's a real improvement, and it makes the manual workaround we documented a few days earlier unnecessary for the big names. But before you trust the new channel as your AI number, know what it leaves out. Three large slices of AI traffic still land somewhere other than "AI Assistant" — and for many sites the missing slices are bigger than the one GA4 now catches.

What the native channel actually catches

GA4's AI Assistant channel is referrer-based and automatic. When a visit arrives with a referrer Google recognizes as an AI assistant, GA4 assigns it medium = ai-assistant and files it under the AI Assistant channel in your standard reports — no configuration required. Google's announcement named ChatGPT, Gemini and Claude as recognized sources, and the channel rolled out to essentially all properties by early June 2026.

If those three are most of your assistant traffic, you can delete your custom channel group and move on. For everyone else, here's the fine print.

What it still hides

1. Perplexity lands in Referral

Perplexity is one of the highest-intent AI referrers — people there are often mid-research, clicking through to read more — and it is not in GA4's AI Assistant channel. A visit from perplexity.ai still gets filed under Referral, mixed in with backlinks and newsletter mentions. Google's recognized list is undocumented and has been expanding, so this may change; today it does not.

2. Google's own AI Overviews and AI Mode count as Organic Search

This is the big one. When someone clicks a citation inside a Google AI Overview or AI Mode answer, that click carries a google.com referrer — so GA4 files it as Organic Search, not AI Assistant. That is intentional: Google treats its AI search surfaces as part of Search, not as a third-party assistant. For most sites this is the single largest source of AI-influenced traffic, and in standard reports it is completely invisible as "AI."

No analytics tool can reclassify it, either — a click from a Google AI surface genuinely looks like a Google search click, because that's what it is.

3. Copy-paste and in-app clicks land in Direct

Plenty of AI traffic arrives with no referrer at all: a link copied out of a chat, or an assistant's mobile app or in-app browser that strips the referer header. Estimates of the stripped share run wide — roughly 35–70% of AI-referred sessions by various third-party analyses — and every one of them falls into Direct, alongside bookmarks and typed URLs. This is the honest universal limit: no tool, GA4 or otherwise, can recover a referrer that was never sent. We said it in our earlier post and it's still true.

Where each source ends up

So the native channel is a floor, not a ceiling. The current best-practice setup is to run both: keep the native AI Assistant channel for the recognized sources, and keep a custom channel group above Referral to catch Perplexity and newer assistants. The how-to for that custom group — the exact regex and the ordering that stops gemini.google.com from being claimed by Search — is in our earlier guide.

What this changes for the GA4-alternative argument

We'll be straight about it: GA4 catching up here narrows one of our talking points. For ChatGPT, Gemini and Claude, GA4 now does automatically what Simplytics does — group them into an AI channel with no setup. The honest differences that remain are smaller and more specific:

• Perplexity is in our AI channel out of the box. Simplytics classifies perplexity.ai as AI, not Referral — so the one major assistant GA4's native channel currently misses is the one we don't.
• No maintained list on your side, ever. GA4's recognized set is undocumented and you can't audit it; with Simplytics the AI channel ships as a fixed, readable list (ChatGPT, Perplexity, Claude, Gemini, Copilot, DeepSeek, Grok, Mistral and more) and we update it.
• No cookie banner, ~1.9 KB instead of ~140 KB. The AI channel was never the only reason to leave GA4. You still skip the EU consent banner and the ~140 KB of JavaScript gtag.js makes every visitor download — for $1/month versus the configuration overhead of "free."

And we'll hold ourselves to the same honesty we're asking of GA4: Simplytics cannot see your AI Overviews traffic either. A click from a Google AI surface reaches us with a google.com referrer, so we file it under Search, exactly as GA4 files it under Organic Search. Stripped-referrer AI clicks land in our Direct bucket, exactly as they land in GA4's. We don't model or "recover" that dark traffic, and we'd rather say so than quote you a number we didn't measure.

The short version

GA4's native AI Assistant channel is a genuine, overdue improvement — if your AI traffic is mostly ChatGPT, Gemini and Claude, it's all you need. Just don't mistake it for your total AI number: Perplexity is in Referral, Google's own AI Overviews are in Organic Search, and copy-paste clicks are in Direct. The measurable assistants are a fixed list of hostnames that should never have needed homework — GA4 finally agrees for three of them, and Simplytics ships the rest, cookie-less, for a dollar a month.

If you're weighing the move, the full Google Analytics comparison and the other comparisons lay out the rest of the trade-offs honestly.

GA4's recognized-assistant list is undocumented and expanding, and per-platform referrer behavior changes fast — the buckets above reflect how GA4's default channel group behaved as of June 14, 2026. If you spot a change, email us and we'll update this post.