How to Track AI Referral Traffic in GA4

For the past two years, Google Analytics has treated AI-assistant traffic as an afterthought, placing visits from ChatGPT and Perplexity in a general "Referral" bucket with all other websites that happen to link to you. On May 13, 2026, Google released a native "AI Assistant" default channel group, which provided a genuine starting point for anyone attempting to measure AI referral traffic in GA4 for the first time.
In addition to a custom channel group for platform-level information that the original channel does not provide, we set this up on klimb.co.in to see what it truly looks like in practice. We made a configuration error along the road that silently emptied out every custom channel we had created. It's beneficial to be aware of this defect before you encounter it.
What is GA4's native AI Assistant channel, and what does it track?
Google added GA4's AI Assistant channel as a default channel group on May 13, 2026. It requires no setup and automatically identifies sessions from recognised AI chatbot referrers. When GA4 recognises a referral, it marks the campaign field (ai-assistant), groups the session under the AI Assistant channel in Default Channel Group reporting, and assigns the medium ai-assistant.
A GA4 channel group: what is it? A channel group is a collection of guidelines that classifies each session according to the source of the traffic, such as Organic Search, Direct, or Referral. GA4 allows you to create custom Channel Groups with your own constraints, but it comes with a Default Channel Group that is difficult to modify.
Although it hasn't released the complete list of referrers, Google lists ChatGPT, Gemini, and Claude as acknowledged examples. The key reason this replaced the majority of the manual workaround teams were doing previously is that all three modifications occur automatically on any property without requiring editor access or a regex pattern.
How did people track AI traffic in Google Analytics before this existed?
Prior to this shipping, creating a new channel group by hand using a regex pattern that matched recognised AI domains was the only method to distinguish AI traffic from general referrals. This was explained in a widely shared tutorial from November 2025: copy the default channel group and add a channel that follows a pattern like.Drag chatgpt.|.copilot.|.perplexity.|.gemini. above Referral to give it precedence.
There were actual limitations to such workaround. The regex required editor-level access, required manual maintenance when platforms switched domains, and GA4's two-custom-channel-group cap meant giving up one of only two slots to AI tracking. For the platforms it recognises, the native channel eliminates the maintenance load. The gaps below occur because it does not completely eliminate the necessity for a custom group.
What does GA4's native AI Assistant channel actually miss?
Only ChatGPT, Gemini, and Claude are consistently tagged by the original channel. The rollout itself was gradual rather than simultaneous, thus some properties saw it weeks later others. Other significant platforms, such as Perplexity, Copilot, and DeepSeek, frequently still land in generic Referral.
Referrer reliance is the larger disparity. Any AI click that comes in without a referrer header ends up in Direct, regardless of whether the user copied and pasted the link or the app removed it. Estimates from the community vary widely, ranging from 35% to 70% of AI traffic, but the direction is constant: the AI Assistant channel is a floor, not the actual total.
Another confusion that needs to be addressed directly is that AI Overviews and AI Mode results are still considered Organic Search since they are generated internally by Google rather than via an outside referral. This channel alone will undercount your overall AI-driven traffic twice over, once for platforms you missed and once for AI search results that would never have appeared at all.
In our opinion, the native channel is actually sufficient on its own if you only care about a general trend line and the majority of your traffic originates from ChatGPT, Gemini, or Claude. You'll need the special setup below if you want to discover which particular platform sent visitors or which of your sites are truly being mentioned.
How do you build a custom channel group to track AI referral traffic in GA4?
Since the Default Channel Group cannot be significantly altered, you create a custom channel group under Admin. Additionally, for platforms that the native channel does not yet cover, this is how you link AI traffic statistics to Google Analytics. Navigate to Admin (the gear symbol) in GA4, then select Data display under Property, followed by Channel groups.
Click "Create new channel group" and give it a name like "AI Engines."
Click Add new channel inside of it, name the channel after the platform (for instance, "ChatGPT"), and define a condition by selecting the dimension (Source is the easiest option), selecting an operator, and entering a value.
Instead of matching exactly, set the operator to matches regex. The next section goes into more detail on why that distinction is important.
For every platform you wish to isolate, repeat these steps. Based on what we developed and what appears in community discussions on this subject, a reasonable beginning list includes seven platforms plus two that need be added for more comprehensive coverage.
After adding all of your channels, click Save Group after dragging the group's channel order to place your AI channels above Referral.
You don't need to wait for new data to gather before examining previous AI traffic because a new custom channel group applies retrospectively to your property's entire history as soon as you save it. (Note: only custom groups apply retroactively; the default AI Assistant channel does not.)
What's the most common mistake that breaks a custom AI Assistant channel in GA4?
Choosing "matches exactly (=)" on the condition operator rather than "matches regex" is the error, and it fails silently. In this manner, we created seven channels (ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, and Meta AI), all of which displayed zero sessions during a 28-day and an 8-month period. In contrast, GA4's native AI Assistant bucket displayed 206 sessions during the entire 8-month period and 98 real sessions during the previous 28 days.
This is how it works. When you select "matches exactly," GA4 compares your full pattern - including pipe characters - to the source value as a single literal string. When a condition like chatgpt.com|chat.openai.com|openai.com is set to "matches exactly," it actually asks, "Is the source exactly equal to the text chatgpt.com|chat.openai.com|openai.com?" The condition fails every time, for every channel, and there is no error warning anywhere because that is never true for a real source value like chatgpt.com on its own.
Drilling into GA4's native AI Assistant bucket with "Session source" as a secondary dimension allowed us to find it. That revealed the true referrer: 147 of the 206 AI Assistant sessions during the entire 8-month period originated directly from chatgpt.com, a figure that ought to have matched our unique ChatGPT channel but wasn't shown there at all.
The solution is a one-field modification: for each channel condition, change the operator from "matches exactly" to "matches regex" while maintaining the same pattern values. Actual AI-referral traffic that is already coming in is appropriately attributed to the particular platform channel after being grouped into the generic native bucket.
How do you diagnose a GA4 channel showing zero traffic instead of guessing?
First, you should be aware that GA4 only shows dimension values that have nonzero data inside the date period you have chosen. A channel with no rows at all does not prove that the arrangement is flawed or that there is no AI traffic. Cross-referencing against a grouping you already know works is the true diagnostic technique; both of them are guesses.
Select either User acquisition (first-touch attribution) or Traffic acquisition (session-level attribution) under Reports > Life cycle > Acquisition.
"Session primary channel group (Default channel group)" is the default row dimension in the table. To view traffic broken down by your own channels, click that drop-down and change it to your custom group, such as "Session AI Engines."
drop down
To rule out a window that is just too tight, use the selector in the upper right corner to broaden the date range first if a channel displays no data.
Return to the default grouping, click the + next to the row dimension, look for Session source, and add it as a secondary dimension to see where the traffic is really arriving.
drop down
This divides the integrated AI Assistant bucket according to the actual referrer domain, which is precisely what revealed chatgpt.com concealed within it rather than our unique channel.
To directly filter by a channel or source name, use the search box located above the table. When there is a "No data available" result, GA4 verifies that it is a true zero rather than a display error.
We were able to identify the discrepancy without speculating that "no traffic exists" or "the regex must be incorrect" thanks to the combination of changing the report to your custom group and then adding "Session source" as a secondary dimension on the default grouping. The same view displays the custom ChatGPT channel picking up actual sessions that correspond to what was concealed in the native bucket when the operator is corrected.
Does AI-referred traffic actually convert better than organic search?
Yes, by a large margin, according to preliminary data, notwithstanding the modest sample sizes that have been made public thus far. According to community-reported research from r/GoogleAnalytics, the conversion rate of AI traffic is generally four to five times higher than that of organic search. One B2B example reported a conversion rate of about 16% for ChatGPT compared to about 1.8% for Google organic on the same site.
 
