AI Traffic in GA4: How ChatGPT, Perplexity, Gemini & Google AI Mode Referrals Actually Show Up.

As of July 2026, Google Analytics 4 has a native "AI Assistant" default channel that automatically buckets sessions from recognized AI chatbot referrers under a dedicated medium value (ai-assistant), separate from ordinary Referral traffic. Google shipped it on May 13, 2026, and its own Default Channel Group documentation names five recognized sources: ChatGPT, Gemini, Deepseek, Copilot, and Grok. Worth flagging directly, since a lot of secondary coverage gets this wrong: Claude and Perplexity are not on that list as of this writing. It is not retroactive, a meaningful share of AI-referred clicks still arrive with no referrer at all and land in Direct, and — the detail that trips up almost everyone — clicks from Google's own AI Overviews and AI Mode are not part of this new channel.

That last point answers the single most common question about this topic, so it's worth stating plainly before anything else: GA4 does not show Google AI Mode or AI Overviews as a distinct referrer or channel. They're search results rendered a different way, and the server-side referrer is identical either way, so Google's own documentation folds them into Organic Search — indistinguishable from an ordinary blue-link click. Everything below covers what GA4 actually does show, referrer by referrer and tool by tool, and how to build the reporting you need on top of it.

Does GA4 Show Google AI Mode or AI Overviews as a Referrer?

No, and this isn't a guess — it's what Google's own Default Channel Group reference says. The current definition of Organic Search reads: "Organic Search is the channel by which users arrive at your site/app via non-ad links in organic-search results, including Google's AI Overviews and AI Mode." Google added that clause specifically to settle the question. A click on a citation inside an AI Overview, a click inside a full AI Mode conversation, and a click on a plain blue link all get classified the same way: source google, medium organic, channel Organic Search.

The reason is mechanical, not a policy choice. The HTTP Referer header a browser sends on click is the page the click came from — google.com/search — and that string doesn't change based on which layout rendered the result. GA4, and every other analytics tool that leans on referrers, has no signal in that header telling it whether the click came from a ten-blue-links page or a generative AI Overview box sitting above them. Google Search itself knows the difference internally; nothing about that knowledge crosses over to the site that gets the click.

Search Console has moved further here than GA4 has. Starting in June 2026, Google rolled out a standalone Search Generative AI performance report inside Search Console — a separate report section, not a filter added to the existing Performance report — showing impressions, pages, countries, devices, and date-range breakdowns specifically for AI Overviews and AI Mode (with a parallel view for generative AI features in Discover). Worth being precise about what it doesn't give you: no clicks, no CTR, and no query-level detail, at least as shipped — so treat it as a visibility count, not a performance report in the sense GA4 or the rest of Search Console normally uses that word, and check what your own property currently shows rather than trusting a description from a few months back, since Google could still extend it. Either way, it only tells you what happened in Search. It can't tell you whether the visitor who saw or clicked into an AI Overview converted, how long they stayed, or what they bought — that's still GA4's job, and GA4 genuinely cannot make this particular split.

How ChatGPT Traffic Actually Shows Up in GA4

On a plain desktop browser, clicking a link inside a ChatGPT conversation sends an intact referrer. You'll see chatgpt.com as the session source in your Referral (or, after May 2026, AI Assistant) report. That's the clean case. Three things complicate it in practice.

ChatGPT does tag some of its own links

OpenAI has appended utm_source to a growing set of outbound links since mid-2025, expanding coverage from citation links to the "More" section of search-style answers. You'll see the value show up as chatgpt or chatgpt.com depending on which surface inside ChatGPT the link came from — treat both as the same traffic. We haven't found a consistently documented utm_medium value that ships alongside it, and that gap is exactly what causes the next problem.

A source-only UTM tag can be worse than no tag at all

