AI Referral Traffic in GA4: How to Measure It Properly

Saad Raza

1 day ago

Cover graphic for the AI search guide "AI Referral Traffic in GA4: How to Measure It Properly" by Saad Raza SEO

To measure AI referral traffic in GA4, find sessions whose source is an AI assistant such as chatgpt.com or perplexity.ai, then group them in a custom channel group that matches those domains with a regular expression on Source. Put it above Referral, and expect an undercount, because some AI visits arrive with no referrer.

People are using these tools in numbers that justify the effort: Pew Research Center found that 34% of U.S. adults said they had ever used ChatGPT in 2025, about double the share in 2023, including 58% of adults under 30.

What counts as AI referral traffic

AI referral traffic means visits that begin when someone clicks a link inside an AI assistant’s answer: a source link in ChatGPT, a citation in Perplexity, a link beside a Copilot or Gemini response. In GA4 these visits show up like any other referral, with a source (the domain the visitor came from) and a medium (usually “referral”). GA4 has no built-in “AI” channel in its default grouping, so out of the box they sit inside Referral, or sometimes inside Direct when the referrer is lost.

That is the first thing to understand. You are not looking for a switch to turn on. You are building a definition, and then being honest about its limits. The measurement is a floor, not a total. If you want the other half of the picture, which is how often assistants mention you without sending anyone, my guide to tracking brand visibility in AI assistants covers it.

Step 1: See what is already arriving

Before you build anything, look at your own data. In your GA4 property, open the acquisition reports that show session source and medium, or build a free-form exploration with a source dimension in the rows and sessions, engaged sessions and key events as values. Filter to the last 90 days and scan the list for assistant domains. Common ones to look for include chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com and claude.ai, but the exact values depend on how each product sends visitors, so trust your own list over mine.

OpenAI states in its publishers and developers FAQ that ChatGPT automatically includes the UTM parameter utm_source=chatgpt.com in referral URLs, so ChatGPT search visits are designed to be identifiable in analytics. I could not verify an equivalent statement for every other assistant, so I do not assume one. Check what each actually sends by clicking through to your own site from a test answer and reading the source GA4 records.

Step 2: Create a custom channel group

A channel group is, in Google’s words, a set of rule-based categories of your traffic sources. GA4 lets you copy the default group and add your own channels. Google’s help page on traffic-source dimensions and channel groups even uses an “AI assistants” channel as its worked example, defined with a “matches regex” condition. Here is the process in plain steps:

Open Admin, find Channel groups, and create a new group by copying the default one. Name it clearly, for example “Default plus AI”.
Add a new channel called “AI assistants”.
Set a condition on the Source field with the operator “matches regex” and a pattern listing the domains you found in step 1.
Move the “AI assistants” channel above Referral. Google notes that traffic is placed in the first channel whose definition it matches, so order decides everything.
Save, then pick your new group as the dimension in Acquisition reports or as a secondary dimension elsewhere.

A starting pattern might look like this, which you should edit to match your own data:

Keep the pattern tight. A loose pattern such as “gemini” or “ai” can sweep up unrelated sites, and that quietly corrupts your numbers. Google’s sample pattern is deliberately broad; I prefer to list the domains I have actually seen and review the list every quarter, because assistants change their domains and new ones appear. Google’s page also tells you to update the expression as the list of assistants changes.

Two practical points from the help page: custom channel groups can be applied to your reports retroactively, so you can build one today and see history, and the number of custom groups per property is limited (the page gives different limits for standard and 360 properties), so do not waste a slot on a throwaway test.

Step 3: Report it in a way people can trust

Once the channel exists, report on quality as well as quantity. Ten visits from an assistant who read your pricing page can matter more than a hundred who bounced from a blog post. A short table is enough:

