Google Analytics 4 (GA4) now classifies AI traffic with a default, out-of-the-box channel: "AI Assistant". But only part of it. Here's what it covers, what slips past it, and whether your custom channel is still needed — short answer: yes.
The channel appeared in your reports two months ago without you touching anything. The root problem is still the one we documented in why your AI traffic shows up as Direct: everything depends on the referrer. And if you built the AI traffic channel in GA4, the question is obvious — is it obsolete now?
Where the 'AI Assistant' Channel Came From
On May 13, 2026, Google added the channel to GA4's Default Channel Group. According to the Google Analytics release notes, "you can now identify how users are discovering your site through chatbots like ChatGPT, Gemini, and Claude" via the new channel in your reports.
The mechanics are simple. When the referrer matches a recognized AI assistant, GA4 assigns the value "ai-assistant" to the medium, groups the session under the "AI Assistant" channel, and labels the campaign "(ai-assistant)" — all three at once, automatically.
Being a "default" channel means exactly that: nothing to enable, nothing to configure, it just appears. According to Search Engine Journal, "property owners don't need to configure anything" — until this change, all of that traffic landed in Referral by default.
In practice you notice it in two places. The Traffic acquisition and User acquisition reports show the new row alongside Organic Search, Direct, and Referral. And if your Referral channel dropped sharply in mid-May, you didn't lose traffic — according to TechWyse, the channel's arrival "will shift some volume out of Referral and into AI Assistant": the same sessions with a new label.
It's also worth reviewing segments and filters that condition on medium. A condition like "medium does not contain cpc" now implicitly excludes sessions with the "ai-assistant" medium — a side effect that's easy to miss.
It's the first time AI traffic measurement goes from manual project to factory standard. That's good news, no caveats. The caveats are in the scope.
Subscribe to the Madbotz newsletter to get the next analysis straight to your inbox. No spam, no noise — just new posts.
What It Covers — and What Slips Past It
To know what the channel groups, only one source matters: the live definition of the default group. According to Google's official documentation, "AI Assistants is the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok," and it "excludes Google's AI Overviews and AI Mode."
Two details in that definition are worth gold. First, the list has grown since launch — the May notes named ChatGPT, Gemini, and Claude; today's definition adds Deepseek, Copilot, and Grok. Second, it's a list of examples: according to Search Engine Journal, Google hasn't published the full list of recognized referrers or how it will update it.
Table 1 — where each AI source lands with the native channel. The last column, "What to do," is the decision you take away.
| AI source | With the native channel it lands in | Why | What to do |
|---|---|---|---|
| ChatGPT, Gemini (web, with referrer) | AI Assistant | Named in Google's live definition | Nothing — the native channel covers them on its own |
| Copilot, Deepseek, Grok | AI Assistant | Joined the live list after launch | Nothing — check your regex doesn't double-count them |
| Claude (web, with referrer) | AI Assistant | Named as an example in the May release notes | Nothing — the native channel covers it |
| Perplexity | Referral | Not in the live list; without the "ai-assistant" medium, normal rules apply | Keep your custom channel — it does group it |
| AI Overviews / AI Mode | Organic Search | The definition explicitly excludes them from the channel | Not separable by channel — watch it in Search Console |
| No referrer (ChatGPT Atlas, apps, copy-paste) | Direct | The channel's condition is the referrer; no signal, no classification | Server layer — no client-side layer sees it |
The quick read: the native channel does a good job covering referrer-carrying traffic from the sources Google recognizes. The three gaps — Perplexity, AI Overviews, and traffic without a referrer — aren't minor defects: for many brands they're exactly the sources that weigh the most.
The Perplexity case illustrates the underlying problem. Google's own custom channel groups guide includes Perplexity in its example regex for measuring AI assistants — but the native channel's live definition doesn't name it. Google decides its list; you don't.
Does It Replace the Custom Channel You Already Built?
No. And we're not saying that out of affection for our own tutorial — all four reasons are in Google's documentation.
They Coexist Without Stepping on Each Other
The default group and custom channel groups are separate dimensions. According to the custom channel groups documentation, your custom groups can be used as a primary or secondary dimension in the same reports that support the default group. Keeping both costs nothing: you choose which one to view in each report, and a standard property allows 2 custom groups in addition to the pre-defined one.
The List Is Under Your Control
In the native channel, the source list belongs to Google: you can't see it in full and you don't decide when a new source joins. In your custom channel, you decide — Google's own documentation recommends updating your regex "if URLs or the list of assistants you wish to measure change." When 2027's hot new assistant ships, your channel groups it the same day; the native one, whenever Google gets to it.
The regex and the domain list live in the AI traffic channel guide — we won't repeat them here.
So Is the Rule Order
Traffic is included in the first channel whose condition it matches, in the order you define. Google's documentation recommends moving your assistants channel above Referral — and above Organic Search if needed. In the default group, that order can't be touched.
And Retroactivity Is the Big Difference
According to the custom channel groups documentation, "custom channel groups can be applied to your reports retroactively" — create the channel today and it reclassifies your history. The native one works the other way around: the "ai-assistant" medium is assigned as incoming traffic is processed, so the channel fills up from its launch onward. According to TechWyse, acquisition reports reflect the new channel "going forward" — your pre-May AI traffic keeps the classification it was born with.
The layer framework ends up like this: the native channel is the floor — basic coverage with zero maintenance. The custom channel adds control — list, order, and retroactivity. Custom events mark the session to build audiences. And server-side measurement captures what no client-side layer sees.
Who is the native channel enough for? If all you need is the monthly volume of referrer-carrying AI traffic, the floor is plenty. If you report by source, build audiences, or need your history, the other layers aren't optional.
A practical test to decide with your own data: open Traffic acquisition and compare the AI Assistant channel against your custom channel over the same period. If the numbers are nearly identical, the native channel covers the sources you care about; if your channel groups more — Perplexity is usually the difference — there's your evidence that you still need it.
What No Channel Sees
Here's the part no launch solves: a channel — native or custom — classifies with the signal that arrives. When traffic arrives without a referrer, like ChatGPT Atlas and agentic browsers, the session lands in Direct with the native channel and with the custom one alike.
It's not an oversight by Google. According to Search Engine Journal, assistant traffic arriving without a referrer header "still lands in Direct" — mobile apps, embedded browsers, copied-and-pasted links. And according to TechWyse, it's "a structural limitation of how browsers and apps handle referrer data, not a platform-specific problem."
Channels classify acquisition; they don't rescue a signal that doesn't exist. For that slice of traffic, the answer lives in another layer — server-side measurement, which sees the raw request before the trimming.
And one layer further up sits the cause of it all: if the models don't cite you, there's no traffic to classify — well or badly. That presence is watched with multi-LLM monitoring, and it's the work that comes before any channel.
Frequently Asked Questions
Do I have to turn on the 'AI Assistant' channel in GA4?
No. It's part of the Default Channel Group since May 13, 2026, and it shows up in your acquisition reports on its own, with zero configuration. If your property receives referrer-carrying traffic from a recognized assistant, you're already seeing it.
Why doesn't my Perplexity traffic show up in the 'AI Assistant' channel?
Perplexity isn't among the examples in Google's live definition, and Google doesn't publish the full list of recognized referrers. Without the "ai-assistant" medium, that session follows the normal rules and lands in Referral. A custom channel group does group it wherever you decide.
Does the 'AI Assistant' channel reclassify my historical data?
The "ai-assistant" medium is assigned as incoming traffic is processed, so the channel fills up from its launch onward; Google hasn't announced any reclassification of historical data. Custom channel groups, by contrast, can be applied to your reports retroactively according to the official documentation.
Can I delete my custom channel now that the native one exists?
You shouldn't. The default group and custom groups coexist as separate dimensions in the same reports, so you lose nothing by keeping both. The custom one gives you what the native one doesn't: control over the source list, control over rule order, and retroactivity.
Closing
Three ideas to take with you:
- The native channel is a real floor: ChatGPT, Gemini, Copilot, Deepseek, or Grok with a referrer get classified on their own, with zero configuration.
- The gaps are still there: Perplexity lands in Referral, AI Overviews stay inside Organic Search, and whatever arrives without a referrer, in Direct.
- Your stack isn't obsolete: the custom channel gives you control and retroactivity, custom events mark sessions for audiences, and server-side sees what the client doesn't.
A channel — native or custom — only classifies the traffic that already reaches your site. The cause comes earlier: whether you show up in AI answers or not. You measure that with the AI Visibility Score, the 130+ check item engine we analyze every site with.