GA4's channel rules follow a simple precedence: if a URL carries any UTM parameter, GA4 uses the UTM values for classification and ignores the referrer entirely. That's normally a feature — it's how you override automatic detection with your own campaign data. But it backfires when only utm_source is present and utm_medium is missing or unrecognized: GA4 won't fall back to treating chatgpt.com as a referrer, because a UTM parameter is present. Instead the session usually falls straight through to Unassigned — a worse outcome, ironically, than if ChatGPT had sent no UTM tag at all and let GA4 classify the visit as a plain Referral. If you're troubleshooting "why is my ChatGPT traffic showing as Unassigned," this source/medium mismatch is almost always the answer. Our UTM parameters guide covers the full set of values GA4 recognizes if you want the reference.

Google's own rule for the new AI Assistant channel is worded around the referrer, not around an existing medium value ("the medium is set to ai-assistant ... if the referrer matches a list of AI Assistants") — which suggests, though Google hasn't published the exact precedence order against UTM tags, that a recognized AI referrer should now land in AI Assistant even on a source-only link that previously fell into Unassigned. Treat that as a reasonable expectation to test on your own property, not a guarantee — spot-check a few sessions in your Traffic Acquisition report rather than assuming.

Apps and the Atlas browser strip the referrer entirely

The ChatGPT iOS and Android apps typically open external links in the phone's system browser, and in that hand-off the Referer header often doesn't survive. ChatGPT Atlas — OpenAI's own browser, launched in October 2025 — has been reported to block or strip referrer headers on many outbound link opens as well. In both cases the session shows up in GA4 as Direct, or occasionally (not set), with nothing left to tie it back to ChatGPT. No default channel grouping update fixes this — there's no referrer left to classify.

Gemini, Perplexity, and Copilot: What's Confirmed and What Isn't

Coverage quality varies a lot by tool, and it's worth being precise about what's actually confirmed versus what a secondary source is repeating.

Gemini

Referrer is gemini.google.com. This is one of the five sources Google's own Default Channel Group documentation names explicitly for the AI Assistant channel — alongside ChatGPT, Deepseek, Copilot, and Grok — so it's about as confirmed as this gets. It's worth holding in your head as a genuinely separate case from AI Mode: both are Google products, but a standalone Gemini chat session lives on its own subdomain and gets the new AI Assistant treatment, while Google Search's AI Mode stays inside Organic Search. Same company, two different classifications. The Gemini mobile app's in-app browser can still strip the referrer on some link opens, same as any other app.

Perplexity

Referrer is perplexity.ai. Perplexity's own Comet browser has been reported to pass referrer data through reliably, behaving more like a conventional browser than an AI wrapper. Unlike ChatGPT, Perplexity's citation links don't consistently carry a utm_source parameter, so if you're publishing content you expect Perplexity to cite — whitepapers, resource pages, anything with a CTA — the practical move is to add your own UTM tagging to those specific links rather than waiting for Perplexity to do it for you. Perplexity isn't one of the five sources Google's current Default Channel Group documentation names (ChatGPT, Gemini, Deepseek, Copilot, and Grok); an older Google help-center example for building a manual custom channel group does list it alongside ChatGPT, Gemini, Copilot, and Claude, but that page also still references "Google Bard" — a product renamed to Gemini back in 2024 — which is a decent sign it predates the native channel and isn't a live, current list. Don't treat any single list (including this one) as definitive; check your own Referral and AI Assistant reports after the fact.

Microsoft Copilot

Referrer is copilot.microsoft.com. Historically this landed as a plain Referral like any unrecognized domain. Unlike Perplexity, Copilot is one of the five sources Google's Default Channel Group documentation names explicitly (alongside ChatGPT, Gemini, Deepseek, and Grok) — so on a rolled-out property, a copilot.microsoft.com referral should already land in AI Assistant natively, not Referral. That still leaves two gaps worth closing: pre-May-2026 historical Copilot sessions, which the native channel won't reclassify, and Perplexity, which isn't on Google's recognized list at all. The custom channel group covered below handles both — it costs nothing to build and closes the gap either way.

Referral, Unassigned, or AI Assistant: The Classification Logic

Before May 2026, none of these tools' domains were on GA4's built-in search-engine or social-network lists, so a referred visit with no matching UTM medium landed in plain Referral — the same bucket as a blog linking to you or a press mention. That's still where traffic from any AI tool not on the recognized list lands today. Our guide to GA4's default channel grouping covers the full rule waterfall if you want the general mechanics — source, medium, campaign, and the order GA4 checks them in.

Unassigned is the other frequent landing spot, and it's not a traffic source — it's a classification failure. It means GA4 saw parameter values that didn't match any rule at all, which for AI traffic usually means the source-only UTM problem described above. It's the AI-referral-shaped twin of the classic "we tagged our newsletter utm_medium=newsletter instead of email" mistake: a real, identifiable visitor whose traffic quietly becomes invisible because of one mismatched parameter.

The new AI Assistant channel sits alongside these. For a referrer Google recognizes, it now wins over the plain Referral fallback — sessions from chatgpt.com, for instance, are widely reported to land in AI Assistant rather than Referral once a property's rollout is live. Direct is unchanged: it's still the "no referrer, no UTM" fallback, and it's still where a not-insignificant share of AI-referred clicks end up once you account for stripped referrers across mobile apps and AI browsers.

How to Build a Custom Channel Group That Catches Everything Native Doesn't

The native AI Assistant channel solves the going-forward case for a short list of named tools. It does not solve two things you'll likely still want: a look backward at traffic before May 13, 2026, and coverage for any AI tool Google hasn't (yet) added to its recognized list. A custom channel group solves both, because — unlike the native channel — custom channel groups are evaluated at query time against your existing session data, so a new rule applies retroactively within your data-retention window (2 or 14 months, depending on your setting).

1. Go to Admin → Data display → Channel groups and create a new channel group (or add a channel to an existing custom one).
2. Add a new channel — name it something like "AI Referrals" — with a condition on Session source, using "matches regex" with a pattern covering the domains you want to catch, for example chatgpt\.com|chat\.openai\.com|claude\.ai|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com. Treat that list as a starting point, not a permanent one — new AI browsers and assistants launch often enough that it's worth revisiting.
3. Reorder the channel list so your new AI channel sits above Referral. Otherwise a matching session gets claimed by the generic Referral rule before it reaches your custom one.
4. Save. Open Reports → Acquisition → Traffic Acquisition and switch the channel group selector to your new custom group to see the reclassified historical sessions.

If you already built a homemade AI channel before May 2026, don't throw it away — add an "OR" condition matching Default channel group exactly matches AI Assistant alongside your existing regex rule. That way you keep your historical backfill and pick up anything the native rollout adds later without maintaining two competing reports.

For a one-off look without touching your reporting configuration, use an Exploration instead: Explore → Free-form, row dimension Session source / medium, with a filter on Session source matching your AI domain list (or, for anything after the rollout, Session default channel group exactly matches AI Assistant). Sort by sessions descending and you'll see exactly which tools are sending traffic and in what volume, without committing to a permanent channel definition.

What You Still Can't See

Referrer stripping is architectural, not a bug GA4 (or any analytics tool) can patch around. A user who copies a URL out of a chat response and pastes it into a new tab, a mobile in-app browser that drops the header on hand-off, a browser like Atlas that manages navigation on its own terms, a screenshot of an AI answer shared in Slack — none of these carry a Referer header, so none of them can ever be classified as AI-referred by GA4, no matter how complete the recognized-referrer list eventually gets. That traffic lands in Direct and stays there, genuinely indistinguishable from someone typing your URL from memory.

This whole mechanism is also web-only, because it depends on an HTTP referrer that only exists in a web navigation context. If someone asks an AI assistant about you and it surfaces your native app rather than your website — a deep link rather than a browser tab — this feature has nothing to say about it. That's Firebase / app-attribution territory, a different measurement problem with its own tooling, not something the AI Assistant channel extends to.

