ChatGPT and AI assistant visits in GA4: why some show as referral and some as direct.
- “ChatGPT traffic in GA4”
- “ChatGPT showing as referral in GA4”
- “ChatGPT traffic showing as direct in GA4”
- “chatgpt.com / (not set) in GA4”
- “AI Assistant channel in GA4”
- “how to track ChatGPT traffic in GA4”
- “Perplexity traffic in Google Analytics”
- “utm_source=chatgpt.com”
Baris Asa, tracking consultant, London · Last checked: 11 November 2026
Referral means the browser told GA4 which site sent the visitor: chatgpt.com. Direct means nothing did, usually because the link was pasted into the browser or opened from an app that passes no referrer. Since 13 May 2026 GA4 moves recognised assistant referrals out of Referral into a new AI Assistant channel. A third row,chatgpt.com / (not set), is ChatGPT’s own link tag (a source with no medium), and GA4 files it as Unassigned.
Two words, so the rest reads easily. The referrer is the address of the page the visitor clicked from; the browser sends it. A UTM tag is a label written into the link itself (?utm_source=chatgpt.com); the site that publishes the link adds it. GA4 builds source, medium and channel from those two and nothing else.
None of these rows is a fault on its own. The same assistant produces all of them, depending on where the person clicked. The one fault is when your own site throws the tag away on the way in: check that first. Google’s AI Overviews and AI Mode are not here at all; Google files them under Organic Search.
What does each row in GA4 mean?
Open Reports, Acquisition, Traffic acquisition and set the primary dimension to Session source / medium.
| WHAT YOU SEE | WHAT ARRIVED | CHANNEL | READ IT AS |
|---|---|---|---|
| chatgpt.com / ai-assistant | Referrer on Google’s list | AI Assistant | Normal, since 13 May 2026 |
| chatgpt.com / referral | Referrer, before 13 May 2026 | Referral | Normal for older dates |
| perplexity.ai / referral (any assistant not on the list) | Referrer | Referral | Normal; group it yourself |
| chatgpt.com / (not set) | UTM tag (source only) | Unassigned | Normal; group it yourself |
| (direct) / (none) | Neither | Direct | Can’t be recovered |
Google’s channel page describes AI Assistant as visits “from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok”, and its May 2026 release note also names Claude. The full list isn’t published. Perplexity is in the third row as an example of an assistant Google doesn’t name; check where yours actually lands. A chatgpt.com / referral row dated after 13 May 2026 is worth a second look: by Google’s description it should normally be AI Assistant, so check the exact referrer domain.
Two rows you may also see sit outside this page. Unassigned has more causes than this one, covered in the Unassigned note. A payment provider in Referral is a different problem with its own fix: payment gateway showing as referral.
Why does the same assistant show up as referral one day and direct the next?
Because the referrer and the tag travel separately, and each one can be lost.
The referrer. Browsers default to a policy called strict-origin-when-cross-origin: when the visitor goes to another HTTPS site, only the origin is sent. So with the default, the most GA4 learns is chatgpt.com, not the conversation. A link marked rel="noreferrer", or a page with a no-referrer policy, sends nothing at all. And a link that doesn’t start on a web page (a URL pasted into the address bar) has no referrer to send.
Apps. The desktop and mobile apps hand links to a browser or open them in their own. I couldn’t find a published statement from OpenAI, Google, Microsoft or Anthropic on what their apps pass, and the same goes for the new AI browsers. Treat app and AI-browser traffic as unknown until you test it: tap one of your links in the app on a phone, at a quiet hour, and see which row that visit lands in.
The tag. OpenAI’s publisher FAQ says ChatGPT adds utm_source=chatgpt.com to links in its search results. The tag is part of the URL, so it survives a copy and paste and an app handoff that may lose the referrer. But it carries a source and no medium. Google’s campaign URL page says missing UTM parameters show as (not set), and a source of chatgpt.com with medium (not set) matches no default channel rule, so it’s Unassigned.
When both are lost, Google’s direct traffic page covers what’s left: no UTM, no referral details, and the visit is (direct) / (none).
Google doesn’t document which wins when a recognised referrer and a utm_source arrive together. Read the rows you actually have rather than predicting them.
Which part is a fault I can fix?
Losing the tag on your own site. If an assistant links to an old URL, an HTTP address or the bare domain, and your redirect drops the query string, utm_source=chatgpt.com is gone before GA4 loads. Google’s direct traffic page names redirects as one way UTM parameters get stripped. That’s F-204 , the same fault that turns paid traffic into Direct. It hurts most on clicks with no referrer, where the tag is the only label the visit has.
Test: take a page assistants are likely to cite and type the old form of its address with a tag on the end, for example:
http://yourshop.co.uk/guides/sizing?utm_source=chatgpt.com
Let it redirect, then read the address bar. It should end on https://www.yourshop.co.uk/guides/sizing?utm_source=chatgpt.com. If the ?utm_source=chatgpt.com part has gone, the redirect rule needs to keep the query string. Repeat for three or four pages. Your developer or platform support makes that change; it’s one rule, not a tracking rebuild.
Everything else (pasted URLs, apps that pass nothing, assistants not on Google’s list) can’t be fixed on your side. You can’t add tags to links you don’t publish, and you can’t tell GA4 after the fact that a Direct visit came from a chat.
How do I track ChatGPT and AI assistant traffic in GA4?
Use the built-in AI Assistant channel for a quick look, then build one custom channel group that also catches the Referral and Unassigned rows. Google says custom channel groups apply to reports retroactively, so the group covers dates before 13 May 2026 too. This is a job for whoever administers your GA4 property:
- In Admin, Data display, Channel groups, create a new group as a copy of the default (this needs the Editor role or above on the property).
- Add a channel called AI assistants with the condition Source matches regex.
- List the assistant sources you’ve actually seen in Session source, spelled exactly as GA4 shows them. For example:
chatgpt\.com|chat\.openai\.com|perplexity\.ai|www\.perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com
- Drag the new channel to the top of the list, above the copied AI Assistant and Referral channels, and save. Google says traffic goes to the first channel it matches, in order.
- In Traffic acquisition, switch the primary dimension to your new group.
GA4 regex is full match by default: a pattern has to match the whole value, not part of it. So chatgpt on its own matches nothing, because the source is chatgpt.com. Google’s own help page has an AI assistants example that gets round this with wildcards (.*chatgpt.*, .*gemini.*, and a first branch ^.*ai that catches any source ending in “ai”). That works, but a list of exact domains is easier to check, and it won’t pick up a future source you didn’t mean to include.
The group doesn’t touch Direct. Nothing does.
Is some of my direct traffic really AI traffic?
Possibly, and GA4 can’t prove it. You can look for a shape. In Traffic acquisition, filter to the Direct channel and add Landing page as a secondary dimension. Direct visits that start on a deep page (a guide, a comparison, an FAQ) aren’t people typing your address. If those are the pages assistants cite, some of that Direct may be assistant traffic from apps and pasted links. Treat it as an indicator, not a number to report.
Two things that look like evidence but aren’t:
- A returning visitor. Google’s scopes page says sessions initiated by direct entrance “are attributed to the UTM values for that user”. Someone who first came from ChatGPT, on a visit that carried the tag or a referrer, and later types your address can show as
chatgpt.comagain. That’s GA4’s attribution, not a second click from the assistant. - The landing page URL. Google’s campaign page says UTM parameters are left out of Landing page + query string and kept in Page location. Search Page location for
utm_source=chatgpt.com, not the landing page.
If Direct jumped on a date you can name, check your own releases for that date first, with the site redesign note.
Who fixes this?
The GA4 property admin, for the channel group, and whoever owns your redirects, for the tag. It’s a short job, not new tracking. I do it as part of GA4 consulting for brands and the agencies that run their accounts: the redirect test on your cited pages, the channel group, and a note of which rows are which.
Filed as SYM-068 under F-204 . Only the stripped-tag case is the fault; the other rows are GA4 reading what it was given.
Common questions
Why does ChatGPT traffic show as direct in GA4?
Because nothing on the visit told GA4 where it came from. GA4 needs a referrer (the site the browser says the visitor came from) or a UTM tag (a label in the link). A URL pasted into the browser has no referring page. An app that hands the link to a browser may pass none either. If the tag was also lost, for example by a redirect on your own site that drops it, the visit is (direct) / (none).
Why does ChatGPT traffic show as referral in GA4?
Because the browser passed chatgpt.com as the referrer. Before 13 May 2026 GA4 filed those visits under Referral. Since then, a referrer on Google’s list of AI assistants goes to the AI Assistant channel instead, with the medium ai-assistant. An assistant that isn’t on Google’s list still shows as referral.
What is the AI Assistant channel in GA4?
A default channel Google added on 13 May 2026. When a visit’s referrer matches Google’s list of AI assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant). Google names ChatGPT, Gemini, Deepseek, Copilot, Grok and Claude as examples but doesn’t publish the full list. AI Overviews and AI Mode stay in Organic Search.
Why do I see chatgpt.com / (not set) in GA4?
OpenAI says ChatGPT adds utm_source=chatgpt.com to links in its search results. There is no utm_medium, and Google says a missing UTM parameter shows as (not set). If that tag arrives without a referrer GA4 recognises, the visit has a source but no medium, matches no channel rule, and is filed as Unassigned.
Does GA4 move my old ChatGPT referral data into the AI Assistant channel?
Google’s release note doesn’t say it does. To compare across 13 May 2026, use a custom channel group: Google says those apply to reports retroactively.
Can I see which ChatGPT conversation sent a visitor?
No. Under the browser’s default referrer policy only the origin of the sending site arrives (chatgpt.com), not the page, and the UTM tag names the source, not the prompt. GA4 can tell you a visit came from an assistant, not what was asked.
Sources
Read on 11 November 2026:
- Google Analytics Help, what’s new in Google Analytics (13 May 2026: AI Assistant traffic measurement; medium
ai-assistantwhen the referrer matches a recognised AI assistant; campaign(ai-assistant); ChatGPT, Gemini and Claude named) - Google Analytics Help, default channel group (AI Assistant description and rule; AI Overviews and AI Mode in Organic Search; Referral and Direct rules; Unassigned when no rule matches) and its linked list of default channel group sources (search, social, shopping and video categories; no AI category)
- Google Analytics Help, custom channel groups (first matching channel wins; the AI assistants example regex; applied to reports retroactively)
- Google Analytics Help, about regular expressions (full regex and case sensitive by default; partial matches need
.*) - Google Analytics Help, collect campaign data with custom URLs (missing UTM parameters show as (not set); UTMs left out of Landing page + query string and kept in Page location)
- Google Analytics Help, understand (direct) / (none) traffic (missing UTMs, redirects stripping UTM parameters, URL shorteners, typed URLs, offline documents, ad blockers)
- Google Analytics Help, scopes of traffic-source dimensions (sessions initiated by direct entrance are attributed to the UTM values for that user)
- OpenAI Help Center, publishers and developers FAQ (ChatGPT includes
utm_source=chatgpt.comin referral URLs; the page blocks automated reads, so this is from its indexed text) - MDN Web Docs, Referer and Referrer-Policy (
strict-origin-when-cross-originis the default and sends only the origin cross-origin;no-referrerandrel="noreferrer"send nothing)