In this piece: what AI referral traffic actually looks like in GA4 by default, the two ways to isolate it depending on your GA4 version, the ordering mistake that hides it even after setup, what to do with the number once you can see it, and the one check to run this week.
Most B2B SaaS founders have no idea how much AI referral traffic Google Analytics is quietly burying inside Referral or Direct, because GA4 has treated ChatGPT and Perplexity visits like generic traffic for years. Here's the direct fix: in mid-May 2026, Google added a native AI Assistant channel to GA4's Default Channel Group, and for properties that haven't gotten it yet, a manual custom channel group with the right regex does the same job in about ten minutes.
This matters now because a growing share of your buyers are asking an AI assistant for a recommendation before they ever type your name into Google. If that traffic stays invisible in your reporting, you can't tell which of your pages are actually earning those mentions, and you can't defend the time spent on content a spreadsheet insists isn't working.
What AI referral traffic looks like in GA4 right now
AI referral traffic is any session that arrives at your site because an AI assistant like ChatGPT, Perplexity, or Gemini pointed a user to your page instead of a traditional search result. By default, GA4 files that click under Referral if the tool passes a referrer, and under Direct if it doesn't.
Free ChatGPT users don't send referrer data at all, so an unknown share of your "Direct" traffic is quietly AI-driven, and there's no clean way to recover that history after the fact. Desktop citation links from ChatGPT have carried a utm_source=chatgpt.com tag since 2025, which is why filtering Session source for "chatgpt" surfaces rows like "chatgpt.com / referral" if you have any. Perplexity, Claude, and Copilot behave inconsistently, and mobile apps and in-app browsers routinely strip the referrer entirely. None of this means your setup is broken. It's the actual state of AI referrer tracking across the industry right now, and it's exactly why Google shipped a dedicated channel for it instead of leaving every property to solve it alone.
Two ways to isolate it, depending on your GA4 version
If your property already has the native AI Assistant channel, it needs no setup: GA4 auto-assigns an "ai-assistant" medium and buckets ChatGPT, Gemini, Claude, Copilot, Grok, and DeepSeek sessions into it automatically. If you don't have it yet, a custom channel group does the same job manually.
- Native AI Assistant channel: setup time is none, it either exists on your property already or it doesn't. Coverage: officially recognizes ChatGPT, Gemini, and Claude by name, with other assistants folded in but not fully documented; not applied retroactively to past data. Best for any property where it's already rolled out, which is worth checking before building anything by hand.
- Custom channel group: setup time is about ten to fifteen minutes. Coverage: whatever domains you put in your own regex, and it applies retroactively to historical data the moment you save it. Best for properties without the native channel yet, or founders who want to catch AI tools the native list doesn't cover.
To build the custom version:
- Go to Admin > Data display > Channel groups and create a new channel group.
- Add a new channel and name it "AI assistants."
- Set the condition to Source matches regex, and use a pattern covering at minimum ChatGPT, Gemini, Claude, Perplexity, and Copilot. Google's own help documentation publishes a working regex you can copy directly rather than writing one from scratch.
- Save the channel, then reorder the list so "AI assistants" sits above Referral.
- Open Traffic acquisition, set your new channel group as the dimension, and read the number.
The mistake that hides your AI traffic even after setup
The single most common failure is leaving the new channel below Referral in the list. GA4 assigns each session to the first channel it matches, top to bottom, so if Referral still sits above your AI assistants channel, every AI session that happens to carry a referrer gets claimed by Referral first, and your new channel reports zero even though the traffic exists.
The second failure is picking "contains" instead of "matches regex" when setting the condition, which silently narrows what counts as a match and drops variants you didn't anticipate. The third is trying to filter Session source directly in a standard report instead of building a channel group, which runs into a strict character limit long before you've listed every AI domain worth tracking.
What to actually do with the number once you can see it
Compare engagement rate and signup rate between your AI-referred sessions and your average organic session before deciding how much this channel deserves your attention. A small number of highly qualified sessions can outweigh a larger number of browsing ones.
Pull the specific landing pages your channel group shows the most AI sessions against, then check whether the first sentence under every subheading on those pages actually answers a question with zero surrounding context needed. That is the exact sentence an AI engine lifts into its answer, so those pages are worth rewriting before anywhere else on your site.
Treat an unexplained rise in Direct traffic as a signal, not noise. Line the spike up against the dates you published or refreshed a page. If the timing lines up, a real portion of that "Direct" bump is very likely AI referral traffic you can't see directly, and it's worth investigating rather than shrugging off as untrackable.
If you haven't yet built the weekly routine for actually earning more of these mentions in the first place, that's a separate exercise worth doing alongside tracking: see how to get your B2B SaaS mentioned by ChatGPT for the specific weekly steps.
What this looks like at seed stage, with real numbers
When Google announced the AI Assistant channel in mid-May 2026, it named ChatGPT, Gemini, and Claude as recognized referrers but did not publish a full list, which is exactly why keeping your own custom channel group running alongside the native one still catches assistants Google's list misses. The rollout itself has also been gradual and non-retroactive, so two companies checking their GA4 admin on the same day can get different answers about whether they even have the feature yet. Practitioners were already recommending manual UTM tagging on any link you personally place months before Google's native channel shipped, and that habit is still worth keeping for links AI tools won't tag for you.
Separately, industry analysis of AI search behavior found that a large share of B2B software buyers now start their research inside an AI chatbot rather than a traditional search box, and that a majority of searches across search engines end without any click at all because an AI-generated summary already answered the question. Neither of those numbers shows up anywhere in your GA4 reports by default. The only way to see your own version of that shift is the channel group you just built.
Your first move this week
Open Admin > Data display > Channel groups today and check whether AI Assistant already exists on your property. If it does, add it to your Traffic acquisition report and write down whatever number you see, even zero, as your baseline. If it doesn't exist yet, build the custom channel group above using Google's published regex pattern, save it, and reorder it above Referral before you touch anything else. Either way, you now have a number to watch instead of a blind spot to guess at.
Frequently asked questions
Does Google Analytics track AI traffic automatically now?
Since mid-May 2026, GA4 has included a native AI Assistant channel in its Default Channel Group that auto-classifies recognized referrers like ChatGPT, Gemini, and Claude. The rollout is gradual and not retroactive, so some properties still need a manual custom channel group in the meantime.
Why does AI referral traffic show up as Direct traffic?
Many AI tools, especially free-tier mobile apps and in-app browsers, don't pass referrer data, so GA4 has nothing to attribute the session to and defaults it to Direct. There's no way to fully recover this after the fact, only to reduce it going forward with UTM tagging on links you control.
What regex should I use for a custom AI channel group?
At minimum, cover ChatGPT, Gemini, Claude, Perplexity, and Copilot as source patterns, matched with "matches regex" rather than "contains." Google's own help documentation publishes a working example built for exactly this use case.
How much AI referral traffic should an early-stage B2B SaaS expect?
Expect it to be small relative to organic search today, but growing, and concentrated on a handful of pages that already answer a specific question clearly and directly. The trend and which pages are earning it both matter more than the raw number.
Should I block AI crawlers like GPTBot to protect my content?
Blocking AI crawlers keeps your content out of the exact answers that could cite you in the first place. Unless you have a specific competitive reason to hide a page, leaving AI bots unblocked is what makes any of this tracking worth doing at all.
Do I need a paid AI visibility tool to do any of this?
No. Everything above runs on GA4's own admin settings and reporting, which are already included in a free property. Paid tools add prompt-tracking and citation monitoring beyond what analytics traffic alone can show, which is a reasonable next step later, not a starting requirement.
Most founders will read this, agree with it, and never open their GA4 admin panel. The ones who check Channel groups today are the ones who'll have three months of real AI referral data by the time a competitor even asks the question. If you want a second pair of eyes on which pages are worth rewriting first, that's a conversation worth having. For more breakdowns like this one, see the rest of what we've written.