And worth repeating because it surprises people: the native channel is not retroactive. Data collected before your property's rollout date keeps whatever classification it originally got — usually Referral or Direct — permanently. The custom channel group above is the only way to see a consistent picture across the before-and-after line.

Why This Matters Now

AI chat interfaces have gone from novelty to a genuine top-of-funnel entry point for a lot of sites, and Google shipping a purpose-built default channel for it is itself a signal about how much volume this now represents — a mature product doesn't add a new default channel for a rounding error. Executives who never used to ask about channel-grouping mechanics are now asking how much traffic and revenue is AI-driven, and "it's mixed into Referral and Unassigned somewhere" is not an answer that survives that conversation. Getting this classification right has moved from a nice-to-have reporting detail to something people are being asked about directly.

Attribution gaps like this one are rarely isolated — they tend to show up alongside other silent disagreements between GA4 and the rest of your stack. If you're chasing a different mismatch, see our breakdown of the most common bugs between GA4 and GTM, or run through our free GA4 audit checklist for a broader pre-flight pass beyond just channel classification.

Frequently Asked Questions

Does GA4 show Google AI Mode as a referrer?

No. Google's own Default Channel Group documentation states that Organic Search includes traffic "via non-ad links in organic-search results, including Google's AI Overviews and AI Mode." Clicks from AI Overviews and AI Mode carry the same google.com referrer as a standard blue-link click and are classified identically — source google, medium organic, channel Organic Search. There is no separate referrer string, UTM parameter, or channel that isolates them in GA4 today. Search Console's Search Generative AI performance report is the closest thing to visibility into this traffic, but it reports impressions on the Search side, not on-site outcomes.

Why is my ChatGPT traffic showing as Unassigned in GA4?

This almost always happens because the link carried a utm_source parameter (commonly chatgpt or chatgpt.com) with no matching utm_medium. GA4 ignores referrer-based classification entirely whenever any UTM parameter is present, so a source-only tag doesn't fall back to being treated as a referral — it falls through every channel rule and lands in Unassigned. Since May 13, 2026, Google's native AI Assistant channel appears to key off the referrer domain directly rather than requiring a specific medium value, so on a rollout property this should increasingly resolve itself for chatgpt.com traffic specifically. If you're still seeing it, build a custom channel group (covered above) with a Session source condition matching chatgpt.com as a backstop.

How do I track AI traffic in Google Analytics 4?

Three layers, used together. First, check whether your property has the native AI Assistant default channel — it's automatic, requires no setup, and as of mid-2026 recognizes five sources by referrer domain: ChatGPT, Gemini, Deepseek, Copilot, and Grok (notably not Claude or Perplexity). Second, build a custom channel group under Admin → Data display → Channel groups with a regex condition on Session source covering the AI domains you care about (chatgpt.com, claude.ai, perplexity.ai, gemini.google.com, copilot.microsoft.com, and others as they launch) — this catches tools the native channel doesn't yet recognize and, because custom channel groups evaluate at query time, applies retroactively to historical sessions the native channel can't touch. Third, accept the limit: any AI-referred click that arrives with no referrer header — common on mobile apps and some AI browsers — lands in Direct and cannot be recovered through channel grouping, because there's no data left to classify.

What is the GA4 AI Assistant channel?

It's a native default channel Google added to GA4 on May 13, 2026. When a session's referrer matches a recognized AI assistant, GA4 automatically sets the medium to ai-assistant, the campaign to (ai-assistant), and groups the session under the "AI Assistant" channel in Default Channel Group reports — no configuration required. Google's Default Channel Group documentation names five recognized sources: ChatGPT, Gemini, Deepseek, Copilot, and Grok. Claude and Perplexity are not on that list as of this writing — Google could extend it without much notice, so treat this as current-as-of-publish rather than permanent. Two limits worth knowing: it is not retroactive (sessions collected before your property's rollout keep their original classification), and it only works for sessions that arrive with an intact referrer — traffic with a stripped or missing referrer still lands in Direct regardless of which AI tool actually sent it.