4 min readEngineering

GA4's AI Assistant Channel: What It Tracks and Misses

GA4's new AI Assistant channel breaks out ChatGPT, Gemini, and Copilot traffic - but excludes Perplexity and isn't retroactive. What it tracks, and the gaps.

Marius Voß
DevRel · edge infra
GA4's AI Assistant channel breaking out ChatGPT, Gemini, Copilot, Grok, and DeepSeek traffic, with Perplexity still landing in Referral

GA4 now has a dedicated channel for AI traffic. Google added an "AI Assistant" Default Channel Group - the classification logic went live on 13 May 2026 and reached properties around 7 June 2026 - that automatically pulls ChatGPT, Gemini, Copilot, Grok, and DeepSeek out of the Referral bucket and into their own named row. No configuration, no tag manager surgery. If you report on where traffic comes from, this is a genuinely useful addition. It also has two gaps worth knowing before you trust the number.

This is an engineering-cluster read about measuring AI traffic, which is a different job from earning AI citations - the answer engine optimization guide covers the earning side. Here the question is: once an AI assistant sends you a click, does your analytics count it correctly?

What the Channel Actually Does

Under the hood it is a rule on the traffic medium. GA4 recognises sessions whose medium resolves to ai-assistant and files them under the new channel, sitting alongside Organic Search, Direct, and Referral in the standard acquisition reports. Before this, a click from ChatGPT landed in Referral mixed in with everything else, or in Direct when no referrer travelled. Now the recognised assistants get their own line automatically.

The list Google ships with is ChatGPT, Gemini, Copilot, Grok, and DeepSeek. For those five, you get a clean channel with zero setup. That is the good part, and for most teams it is a real improvement over eyeballing the Referral report for chatgpt.com. Search Engine Journal's rundown covers the rollout in more detail.

GA4 reclassifying ChatGPT, Gemini, Copilot, Grok, and DeepSeek sessions into the AI Assistant channel, while Perplexity traffic still falls into the Referral channel

The Two Gaps

Here is where you stop trusting the number blindly.

Perplexity is not in it. Perplexity is absent from Google's official definition, so its referrals keep landing in the Referral channel. If a meaningful slice of your AI traffic comes from Perplexity - and for research-heavy audiences it does - the AI Assistant channel undercounts you until you add a custom rule (source contains perplexity.ai, medium = referral). Any assistant Google has not added yet has the same problem; the channel is a fixed list, and the AI landscape is not.

It is not retroactive. Classification runs from 13 May 2026 forward. Every date range before that shows zero AI Assistant traffic, which looks like AI traffic did not exist yet rather than "GA4 wasn't labelling it yet." Year-over-year and long-window comparisons are distorted by the start date, not by reality.

Two gaps in the GA4 AI Assistant channel: Perplexity excluded until a manual rule is added, and no data before 13 May 2026, with a tagged short link recording the click regardless

The Fix That Does Not Depend on Google's List

Both gaps have the same root cause: GA4 classifies a session after the fact, from a referrer, against a list Google maintains. Anything off the list, or before the start date, is invisible. A link you own does not have that dependency.

When you place a link in content an AI can cite - docs, a landing page, a resource an assistant is likely to surface - use a tagged short link. The redirect records the click server-side the moment it resolves: the campaign, the destination, the time. That capture happens whether GA4 later files the session as AI Assistant, Referral, or Direct, so it catches Perplexity, it exists for dates before 13 May, and it does not wait for Google to add the next assistant. It is the same server-side principle that makes dark social and cookieless attribution measurable at all.

To be clear about the boundary: this does not replace GA4, and the AI Assistant channel is worth using for the five assistants it covers. A short link is the independent second source that fills what a referrer-based, list-based classifier structurally cannot - and it does it in privacy-first analytics that count the click without a cookie. Tag your AI-facing links and you stop being at the mercy of whose name is on Google's list this quarter.

What to Do This Week

Three quick moves:

  1. Turn on the AI Assistant channel awareness - it is automatic, so mainly confirm it is appearing in your reports.
  2. Add the Perplexity custom rule so you are not silently undercounting.
  3. Put tagged short links on the pages AI assistants are most likely to cite, and reconcile their click totals against the GA4 channel to size the gap.

The channel is a good default. Treat it as one input, not the whole picture, and instrument a source that does not depend on a maintained list.

Read the Cornerstone Series

This sits in the engineering cluster. For the citation side, see answer engine optimization; for the measurement siblings, dark social and cookieless attribution.

Frequently asked questions

What is the GA4 AI Assistant channel?

It is a new Default Channel Group in GA4 that automatically reclassifies sessions from AI assistants out of Referral into their own channel. Google added the classification logic on 13 May 2026 and rolled it out to properties around 7 June 2026. It needs no configuration - matching traffic just starts appearing under a channel called AI Assistant.

Which AI assistants does GA4 track in this channel?

ChatGPT, Gemini, Copilot, Grok, and DeepSeek are recognised and reclassified automatically. The channel matches sessions whose medium is ai-assistant. It is the same acquisition report you already use, with a new named row sitting beside Organic Search, Direct, and Referral.

Does GA4 track Perplexity traffic?

Not in the AI Assistant channel by default. Perplexity is absent from Google's official definition, so Perplexity referrals still land in the Referral channel. To capture it, create a custom channel rule in GA4 matching source contains perplexity.ai with medium referral, or you will undercount your AI traffic.

Is the GA4 AI Assistant data retroactive?

No. Classification starts from 13 May 2026 forward, so any date range before that shows zero in the AI Assistant column. That is expected, not missing data. If you want AI traffic measured consistently across the whole period, you need a source that recorded it from the start, such as your own tagged link clicks.

How do I measure AI traffic that GA4 misses?

Tag the links you place in AI-readable content and read the click at the redirect. A short link records every resolve server-side regardless of how GA4 classifies the session, so it captures Perplexity, fills the pre-May-13 gap, and does not depend on Google adding each new assistant to its list.

Try Elido

Paste a URL, get a working short link

No signup. Link lives for 30 days. Sign up to keep it forever.

Free, no signup required · 2 per day

Try Elido

EU-hosted URL shortener with custom domains, deep analytics, and an open API. Free tier - no credit card.

Tags
ga4 ai assistant channel
ga4 ai traffic
track chatgpt traffic ga4
ai assistant default channel group
measure ai referral traffic
perplexity ga4

Continue reading