Tracking AI Referral Traffic in GA4

To track AI referral traffic in GA4, create a custom channel group with a channel that matches AI referrers on their source domains, and order it above Referral so those sessions get captured first. This pulls visits from ChatGPT, Perplexity, Gemini and others out of the generic Referral and Direct buckets and into a channel you can actually report on. It’s the single most useful GA4 change for AI visibility — with important limits you need to state honestly. This post walks through the exact setup.

Why AI traffic hides in your GA4 by default

By default, GA4 has no idea what “AI traffic” is. When someone clicks a link in an AI answer that does pass a referrer, GA4 files it under generic Referral alongside every other site. When the click passes no referrer — which is common — it lands in Direct, indistinguishable from someone typing your URL. So without a custom setup, your AI traffic is scattered invisibly across two buckets and you can’t report on it at all.

Creating a dedicated AI channel fixes the visible portion: it gathers the referrer-passing AI clicks into one named channel you can track over time. It can’t recover the no-referrer portion, but isolating what is trackable is a large step up from nothing.

Step one: create a custom channel group

In GA4, go to Admin, then under the property find Channel groups, and create a new custom channel group (a copy of the default is a good starting point so you keep all the standard channels). This custom group is where your AI channel will live, leaving GA4’s default channel grouping untouched for other reporting.

Custom channel groups apply going forward and, in current GA4, can also reprocess historical data in many reports — but confirm the behaviour in your property, since availability varies. Either way, set this up as early as possible so your trend line starts accumulating.

Step two: add the AI Referral channel

Inside your custom channel group, create a new channel named something clear like “AI Referral” or “AI Assistants.” Set its condition to match the source against a regular expression covering the main AI referrer domains. A practical starting regex:

chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|
copilot\.microsoft\.com|claude\.ai|meta\.ai|you\.com

Use it as a single line (the line break above is only for readability). The condition should match “Source matches regex” against that pattern. This tells GA4: any session whose source is one of these AI domains belongs in the AI Referral channel. Keep the list current — new engines appear, and you’ll want to add their domains as they gain usage.

Step three: order it above Referral

This step is where most setups quietly fail. GA4 evaluates channels in order and assigns each session to the first one it matches. Since AI domains are technically referrers, the default Referral channel will claim them before your AI channel ever sees them — unless your AI channel sits higher in the order.

Drag your AI Referral channel above the Referral channel in the custom group’s ordering. Now AI sessions match your channel first and land where you want them, while all other referrers fall through to the standard Referral channel as normal. Without this ordering, your AI channel will read zero no matter how correct the regex is.

Step four: report and monitor

With the channel live, use it in your reports by switching the channel grouping to your custom group wherever you view acquisition data. Track AI Referral sessions over time, and — more importantly — the conversions and engagement from that channel, since the value of AI traffic is in outcomes, not raw visits. Some evidence suggests AI-referred visitors arrive pre-informed and can convert well, so watch quality, not just volume.

Set a monthly review alongside your prompt testing, so your downstream traffic data and your citation data move together in one picture.

The blind spot you must disclose

Be honest, especially with clients, about what this misses. A large share of AI-referred sessions arrive with no referrer and land in Direct, where this channel can’t catch them. Clicks originating inside mobile apps are largely untrackable. And AI Overview clicks are attributed to normal Google organic, not to any AI channel. So your AI Referral channel is a reliable floor and a good trend indicator, but it materially understates true AI-driven traffic. Report it as “measured AI traffic,” never as the complete number.

Frequently asked questions

The bottom line

Isolating AI traffic in GA4 is a four-step job: create a custom channel group, add an AI Referral channel with a regex of AI domains, order it above Referral, and report on it monthly. The ordering step is the one everyone misses. Do it right and you get a real, trackable floor for AI-driven visits and conversions — just remember to present it honestly as a floor, not the whole story.

We set up AI traffic tracking and fold it into your monthly reporting as part of our AI Visibility service.