How to Track AI Search Traffic in GA4

GA4 now has a built-in AI Assistant channel, added in May 2026, that pulls ChatGPT, Gemini, Copilot and similar out of Referral. It is not retroactive and it excludes Google’s AI Overviews. To see AI traffic before that date, or to control the list yourself, build a custom channel group matching the AI referrer hostnames on Session source.

Until recently, a visit from ChatGPT looked like nothing in particular in Google Analytics. It was a referral from a domain most owners had never thought to look for, sitting below the fold of the acquisition report next to a spam bot and a forum link. Or it was Direct, which is where analytics puts everything it cannot explain. That has changed, partly.

Why AI referrals never showed up as Organic

GA4 sorts traffic into channels using source and medium. Source is usually the referring hostname; medium is how the visit was categorized. Organic Search is a specific combination — the source has to be a domain GA4 recognizes as a search engine, and the medium has to be organic.

A click out of a ChatGPT answer is a plain link. The browser sends chatgpt.com as the referrer, GA4 sees a hostname it has no search-engine record for, and files the session as Referral with medium referral. Nothing is broken. The taxonomy predates the behavior.

The Direct problem is worse and has a different cause. Referrer headers get stripped in transit — in-app browsers, desktop apps, links copied out of an answer and pasted into a new tab. When the referrer is gone, the session lands in Direct permanently. No channel group recovers those, because the data never arrived.

What GA4 added, and its three limits

On May 13, 2026, Google added an AI Assistant channel to the default channel group. Google’s default channel group documentation defines it as traffic arriving “from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok,” and states plainly that it “excludes Google’s AI Overviews and AI Mode.” Under the hood, GA4 rewrites the medium to ai-assistant when the referrer matches its internal list.

This is a real improvement and you should check for it in your Traffic acquisition report before building anything. But three limits matter.

It is not retroactive

Sessions before mid-May 2026 keep the channel they were assigned at the time. Your AI traffic from last year is still sitting in Referral. Year-over-year comparison on the default channel group will show a channel that appears to have materialized out of nothing.

The list is Google’s, and it is not published

Google names five examples and does not publish the full set of hostnames behind the channel. You cannot audit it, and you will not be told when it changes. Whether Perplexity is included is not documented either way — check your own Source data rather than assuming.

Medium rewriting can surprise you

Existing segments or audiences keyed on medium equals referral will now miss this traffic, because it reports as ai-assistant. Worth checking before you conclude a channel collapsed.

Building the custom channel group

A custom channel group applies retroactively, which is the main reason to build one even now that the native channel exists. Google’s custom channel groups documentation confirms they “can be applied to your reports retroactively.” Standard properties get two custom groups beyond the default; Analytics 360 gets five.

Open Admin, then Data display, then Channel groups.
Click Create new channel group. Name it something you will recognize in a dimension picker — “Channel group with AI” is fine.
GA4 pre-loads a copy of the default channels. Click Add new channel and name the new channel AI Search.
Set the first condition to Source, operator matches regex, and paste the pattern below.
Add a second condition with OR: Default channel group exactly matches AI Assistant. This picks up anything Google classifies that your list missed.
Drag the AI Search channel above Referral and above Organic Search. This is the step people skip. GA4 assigns each session to the first channel it matches in list order, so a channel sitting below Referral will never fire.
Save. Give reports up to a day to reprocess.

The regex

GA4’s regex match is unanchored, which is deliberate here — it catches www.perplexity.ai and subdomains without extra work. It also means a loose entry can over-match, so before adding anything, sort Referral traffic by Source and confirm the hostname is really there. Do not paste in a hundred-domain list you found somewhere. Most of those are AI company marketing sites and API endpoints that will never send you a human.

The AI Overviews blind spot

No configuration solves this one. When someone clicks a link inside a Google AI Overview or AI Mode answer, the referrer is Google, the medium is organic, and the session is Organic Search. It is indistinguishable from a click on a blue link.

Google confirms the same is true in Search Console. Its AI features documentation states that sites appearing in AI features “are included in the overall search traffic in Search Console” and are reported in the Performance report within the Web search type.

There is now a partial workaround. Google launched a Generative AI performance report in Search Console in June 2026, breaking out impressions and clicks from AI Overviews and AI Mode. It is rolling out gradually, and it lives in Search Console rather than GA4, so you cannot join it to conversions. It is still the only first-party read on AI Overviews performance that exists.

The Looker Studio view

Create a GA4 data source and refresh the connection so the schema updates. Custom channel groups are exposed as dimensions in the GA4 connector, though you may need to reconnect before they appear. If yours does not show up, the fallback is a calculated field: a CASE statement using REGEXP_MATCH(Session source, '...') with the same regex, returning “AI Search” and letting everything else fall through.

Build four things and stop:

A time series of AI Search sessions, weekly, going back as far as you have data. The custom group is retroactive, so this works.
A table of Session source within AI Search, so you can see which assistants send traffic. This is where you find hostnames to add to the regex.
Landing page by sessions and key events for AI Search only. AI assistants tend to send people deep into a site rather than to the homepage.
Engagement rate and key event rate for AI Search against Organic Search. Compare quality, not volume — volume will be small for a long time.

What you still cannot measure

Referrer-stripped sessions. App and in-app browser traffic lands in Direct and stays there.
Clicks from AI Overviews and AI Mode. Organic Search in GA4, with no separation available.
Citations that produce no click. If an assistant names your business and answers the question completely, that is influence with zero measurable trace. This is most of what AI search does.
Whether you were mentioned at all. GA4 measures arrivals. It cannot tell you that an assistant recommended a competitor instead.

The honest position is that the channel group tells you AI traffic exists and roughly how it behaves once it lands. It does not tell you how you are performing in AI search. Anyone selling that distinction as solved is overselling it.

Do it in this order

Check Traffic acquisition for an AI Assistant channel. If it is there, you already have partial coverage and no work to do for current traffic.
Sort Referral traffic by Source over the last twelve months and find the AI hostnames actually sending you visits.
Build the custom channel group with the regex, add the OR condition on the native channel, and order it above Referral.
Confirm it is working by comparing AI Search sessions against the raw Referral hostname numbers for the same period.
Check Search Console for the Generative AI performance report.
Build the Looker Studio view. Review monthly, not weekly — the numbers are small enough that weekly movement is noise.

One caveat on effort. If AI sources send you a handful of sessions a month, this is a thirty-minute setup and a monthly glance, not a project. The reason to do it now is that the custom group is retroactive and the native channel is not — setting it up today gives you a trend line you cannot reconstruct later.