Your website is already getting traffic from AI tools. The good news is that, as of May 2026, Google Analytics 4 will finally show you some of it without any setup. The catch is that the native view captures only part of the picture.
When a potential client asks ChatGPT to recommend a firm in your category and your company comes up in the answer, that person often clicks through to your site. For years, that visit got buried inside GA4's generic "Referral" bucket, or worse, dumped into "Direct" as if they had typed your URL from memory. You had no clean way to see it.
In May 2026, Google changed that. GA4 now has a built-in AI Assistant channel that automatically separates a chunk of this traffic out for you. This guide covers what that native channel does, the significant gaps it leaves, and how to build a complete view, including a way to have Claude set the whole thing up for you.
What GA4's New AI Assistant Channel Does
On May 13, 2026, Google added a native AI Assistant channel to GA4's Default Channel Group, with broad availability reaching most properties by early June. It requires no configuration. When GA4 recognizes a visit referred by a supported AI assistant, it automatically tags that session and slots it into the AI Assistant channel in your standard acquisition reports.
To find it, go to Reports > Acquisition > Traffic Acquisition and set the primary dimension to Session default channel group. You should see "AI Assistant" listed alongside Organic Search, Direct, Social, and Referral.
For a fast read on whether AI tools are sending you traffic, this is genuinely useful, and it took zero effort on your part. But treat the number as a floor, not a ceiling.
What the Native Channel Misses (This Is the Important Part)
The native channel cleans up the easy cases. It does not solve the underlying measurement problem. Three gaps matter:
Not every AI tool is included. Google's official definition covers ChatGPT, Gemini, DeepSeek, Copilot, and Grok. Claude and Perplexity are not on that list, so their referrals still land in the Referral bucket, and Google's own AI Overviews and AI Mode get counted as Organic Search rather than as AI traffic.
Most AI traffic has no referrer at all. This is the big one. An estimated 60 to 70% of real AI-driven sessions arrive with no referrer data, usually because the click came from a mobile app that strips the referrer. (Loamly's 2026 analysis of 446,405 visits put the figure at 70.6%.) Those visits fall into Direct, and the native channel cannot recover them. No tool can fully recover them today.
It does not backfill. The classification is forward-only. GA4 will not retroactively reclassify the AI traffic you received before the channel went live. If you want any historical view, you have to analyze it separately.
The takeaway: the native channel is a convenience, not a complete measurement system. To see Perplexity, to control your own definition of "AI traffic," and to build a record you can trust over time, you still want a custom channel group running alongside it.
How to Build a Custom AI Channel Group
This takes about 15 minutes and gives you a view you control. It runs in parallel with the native channel, so you can compare the two.
Step 1: Open Channel Groups. In GA4, go to Admin > Data display > Channel groups. You will see Google's default group. Do not edit it. Click "Create new channel group" and name it something clear, like "AI Traffic (2026)."
Step 2: Add an AI channel with a regex rule. Add a new channel, name it "AI Referral," and set the condition to Source > matches regex, then paste a pattern covering the major sources:
chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|grok\.com|you\.com|meta\.ai
Update this quarterly as new tools emerge and as platforms change domains. A single Source condition is all you need here. GA4 combines condition groups with AND rather than OR, so adding a second group such as Medium > exactly matches > (not set) would force every session to satisfy that too, which would wrongly exclude AI referrals that arrive with a medium. The Source > matches regex rule on its own already captures your AI traffic regardless of medium, including the no-referrer sessions that show up as (not set).
Step 3: Reorder the channel. This is the step most guides miss. GA4 assigns each visit to the first matching channel from the top of the list down. If your AI Referral channel sits below Referral, GA4 will file those visits as referrals before your rule ever fires. Drag your AI Referral channel above Referral, then apply and save.
Step 4: View it. Go to Reports > Acquisition > Traffic Acquisition and switch the channel group selector at the top of the table to your new group. One advantage over the native channel: when you view reports through a custom channel group, GA4 applies its rules to your historical data, so you can see past AI traffic reclassified retroactively, not just from today forward.
A couple of technical notes. Free GA4 properties allow only two custom channel groups (GA4 360 allows five), so if you are already at that limit you will need to free a slot first. And since the native AI Assistant channel and your custom rule can both capture the same sessions, read one or the other rather than adding them together.
At Falls River Media, we set up AI referral tracking as part of every analytics engagement, native channel plus a custom group for the full picture.
What to Look For in Your AI Traffic Data
Once both views are running, compare AI traffic against your other channels:
Trend line. The absolute number is small today. Track the growth rate, not just the volume.
Engagement and session duration. AI-referred visitors are often pre-qualified. They have already read an AI summary about you before clicking. They tend to spend longer on site and view more pages than typical search visitors.
Landing pages. Which pages are AI tools sending people to? That tells you which of your content AI systems are actually citing, and where your gaps are.
Conversion rate. Track your key action, whether that is a form fill, a demo request, or a contact. AI referral visitors frequently convert at higher rates than social traffic because they arrive with intent.
What This Means for Your Strategy
If AI tools are sending you traffic, that is a signal your content is being cited in AI-generated answers. That is worth investing in. For B2B companies selling into considered purchases, this channel represents high-intent discovery: someone asked an AI assistant for a recommendation, and you were in the answer.
The teams that set up clean measurement now, while volume is small enough to read clearly, will have a year or more of trend data by the time this becomes a meaningful share of traffic. The ones who wait will start from zero.
Frequently Asked Questions
Does GA4 track AI traffic automatically now?
Partly. Since May 13, 2026, GA4 includes a native AI Assistant channel that automatically separates traffic from assistants like ChatGPT, Gemini, DeepSeek, Copilot, and Grok, with no setup. It does not catch every source (Claude and Perplexity are not on Google's list and still land in Referral, and AI Overviews count as Organic Search), and it cannot recover the majority of AI visits that arrive with no referrer.
Do I still need a custom channel group?
For most businesses, yes, if you want a complete and durable picture. A custom channel group lets you include sources the native channel misses, define AI traffic on your own terms, and run a consistent record you control. The two work well side by side.
Does setting this up require code changes?
No. Both the native channel and the custom channel group live entirely in the GA4 interface. The custom group reclassifies traffic GA4 is already collecting. There is no tracking code to change.
Can AI tools really see all of my AI traffic?
No tool can today. Because so much AI traffic arrives with no referrer, every measurement approach captures a trackable portion and misses the rest. That is still enough to identify trends and measure growth, which is the point.
Is tracking AI traffic the same as tracking whether AI mentions my brand?
No, and it helps to keep them separate. The GA4 setup here measures traffic: the people who clicked through to your site from an AI tool. A different category of tools, AI visibility or AEO platforms, measures whether your brand appears in AI answers in the first place, and they do it by running sample prompts against the models on a schedule, not by watching real conversations, which no one can see. Traffic tracking tells you what happened on your site. Visibility tracking estimates how often you show up in answers. Teams that care about AI discovery usually want both.
