Track AI Traffic in GA4 (2026): The Honest Guide

TL;DR: As of May 13, 2026, GA4 has a native “AI Assistants” channel that auto-buckets traffic from ChatGPT, Gemini, Copilot, Grok, and Deepseek with zero setup. Good. But it misses three things: AI traffic that arrives with no referrer (native apps and in-app browsers) still lands in Direct, Google’s own AI Overviews and AI Mode get filed under Organic Search where you cannot separate them, and Perplexity is not on Google’s list so it still shows up as a plain Referral. And if anyone tells you “60 to 70% of your AI traffic is misattributed,” they are making that number up: no credible source for it exists. Here is what the native channel does, what it misses, and the one setting that fills most of the gap.

Does GA4 track AI traffic now?

Yes. On May 13, 2026, Google added a native “AI Assistants” default channel group (Google’s release notes and Default Channels reference). When GA4 sees a referrer on Google’s recognized list, it rewrites the medium to ai-assistant, sets the campaign to (ai-assistant), and files the session under the AI Assistants channel. No configuration required. Google’s docs name ChatGPT, Gemini, Deepseek, Copilot, and Grok as sources for it. One catch worth knowing: it is forward-only, so it does not reclassify your history, and the recognized list changes (Claude was named in the May announcement but had dropped out of the live channel definition by June).

What does the native channel miss?

Three things, and they matter. First, any AI visit that arrives with no referrer header still lands in Direct. Native mobile apps and in-app browsers strip the referrer, so those sessions look identical to someone typing your URL. The native channel can only classify what it can see. Second, Google’s own AI Overviews and AI Mode are explicitly excluded from the AI Assistants channel and roll into Organic Search instead (Google’s docs say so verbatim). Those clicks carry a google.com referrer identical to a normal search result, so you cannot pull them out. Third, Perplexity is not on Google’s recognized list, so it still shows up as a regular Referral from perplexity.ai.

How do I fill the gaps?

Add a custom channel group with a “matches regex” rule on the session source. GA4 supports regex rules on Source and Source/Medium, and Google’s own docs publish an AI-assistant example. A minimal, practical pattern to start with:

That catches Perplexity and the long-tail assistants the native channel skips, and it lets you backfill a consistent view for data from before May 2026. Skip the gemini.google.com token if you are keeping it short, because Gemini almost always lands in Organic anyway, so it catches very little. The regex approach is belt-and-suspenders on top of the native channel, not a replacement for it.

How much AI traffic am I actually losing to Direct?

Nobody credibly knows, and you should distrust anyone who claims to. The “60 to 70% of AI sessions have no referrer” figure that circulates has no named source or sample behind it, and it did not survive fact-checking. The loss to Direct from referrer stripping is real in direction but genuinely unquantified across the industry. The only honest way to estimate it for your own site is to compare your server or edge logs against GA4 and see how much AI-adjacent traffic shows up in one and not the other. Anyone selling you a fixed percentage is selling you a guess.

What should you actually do?

Turn on the native channel, patch the two holes you can, and be honest about the one you cannot.

Confirm the AI Assistants channel is showing in your reports (it should, automatically).
Add the custom channel-group regex above to capture Perplexity and the long tail.
Accept that AI Overviews and AI Mode are invisible inside Organic. Watch your branded-organic and direct trends as a proxy for the “read the answer, searched you later” behavior.
Do not report a misattribution percentage to anyone. Report the trend, and estimate the Direct leakage from your own logs if you need a number.

FAQ

Do I still need a custom regex now that GA4 has a native channel? Yes, for Perplexity (not on Google’s list) and for backfilling data from before May 2026.

Can I see my Google AI Overviews traffic separately? No. Google files it under Organic Search with a normal google.com referrer, and there is no way to split it out in GA4 today.

Why is so much AI traffic in Direct? Native apps and in-app browsers strip the referrer, so GA4 cannot tell where the visit came from. It is real traffic with no return address.

Is there a trustworthy number for how much I am losing? No. The commonly quoted figures are unsourced. Estimate it from your own logs or do not quote it.

Sources and method

The native channel, its mechanism, the AI-Overviews exclusion, and the custom-channel-group regex are all anchored in Google’s own GA4 documentation (release notes, Default Channels reference, and custom-channel-group docs), corroborated by Search Engine Journal and practitioner guides from Martech, Analytics Mania, and Loves Data. The referrer-stripping-to-Direct behavior is well-established analytics mechanics but not quantified by any credible study. This is a fast-moving area and Google’s recognized-referrer list is actively changing, so re-check the live docs before you act on it. When you filter your own analytics to the AI Assistants channel plus that regex, does the traffic line up with the places you have actually been getting mentioned?