AI Traffic in Google Analytics 4: How to Measure It

Since May 13, 2026, Google Analytics 4 has automatically detected part of the traffic coming from ChatGPT, Gemini and Claude and classified it under a dedicated "AI Assistant" channel, with no configuration needed on your side. But this native channel doesn't catch everything: a large share of AI-originated visits arrive with no referrer at all, and land in "Direct" instead. Here's how to read what GA4 already sees, fill the gaps it misses, and interpret the numbers with the right caveats.

This is a practical guide: it starts from GA4's acquisition report as it exists today, explains what shows up, what stays hidden, and how to build a custom channel so you don't depend entirely on a feature Google can still change.

What is GA4's "AI Assistant" channel?

It's a category added to GA4's default channel group that automatically classifies a session when its referrer matches an AI assistant domain Google recognizes. Several specialized outlets, including SEO Day and Search Engine Journal, date this addition to May 13, 2026, as reflected in the Google Analytics help center.

In practice, when GA4 recognizes a referrer as ChatGPT, Gemini or Claude, it assigns the session the medium ai-assistant and sorts it into this new channel, visible in the "Traffic acquisition" and "User acquisition" reports by choosing "Session default channel group" as the primary dimension.

The exact list of covered domains isn't fully published by Google. Specialized sources don't fully agree on its scope: some cite ChatGPT, Gemini and Claude as the three confirmed assistants, others add Copilot, Grok or DeepSeek, and several report that Perplexity still lands under generic "Referral" rather than the dedicated channel. Don't trust a list found on a blog: check your own account to see which referrers actually show up under the AI Assistant channel before building a report on top of it.

Why the native channel isn't enough

The AI Assistant channel only sees part of AI-originated traffic, for a simple reason: it depends entirely on the HTTP referrer (document.referrer) the browser sends. And a large share of AI answers don't send that referrer, for several compounding reasons:

• Mobile apps: the ChatGPT app or the Gemini app opens links in a built-in browser that doesn't always pass a usable referrer.
• Copy-pasted URLs: the user reads the AI's answer, copies the address it mentions, and pastes it directly into their browser. No referrer exists in that case: by definition, the session is Direct traffic.
• Links opened without a referrer: some interfaces open links with a noopener,noreferrer attribute, which explicitly prevents the browser from passing the originating page.

The result: GA4's AI Assistant channel is a floor, not a complete measurement. It tells you "at least this much traffic comes from an AI," never "here is all the AI traffic." It's the same blind spot we describe for AI answers that generate no click at all: part of your AI visibility will never show up in any analytics tool, whichever one you use.

The October 2026 incident: when ChatGPT stopped tagging its links

This episode is a good illustration of how fragile this measurement is. OpenAI had added a utm_source=chatgpt.com parameter in 2025 to links shown in some sections of ChatGPT, which made it possible to isolate them in GA4 even without a referrer, since a UTM parameter in the clicked URL is enough for attribution, referrer or no referrer.

In mid-October 2026, several SEO practitioners reported a break: ChatGPT's links were opening in a new window via window.open() with noopener,noreferrer attributes, and the UTM parameter disappeared from the clicked URL. The observed result on several monitored sites: a drop in traffic classified as "ChatGPT" and a matching rise in "Direct" traffic, over roughly October 8 to 15. According to coverage relayed by Search Engine Roundtable, the issue was called a bug (not a deliberate choice) by the person who documented it, and the tagging has since returned, though the referrer isn't consistently restored.

The lesson for a brand: a GA4 segment or channel built on a UTM parameter or referrer specific to one AI provider can break without warning, overnight, because it depends on a technical choice you don't control. A sharp dip in your "AI" traffic means checking first whether the referrer or parameter changed, before concluding your visibility actually dropped.

Building a custom "AI Traffic" channel in GA4

To avoid depending solely on Google's native channel, the method recommended by several specialized guides is to create a custom channel group, placed explicitly above the "Referral" channel in the rule order.

This is the technical point most often done wrong: GA4 evaluates channel rules top to bottom and stops at the first match. If your "AI Traffic" rule sits after the "Referral" rule, every session with an AI referrer will already have been classified as Referral before it reaches your rule, which will therefore never apply. The order must be: AI Traffic first, Referral after.

The rule itself relies on a regular expression applied to the session's referrer, grouping the main assistants' domains:

• chatgpt.com and chat.openai.com — ChatGPT
• perplexity.ai — Perplexity
• gemini.google.com — Gemini
• claude.ai — Claude
• copilot.microsoft.com and edgeservices.bing.com — Copilot

In GA4 admin (Data display → Custom channel groups), create a new channel rule with the condition "Session first-touch referrer matches regex" and the domain list above. Unlike the native channel, a custom channel group also applies retroactively to data already collected, so you can pull up the history.

UTM parameters: a complement, not a fix

When a link you share yourself (on a product page, an offer page, a press release) can include a utm_source parameter, adding one manually in anticipation of being shared by an AI makes little sense: you don't control whether the AI will keep that parameter when citing your page, nor each assistant's behavior on this, which already changed once in 2026, as the October incident shows. UTM parameters are useful for tracking your own campaigns, not for making the measurement of inbound AI-answer traffic reliable.

On the other hand, the parameter AI platforms add themselves to their own links (such as utm_source=chatgpt.com for ChatGPT) remains the most reliable signal when present, because it survives even when the referrer is missing. That's exactly why its disappearance in October 2026, even temporary, had a direct, measurable effect on many sites' reports.

What AI referral traffic doesn't measure

Even a perfectly configured GA4 channel only captures clicks that actually bring a visitor back to your site. It says nothing about two things:

• Mentions without a click. If ChatGPT cites your brand in its answer with no clickable link, or if the user reads the answer without ever clicking, GA4 sees nothing, even though your brand was genuinely exposed. That's the core of the zero-click phenomenon.
• Clicks from Google's AI Overviews and AI Mode, available in France since July 22, 2026. These clicks arrive with a plain google.com referrer, exactly like a traditional organic search. GA4 doesn't distinguish them from the rest of Google traffic, and no channel, native or custom, isolates them today.

AI referral traffic measured in GA4 is therefore a subset of a subset: of everything AI engines say about you, only a fraction generates a visit, and of that fraction, only part is correctly attributed. For a fuller picture of what AI engines actually say about your brand, click or no click, see our guide on methods for measuring AI visibility, of which GA4 traffic is only one of four.

What to do concretely?

1. Check whether the AI Assistant channel already exists in your account. Reports → Acquisition → Traffic acquisition, primary dimension "Session default channel group." If it doesn't show up yet, that may be a matter of volume or rollout timing: don't duplicate it with a custom channel covering the same scope.
2. Build a custom channel group with the regex on the domains above, placed before the Referral rule, to cover Perplexity and any assistants the native channel might be missing.
3. Compare the two regularly: if the custom channel captures a much higher volume than the native one for a given referrer, that's a sign Google hasn't (yet) added that domain to its own list.
4. Watch for sudden breaks. A sharp drop in traffic classified as AI, matched by a corresponding rise in Direct traffic, almost always signals a technical change on the AI provider's side, not an actual loss of visibility.
5. Don't stop at traffic. Combine this measurement with a GEO score and a citation test to know what AI engines say about you, even when it generates no measurable visit.

FAQ

Does GA4 automatically detect traffic from ChatGPT, Gemini and Claude?

Partly. Since May 2026, an "AI Assistant" channel automatically classifies sessions whose referrer matches an AI domain Google recognizes. But this channel doesn't cover all AI traffic: a share arrives with no referrer and stays invisible, classified as Direct.

Does Perplexity show up in GA4's AI Assistant channel?

Specialized sources don't fully agree on this at the time of writing. Check your own account to see whether sessions from perplexity.ai show up under "AI Assistant" or generic "Referral," rather than trusting a list found online.

Why did my "ChatGPT" traffic drop sharply in October 2026?

Likely because of a technical change at OpenAI: several sites noticed, between October 8 and 15, 2026, that ChatGPT's links temporarily stopped passing their UTM parameter and referrer, which pushed that traffic into the Direct category. The issue was described as a bug and has since been fixed.

Does AI referral traffic measured in GA4 reflect my entire visibility in AI answers?

No. It only measures visits actually generated by a correctly attributed click. It says nothing about brand mentions with no link, nor about clicks from Google's AI Overviews, which are counted as plain Google traffic.

Sources

• SEO Day, "GA4: New AI Assistant channel for AI referrals".
• Search Engine Journal, "GA4's AI Assistant Channel Undercounts Your AI Traffic. Here's How To Build One That Doesn't".
• Search Engine Roundtable, "ChatGPT Updates To Improve Tracking In Analytics With More UTM Parameters".
• Search Engine Roundtable, "OpenAI Drops UTM Parameters From ChatGPT Results (GPT-6)".
• Ahrefs, on the click-through drop following the AI Overviews launch in France.

→GEO audit: how to audit your AI visibility

→Measuring your AI visibility: tools and methods in 2026

→GEO KPIs: the metrics that matter for measuring AI visibility

→Zero click: when AI answers send no traffic