Metric	Why it matters
Sessions from AI assistants	Your floor for AI-driven visits
Landing pages	Shows which pages assistants cite and send people to
Engaged sessions and engagement time	Tests whether the visitors found what they expected
Key events (enquiries, calls, purchases)	Connects the channel to outcomes, however small the volume
Source breakdown	Shows which assistants matter for you

The landing-page view is the most useful. If the same three articles receive nearly all your assistant visits, those are the pages assistants find quotable. Study how they open, how they define terms and how they present facts, then bring the same clarity to your other pages. For how assistants choose sources, see my notes on ChatGPT search SEO, and for Microsoft’s side, Bing SEO for AI search.

What GA4 cannot tell you

This is where honest reporting earns trust. Several limits are built in:

Missing referrers. Some clicks arrive with no referrer, for example from certain apps, or when a person copies a link out of an answer and pastes it. Those visits land in Direct, and no regular expression can rescue them.
AI Overviews and AI Mode are not separate. Google’s documentation on AI features and your website says traffic from these features is included in overall Search Console data. In GA4 those visitors arrive from Google, so as far as I know you cannot split them from ordinary Google organic traffic with a channel rule. Treat any tool that claims to do so with caution and ask how.
Tagging varies by product. A UTM that exists today may change, and not every assistant adds one.
Influence without a click. A person may see your brand in an answer, then search for you by name a week later. That visit will look like Direct or branded organic traffic. This is the same attribution gap behind zero-click search.
Small numbers. On many sites AI visits are a tiny share of sessions. Percentages from tiny samples swing wildly, so report counts and trends over several months.

My rule is to label the channel “AI assistants (measured)” in client-facing material, so nobody reads it as total AI influence.

A simple cross-check that makes the data more believable

Pair the GA4 numbers with two things. First, a sample of your prompts run manually, as in the visibility tracking process, so you know whether you appear in answers at all. Second, branded search impressions in Search Console, to see whether name searches rise as your visibility improves. If assistant visits are rising, prompts show you cited, and branded searches are steady or rising, the story is coherent. If one of the three disagrees, look into it before reporting a win.

Imagine, as an illustration only, a Karachi accounting firm whose GA4 shows eight sessions a month from assistants, all landing on one guide to filing requirements. The sensible conclusion is not “AI is big for us”. It is “one guide is quotable, so improve and extend that kind of page, and keep measuring”. That is a decision rather than a boast.

Keep the setup healthy

Review the regex every quarter against your source list. Check that your landing pages load without blocking prompts or security challenges for ordinary visitors, since a broken experience wastes the rare visit that arrives. Document your definition in one paragraph so a future colleague knows what the channel includes. On my own site, rebuilt in October 2026, I wrote the definition down before looking at any numbers, so I could not quietly move the goalposts later. If you want analytics set up properly alongside crawlability and structured data, my technical SEO services include that groundwork, and the page-level advice in my guide to optimising for AI Overviews applies to the pages that win citations. The wider picture is in the GEO hub.

Questions people ask about AI referral traffic in GA4

Does GA4 have an AI channel by default?

Not in the default channel group as far as I know. You create one with a custom channel group, which Google’s own help page demonstrates with an “AI assistants” example. Without it, these visits sit in Referral or Direct.

Why does my AI traffic look so small?

Partly because assistants send fewer clicks than classic search, and partly because some visits lose their referrer and land in Direct. Treat your figure as a minimum.

Can I separate AI Overviews traffic from normal Google organic traffic?

Not reliably. Google says these features are counted within overall Search Console data, and the clicks arrive in GA4 as Google traffic. Be wary of anyone presenting a precise split without explaining the method.

Will a custom channel group change my historical data?

Google’s help page says custom channel groups can be applied to reports retroactively, so you can see earlier months once the group is saved. Raw data stays untouched.

If you would like your GA4 reviewed, with a clean AI channel and sensible reporting, contact me for a free audit and we can look at your actual source list together.

More AI search guides: start with the generative engine optimization guide, then go deeper: