How to measure AI search traffic in GA4 (and find the hidden referrals)

In May 2026 Google quietly fixed the biggest hole in AI measurement: GA4 now recognises AI-assistant referrals on its own. It's a real step — and it's still only half the picture. Some AI visits arrive with no referrer at all, and Google's own AI results never get labelled at all.

The short version: read GA4's native AI Assistant channel first, then add one custom channel group to catch the assistants Google leaves out. Accept that a slice of AI traffic will always land in Direct — no referrer, no source — so pair GA4 with a separate mentions check. You're measuring two different things: the clicks you can see, and the recommendations you can't.

What "AI search traffic" actually is

It's a person who asked an AI a question, got a link inside the answer, and clicked through. Not a bot, and not a crawler — a real visitor who found you because an assistant recommended you mid-conversation (Search Atlas). Those visitors tend to arrive already convinced, which is why measuring them matters.

Why most of it hides — four leaks

• Referrers get stripped. Many assistants don't send a referrer on click, so GA4 has no source to attribute and files the visit under Direct (Search Engine Journal, Supermetrics).
• Mobile apps lose it too. ChatGPT's app strips the referrer, so app clicks surface as Direct as well (Search Atlas).
• Google's own AI hides inside Organic Search. GA4's AI Assistant channel explicitly excludes AI Overviews and AI Mode, so clicks from those count as ordinary organic search (Digital Applied).
• It's forward-only. GA4 does not retroactively reclassify: anything before 13 May 2026 stays Referral, Direct, or whatever you had (Digital Applied).

What GA4 now does for you — free

• On 13 May 2026 GA4 added an AI Assistant channel to the Default Channel Group. No setup required (Google Analytics — What's new).
• When the referrer matches a recognised assistant, GA4 assigns medium = `ai-assistant`, channel = AI Assistant, campaign = `(ai-assistant)` (Google Analytics).
• Google's launch named ChatGPT, Gemini and Claude; the live docs now list ChatGPT, Gemini, DeepSeek, Copilot and Grok — and Google has never published the full list (Search Engine Journal, Digital Applied).
• Perplexity is not in the native list, so its traffic still lands in Referral (Digital Applied).
• Broad availability across properties was reached around 7 June 2026 (Digital Applied).

Step 1 — read the native channel (2 minutes)

• Go to Reports → Acquisition → Traffic acquisition and set the primary dimension to Session default channel group.
• Look for the AI Assistant row. That number, today, is your baseline — screenshot it and date it (Supermetrics).

Step 2 — add one custom channel group (the catch-all)

Because Google's list is incomplete, build your own group to catch what the native channel misses (Themeisle, Swydo):

1. Admin → Data display → Channel groups → open the menu on Default Channel Group and copy it (the default can't be edited).
2. Add a new channel and name it "AI Search".
3. Add two conditions joined by OR: *Session source* matches regex (pattern below), or *Session medium* exactly matches ai-assistant. That second condition inherits anything Google adds later.
4. Reorder so AI Search sits above Referral. GA4 matches rules top-to-bottom, and this is the step almost everyone gets wrong — if Referral comes first, your new channel never fires.
5. Save, then select the group as the dimension in your reports.

The regex (extend it as you find new AI domains):

chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|claude\.ai|copilot\.microsoft\.com|grok\.com|x\.ai|deepseek\.com|you\.com|poe\.com|phind\.com

Step 3 — hunt the leaks

• Watch Direct. A step-change in Direct — especially on mobile — with no campaign to explain it is often AI clicks with no referrer (Search Engine Journal).
• Filter the Referral report by source weekly and add any new AI domains you spot to the regex (Themeisle).
• Keep it in perspective: AI referrals are roughly 1.08% of site traffic, and ChatGPT is about 87% of that (Conductor).
• Programmatically: the GA4 Data API exposes the same sessionDefaultChannelGroup dimension for reporting in code (GA4 Data API schema).

Step 4 — the part GA4 cannot fix

If there's no referrer, there's no source — and no channel group, regex, or API can invent one (Supermetrics). What actually helps:

• Tag the links you control with UTMs (e.g. utm_medium=ai) so those visits are never ambiguous.
• Capture the referrer in a custom dimension for the cases you *can* see, so you can slice by platform.
• Fire a GTM event — ai_referral_detected, with the platform as a parameter — and register ai_source_platform as a custom dimension for detail the channel group can't give you (Swydo).
• Treat GA4's AI number as a floor, never the whole truth.

Step 5 — don't confuse traffic with visibility

GA4 measures clicks, not recommendations. A mention that never gets clicked is invisible to GA — and that's where most of the value sits. 68% of Google searches now end without a click at all (SparkToro).

So measure both, deliberately: the clicks (GA4, above) and the mentions (ask the engines your buyer questions and check whether you're named). 83.6% of people have discovered a brand they'd never heard of through an AI (Snipp) — and most of them weren't tracked as a referral when they finally arrived.

Why any of this is worth measuring

• 42% of US adults now use AI chatbots to search (Pew Research Center).
• 41.6% start product research with an AI assistant — ahead of the share who start at Amazon (Snipp).
• Using AI to find a local business jumped from 9% to 52% in a single year (SOCi).
• AI-referred visitors arrive pre-sold: small share of traffic, highest share of intent (Conductor).

The 5-minute checklist

• Screenshot the native AI Assistant row today — that's your baseline.
• Build the "AI Search" custom channel group and reorder it above Referral.
• Filter the Referral report by source weekly; add new AI domains to the regex.
• Watch Direct for mobile step-changes.
• UTM any AI link you control.
• Run a mentions check on your buyer questions — GA4 will never do this for you.

Two numbers, then: what GA4 can see, and what the engines actually say. Track both, and you'll never mistake a quiet dashboard for invisibility.

Get in touch: thecollective@memeador.com