Your GA4 Is Blind to AI Traffic: Track ChatGPT, Claude & Perplexity
GA4 misses most of your AI traffic. The native AI Assistant channel Google launched on May 13, 2026 only recognizes ChatGPT, Gemini, and Claude, so Perplexity and Copilot stay buried in Referral. Worse, Statcounter found 35 to 70 percent of AI referral sessions arrive with no referrer and land in Direct. To see the full picture you need a custom regex channel group plus server-side capture. Seresa’s own pipeline measures AI referrals at 13 to 20 percent of sessions, not the roughly 1 percent most stores see.
Why GA4 can’t see most AI traffic
GA4 files AI visits as Referral or Direct by default, so the channel growing fastest in your stack is the one your dashboard hides.
AI traffic means people, not crawlers. It’s the human who asks ChatGPT, Claude, or Perplexity a question, sees your page cited in the answer, and clicks through. That click is a real session carrying a referrer from the AI tool’s domain. The bots that index your pages for training never appear in GA4, because GA4 is JavaScript-based and only fires for real browsers.
The problem isn’t that GA4 can’t record the visit. It’s how GA4 classifies it. A click from chatgpt.com arrives as a referral and gets lumped in with every other referral, so it never stands out as its own line. AI platforms generated more than 1.13 billion referral visits in June 2025, up 357 percent year over year, according to Similarweb. None of that volume shows up in a default GA4 channel report.
AI-assisted sessions are growing more than 80 percent year over year, yet GA4’s default reports file them under Referral and Direct, so the fastest-growing channel is the one most dashboards hide.
What the May 2026 AI Assistant channel catches
Google’s native channel is a real head start, but it recognizes only three of the five major tools and never backfills your history.
On May 13, 2026, Google added a native AI Assistant channel to GA4’s Default Channel Group. When an incoming session’s referrer matches a recognized AI domain, GA4 tags it with the medium ai-assistant and files it under the AI Assistant channel automatically. To find it, open Reports, then Acquisition, then Traffic acquisition, and set the primary dimension to Session default channel group.
There are two catches. Google’s recognized list names only ChatGPT, Gemini, and Claude, so visits from Perplexity and Copilot stay buried in Referral. And there’s no backfill: the channel counts forward only, from the day it switched on, so it can’t reconstruct the AI traffic you already had. Translation: the native channel tells you part of the story, starting today, for three of the five tools.
You may be interested in: Chrome Kept Third-Party Cookies. Why Are You Still Losing Conversion Data?
Build a channel group that catches all five tools
A custom regex channel group covers every major AI source, but like the native channel it only applies from the moment you create it.
To catch all five tools, build your own channel group. Open Admin, then Data display, then Channel groups, and click Create new channel group. Add a channel named AI Search, set the condition to Source matches regex, and use a pattern that covers each domain:
chatgpt.com|chat.openai.com|gemini.google.com|claude.ai|perplexity.ai|copilot.microsoft.com
Drag the AI Search channel above Referral so AI visits resolve there first, then save. From that point on, every AI visit with an intact referrer lands in one clean line. The same caveat applies as with the native channel: custom groups don’t backfill, so use a Free-form Exploration with a Session source regex filter to read your history.
| AI tool | Caught by native AI Assistant channel? | Global AI referral share (Statcounter, Mar 2026) |
|---|---|---|
| ChatGPT | Yes | 78.16% |
| Gemini | Yes | 8.65% (overtook Perplexity) |
| Claude | Yes | 2.91% (peaks ~3.6%) |
| Perplexity | No, stays in Referral | Single digit, passed by Gemini |
| Copilot | No, stays in Referral | Small but persistent |
The native channel and a custom regex group together still only capture AI visits that arrive with a referrer, which is not all of them.
GA4’s native AI Assistant channel recognizes only ChatGPT, Gemini, and Claude, so without a custom channel group a third of the AI ecosystem stays invisible inside generic Referral.
The referrer gap no channel group can close
Even a perfect regex can’t label a session that never carries a source, and a large share of AI visits arrive exactly that way.
Here’s the limit of any channel-group approach. When a visitor clicks inside an AI app, an embedded browser, or certain mobile link handlers, the referrer header is stripped before the session reaches your site. GA4 has nothing to classify, so the visit drops into Direct with no source at all. Statcounter found between 35 and 70 percent of AI referral sessions arrive without referrer information.
No regex recovers those visits, because they were never labeled. The only way to catch them is to record the click on your own server, first-party, before the browser drops the header. That moves the measurement off the browser and onto infrastructure you control.
You may be interested in: Google Killed Privacy Sandbox. Your WooCommerce Data Is Still Leaking
What AI traffic is worth once you can see it
AI visitors are scarce but high-intent, and the per-tool mix decides where your content earns its citations.
Once the data is visible, the case for measuring it is straightforward. AI search traffic converts at roughly 4.4 times the rate of traditional organic search. These visitors have already refined their question inside the AI conversation, so they land further along the decision journey than a cold search click.
The per-tool mix matters too. ChatGPT dominates raw volume, but for B2B audiences Claude reaches about 18 percent of measurable AI referrals versus roughly 63 percent for ChatGPT, because B2B buyers lean on Claude and Perplexity for longer research queries. Seresa’s own first-party pipeline measures AI referrals at 13 to 20 percent of sessions, against the roughly 1 percent most stores report, with Claude the dominant referrer. Server-side capture is also how a first-party tool like Transmute Engine™ records the AI click before the referrer is stripped, so the Direct bucket stops swallowing your best visitors.
Key Takeaways
- GA4 hides AI traffic by default: visits land in Referral or Direct, never their own line.
- The May 2026 native channel catches only three tools: ChatGPT, Gemini, and Claude, with no backfill and no Perplexity or Copilot.
- A custom regex channel group catches all five: but only from its creation date, so use an Exploration for history.
- 35 to 70 percent of AI sessions lose their referrer: only server-side, first-party capture recovers them.
- AI visitors convert at about 4.4x organic: so the blind spot is expensive, not academic.
Frequently asked questions
Partly. Since May 13, 2026, GA4’s native AI Assistant channel automatically tags visits from ChatGPT, Gemini, and Claude with the medium ai-assistant and files them under an AI Assistant channel. Perplexity and Copilot are not on Google’s recognized list, so their visits stay in the generic Referral channel. To capture all five tools you still need a custom channel group with a regex that includes perplexity.ai and copilot.microsoft.com.
Because the referrer header is often stripped before the visit reaches your site. When someone clicks a link inside an AI app, an embedded browser, or certain mobile flows, the originating domain is dropped, so GA4 has nothing to classify and files the session as Direct. Statcounter found 35 to 70 percent of AI referral sessions arrive this way. No channel group can recover them, because they were never labeled in the first place.
Use a Free-form Exploration rather than a custom channel group. Custom channel groups apply only from their creation date and never backfill historical data. In Explore, add Session source or Session source/medium as a dimension, add Sessions and Engaged sessions as metrics, then filter on a regex matching the AI domains. That surfaces every AI visit GA4 already holds, across the full retention window.
Yes. AI search traffic converts at roughly 4.4 times the rate of traditional organic search, and the volume is growing more than 80 percent year over year. A channel that is small today but compounding fast, and that brings higher-intent visitors, is exactly the one worth measuring early so you can see which pages AI tools cite and where the engaged visitors land.
References
- ACCESS Newswire. “How to Track AI Traffic in GA4 (ChatGPT, Gemini, Claude, Perplexity & Copilot).” accessnewswire.com, June 2026.
- AuthorityTech. “AI Traffic Attribution: How to Track ChatGPT, Perplexity, Gemini.” authoritytech.io, January 2026.
- Nadia Mohamed. “Track AI Referral Traffic in GA4: 2026 Setup Guide” (citing Similarweb 2025). nadiamohamed.me, 2026.
- Seresa. First-party AI referral measurement, outPIPE / BigQuery pipeline. seresa.io, 2026.
If you want every AI visit counted, including the ones GA4 files as Direct, start by capturing events first-party at seresa.io.