A Beginner's Guide to Tracking AI Referral Traffic in GA4

Which referrers identify AI engines in GA4?

As of October 2026, GA4's own default-channel documentation defines a dedicated "AI Assistant" channel: traffic is assigned to it when "the medium exactly matches 'ai-assistant'" or "the medium is set to 'ai-assistant' and the campaign is set to '(ai-assistant)' if the referrer matches a list of AI Assistants," per Google's Analytics Help page on default channel groups. The same page names the engines this covers: "sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok" — and explicitly separates this from Google's own AI Overviews and AI Mode, which it does not classify as AI Assistant traffic at all.

Two gaps matter here. First, Perplexity and Claude are not on that list, so their referred visits land in the ordinary Referral channel today, mixed in with every other non-ad external link. Second, Google's own AI features (AI Overviews, AI Mode) route through a normal google.com search referrer and get counted as Organic Search — there's no separate flag for "this click came from an AI summary" versus a traditional blue link. Press coverage of the AI Assistant channel's initial rollout (widely reported as mid-May 2026) described it as covering ChatGPT, Gemini and Claude; Google's current live documentation instead names ChatGPT, Gemini, Deepseek, Copilot and Grok. The two don't match, and this post follows the current live page over the older launch coverage, since engine coverage for a feature like this is exactly the kind of detail that changes — treat the named list as accurate as of this writing and re-check it on publish day for your own use.

How to build a custom channel group for AI traffic?

GA4's default channels can't be edited directly, but a custom channel group lets you build your own ordered set of rules on top of the same source and medium data. Per Google's Analytics Help documentation on custom channel groups:

1. Go to Admin > Data display > Channel groups in your GA4 property (you need Editor access or above at the property level).
2. Click Create new channel group — this starts from a copy of the default group, so you're editing a copy, not GA4's own default.
3. Add or edit a channel rule using source, medium, campaign ID/name, manual ad content or source platform as the matching fields. For an AI-focused rule, match on source containing known AI referrer domains (for example chatgpt.com, perplexity.ai, claude.ai, gemini.google.com) or medium exactly matching ai-assistant.
4. Reorder the channel so your AI rule sits above Organic Search and Referral in the list. Google's documentation is explicit that "traffic is included in the first channel whose definition it matches given the current order of channels in the group" — so if a broader rule sits above your AI rule, matching traffic never reaches it.
5. Save, then view your custom channel group (not the default one) in Reports > Life cycle > Acquisition, or build it into an Explore report, to see AI-sourced sessions as their own row.

Standard GA4 properties allow two custom channel groups plus the predefined one, with up to 50 channels per group — plenty of room for one AI-focused group alongside whatever else you already track.

Once the group is saved, view it under Reports > Life cycle > Acquisition > Traffic acquisition, switching the dimension from the default channel group to your new custom group, to see AI-sourced sessions broken out as their own row rather than folded into Referral or Organic Search.

What visits are missed?

Three real gaps, not minor ones:

• Copy-paste and app clicks lose the referrer entirely. A link copied out of a ChatGPT answer, or tapped inside a mobile AI app, typically arrives with no referrer header, so GA4 falls back to Direct — indistinguishable from someone typing your URL in by hand.
• Vendor estimates of how much this is disagree, and the two aren't quite measuring the same thing. Loamly's own published breakdown (446,405 total site visits analyzed; 20,428 of those confirmed as AI-origin) found that 70.6% of the AI-origin subset — 14,413 of 20,428 — arrived with no referrer header, landing in Direct. Clickport's April 2026 snapshot found something narrower: of 2,619 sessions its system specifically recognized as AI Search traffic (itself only 0.7% of roughly 372,000 total sessions analyzed that month), 35.7% carried an AI source tag but no referrer. Both vendors publish the traffic-type breakdown but not a full attribution methodology, so treat the exact percentages as directional, not precise — but treat "a meaningful share of AI-origin traffic shows up as Direct" as solid, since both datasets point the same direction even while disagreeing on magnitude and on exactly what's being measured as the denominator.
• AI Overview and AI Mode clicks hide inside Organic Search, as covered above, so GA4 alone can't separate "a normal organic click" from "a click that happened because an AI summary cited this page."

How to read the numbers honestly?

Treat GA4's AI-related numbers as a floor on real AI-driven visits, never a ceiling. A rising AI Assistant channel count is real signal — it means more people are clicking through from a supported assistant. A flat or small AI Assistant count does not mean AI isn't sending you traffic; it may mean the traffic is landing in Direct, Referral or Organic Search instead, for exactly the reasons above.

Don't compare raw AI Assistant session counts across sites or time periods as if they were a complete count of "AI-driven visits" — the channel's own coverage has changed over the course of 2026 and still excludes major engines. A more honest read pairs the channel number with a Direct-traffic trend line and a self-reported source field (see the attribution proxies that fill this gap), rather than trusting one number in isolation.

Common mistakes

• Assuming GA4's AI Assistant channel captures all AI engines — it currently misses Perplexity, Claude and Google's own AI features by Google's own definition.
• Building a custom channel rule but leaving it below Organic Search or Referral in the list order, so it never actually catches anything.
• Treating a quiet AI Assistant channel as proof that AI isn't sending visits, instead of checking Direct traffic for a correlated bump.
• Comparing AI Assistant numbers month to month without noting that the channel's own referrer list has changed during the year.

Checklist before you trust a number

• Confirmed which engines your GA4 property's AI Assistant channel (or your custom group) currently matches, and which it doesn't.
• Built a custom channel group with AI rules ordered above Organic Search and Referral.
• Checked whether Direct traffic moved in the same window as a reported AI mention or citation.
• Paired the GA4 number with at least one proxy metric that doesn't depend on a referrer header.

What to pair it with?

GA4 alone can't close the attribution gap — nothing can right now. Pair it with self-reported attribution and the other proxies teams actually use, and with Bing's own free citation data if Bing or Copilot matter for your category, since that's first-party evidence of citations rather than an inference from a referrer header.

FAQ

Does GA4 show Google AI Overview traffic separately? No. A click from inside an AI Overview or AI Mode answer arrives with a normal google.com search referrer, so GA4 counts it as Organic Search, not as a distinct AI channel.

Why would my AI Assistant channel show almost no sessions? Likely reasons: the engine sending you traffic isn't on GA4's current AI Assistant referrer list (Perplexity and Claude aren't, as of this writing), the visit arrived with no referrer and landed in Direct, or you simply aren't getting much AI-referred traffic yet.

Should I build a custom channel group if the AI Assistant channel already exists? Yes, if you want engines the default channel misses (Perplexity, Claude) included, or if you want AI traffic broken out by individual engine rather than lumped into one bucket.

Is a rising Direct-traffic trend proof of AI-driven visits? No, not by itself. It's a proxy, not proof — correlate it with something else (a known citation, a self-reported source, a timing match) before treating it as a sign of AI referrals.

What to do next

1. Check whether your GA4 property's AI Assistant channel currently matches the engines that matter for your brand — it may not.
2. Build a custom channel group with AI-referrer rules ordered above Organic Search and Referral, following the five steps above.
3. Start tracking Direct-traffic trends alongside any known AI mentions, and move to proxy-based attribution for the traffic GA4 can't see at all.

ContextOwl sells one-time AI visibility reports. The AI Citation Snapshot is a free, single-question version of the same check — it shows what an engine actually says, which GA4's traffic numbers never will.