A GA4 Custom Channel Group for AI Sources
GA4 buries AI assistant traffic in Referral. A ten-minute custom channel group isolates it into its own reportable line — and what that number can and can't tell you.
By default, GA4 scatters traffic from AI assistants across Referral and Organic Search, so you can’t see how much of your traffic comes from AI engines. A custom channel group fixes this: you define a channel that captures sessions whose source matches the AI engines you care about, and from then on AI traffic reports as its own line. It takes about ten minutes to set up and turns an invisible, growing traffic source into something you can actually report on and trend.
Key takeaway
- GA4 lumps AI assistant traffic into Referral by default, hiding a channel that’s growing quickly.
- A custom channel group with a source-match rule isolates AI traffic into its own reportable line.
- Custom channel groups apply going forward and to historical data in most reports, but keep your definition stable so trends stay comparable.
Why the default reporting fails you
When someone clicks a citation in ChatGPT, Perplexity or Copilot, GA4 sees a referral from that domain and files it under Referral alongside every other referring site. Some AI-adjacent traffic can also land in Organic Search or Direct depending on how the link is passed. The result is that a channel many businesses now care about — AI-sourced visits — has no line of its own, and answering “how much traffic are we getting from AI?” means manually digging through referral sources every time. A custom channel group solves this permanently.
~10 minutes
Roughly how long it takes to create an AI channel group in GA4 — a one-time setup that converts an invisible, fast-growing traffic source into a reportable channel you can trend month over month.
Source — GA4 configuration practice
Setting it up
- Open channel group settings. In GA4, go to Admin, then Data display, then Channel groups. Create a new channel group (or copy the default one so you keep the standard channels intact).
- Add a new channel. Name it something clear like “AI Assistants” and place it above Referral and Organic Search in the ordering, since GA4 applies rules top-down and the first match wins.
- Define the match rule. Set a condition on Source matching a regular expression covering the AI domains you want — chatgpt.com, chat.openai.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai and similar.
- Save and verify. Check your reports after saving, and confirm sessions are landing in the new channel rather than Referral.
Choosing which sources to include
Include the assistants your audience actually uses, and keep the list documented so you know exactly what the channel represents. New AI products appear regularly, so review the list periodically and add sources as they become relevant. When you do add one, note the date — a jump in AI traffic caused by broadening the definition is not the same as a jump caused by growing visibility, and you’ll want to be able to tell the difference when reporting. Consistency of definition is what makes the trend trustworthy.
What this channel can and can’t tell you
The channel measures clicks from AI answers — genuinely useful for showing AI-sourced sessions, their conversion behaviour and how the channel is trending. What it cannot measure is the much larger share of AI visibility that never produces a click: being cited, named or recommended in an answer the user acts on without visiting. So treat AI referral traffic as one input alongside share of citation, not as the verdict on your AI visibility. A brand can be heavily cited and show modest referral numbers; that’s a normal outcome, not a failure.
Frequently asked questions
How do I track AI traffic in GA4?
Create a custom channel group under Admin → Data display → Channel groups, add a channel named something like “AI Assistants,” place it above Referral in the ordering, and define a Source condition matching the AI domains you care about — chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai and similar. Save, then verify sessions appear in the new channel.
Why doesn’t GA4 show AI traffic by default?
Because GA4’s default channel definitions predate the growth of AI assistants, so clicks from AI answers get filed under Referral alongside every other referring domain, with some landing in Organic Search or Direct. There’s no built-in AI channel, which means a fast-growing traffic source has no line of its own until you create one.
Which AI sources should I include?
The assistants your audience actually uses — commonly ChatGPT, Perplexity, Gemini, Copilot and Claude domains. Document your list so you know what the channel represents, review it periodically as new products appear, and note the date whenever you add a source. That way you can distinguish a traffic jump caused by broadening the definition from one caused by genuinely growing visibility.
Does AI referral traffic measure my AI visibility?
Only partly. It captures clicks from AI answers, but not the larger share of AI visibility that produces no click — being cited, named or recommended in an answer the user acts on without visiting your site. Use AI referral traffic as one input alongside share of citation. A heavily-cited brand can show modest referral numbers, and that’s a normal result rather than a failure.
The bottom line
Ten minutes in GA4 turns AI traffic from an invisible slice of Referral into its own reportable channel. Create a custom channel group, add an AI Assistants channel above Referral, match on the source domains that matter to you, and keep the definition documented and stable. Then read it for what it is — the click-through portion of AI visibility, best reported alongside your share of citation.
We set up AI traffic tracking and citation measurement together, so reporting shows the full picture. Part of our AI Visibility service.