Consider that as guidance rather than a standard by which to make plans. The practical benefit of tracking AI referral traffic in GA4 in the first place is being able to measure your own conversion rate instead of borrowing someone else's. The data from a single B2B site won't transfer well to an e-commerce store or a local service firm. Even if the overall session count appears to be a rounding error when compared to organic search, low volume with a high conversion rate is still a legitimate signal worth keeping an eye on on your own property.
Should you use the native channel, a custom one, or both to track AI traffic in Google Analytics?
Instead of choosing one, run both side by side. Today, a significant portion of AI referrals are covered by the native AI Assistant channel, which requires minimal setup and accurately captures ChatGPT, Gemini, and Claude traffic. If you need platform-level information that the native channel cannot provide, want to identify platforms that are not on Google's approved list, or need a second data point to sanity-check against - exactly the cross-reference that identified our own misconfiguration - building a custom channel group is still worthwhile.
When creating a custom group, it's important to double-check the operator setting before accepting a "zero traffic" result. Before determining that there is no AI traffic on your website or that your setup is flawed, set it to match regex, check against the native channel's "Session source" breakdown, and expand your date range.
The more difficult part of the issue is bridging the gap between having analytics and a system that makes use of them by attempting to link this type of traffic data to meaningful SEO and content decisions rather than merely observing a new figure in a report.
GA4's AI Assistant channel measures the other half of the narrative for teams that are already monitoring whether their brand appears in ChatGPT, Perplexity, and other AI responses: if those mentions result in actual visits. Check out the AI visibility page to see how Klimb connects both sides, connects directly to your GSC (Google Search Console) and GA4 data (Google Analytics), and see the Google Analytics 4 integration for setup information.