GA4 Says 'Direct'? How to See Your ChatGPT & Perplexity Traffic (Free)

A customer says they found you through ChatGPT. A colleague swears Perplexity is sending leads. Yet your GA4 acquisition report shows nothing but a fat Direct bar. The traffic is real — it is just landing in the one bucket GA4 reserves for "unknown origin." This guide explains exactly why AI referrals get misfiled, the four ways to surface them today (including the AI Assistant channel GA4 rolled out in May 2026), and how to catch AI traffic that site-side analytics never sees at all.

Why ChatGPT Traffic Disappears Into "Direct"

GA4 names a session's source using three signals, in rough order of precedence: UTM parameters on the landing URL, the HTTP Referer header the browser sends, and — when both are absent — the fallback label Direct. AI assistants break the first two in ways classic web traffic never did:

• App-embedded browsers don't always pass referrers. When a link opens inside ChatGPT's app or an in-app webview, the request that reaches your site frequently carries no Referer header at all. GA4's only remaining option is Direct.
• JavaScript-based handoffs lose the header. Several AI surfaces route clicks through script-driven redirects, which start a fresh navigation without the original referrer attached.
• Google's AI Mode strips referrers on purpose. Links emitted by AI Mode carry rel="noreferrer", which instructs the browser to send no referrer — analytics practitioners tracking this have watched AI Mode sessions file as Direct since the feature launched.

There is one important exception: ChatGPT appends utm_source=chatgpt.com to many of its outbound links. Practitioners first observed the tagging in mid-2025 and coverage has grown since — but it is inconsistent (not every link or surface gets tagged) and it never includes utm_medium or utm_campaign. That is why some ChatGPT traffic shows up correctly as chatgpt.com / referral while the rest silently joins your Direct bucket. Estimates of how much AI traffic gets misfiled vary widely — analytics consultancy AuthorityTech has put the misclassified share anywhere from roughly a third to two-thirds of AI sessions — so treat any single number as a rough guide, not a constant.

Four Ways to See Your AI Traffic Today

1. Build a regex segment for AI domains

The fastest fix that works in every GA4 property: create a segment that matches session source against the known AI referrer domains.

In GA4, open Explore → Free form, drag Session source into the segment definition, and match it against a regex like chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai|grok\.com. Save it as a reusable segment and apply it to your acquisition and landing-page reports. This surfaces the AI traffic that did arrive with a referrer or UTM — it cannot resurrect sessions that carried neither.

2. Use GA4's native AI Assistant channel

In mid-May 2026, Google began rolling out a dedicated AI Assistant channel inside GA4's Default Channel Group — announced as live on May 13, 2026, and widely covered by analytics practitioners since. GA4 now automatically classifies sessions from recognized AI assistants (ChatGPT, Gemini, Claude, Copilot, and others) so they appear as their own row in Reports → Acquisition → Traffic acquisition instead of hiding inside Referral or Direct. No configuration is required for the default channel grouping.

Two honest limits: first, the channel only recognizes known AI referrers and UTMs — a session whose referrer was stripped by an app webview or by AI Mode's noreferrer still lands in Direct. Second, if your property uses custom channel definitions, you may need to add the AI Assistant grouping to them manually. It is a genuine improvement, not a complete fix.

3. Tag the links you seed in AI-visible content

You cannot control how ChatGPT links to you, but you can control the URLs you publish in the places AI tools read: documentation, FAQ pages, comparison pages, and your llms.txt file if you maintain one. When you tag those destination URLs with your own UTM parameters — for example utm_source=ai-content&utm_medium=referral&utm_campaign=geo — the parameters usually survive being quoted, scraped, or cited, and any resulting session is attributable in GA4 no matter what happened to the referrer header.

Keep two rules: use lowercase values consistently (mixed case splits your reporting into duplicate rows), and never use utm_source=chatgpt.com on links you place yourself — that fabricates provenance and double-counts against ChatGPT's own tagging. For the full convention set, see our UTM parameters guide.

4. Measure at the redirect instead

The structural weakness in all three GA4 approaches is that measurement starts after the landing, when the referrer may already be gone. A tracked short link moves the measurement earlier: when someone clicks sinkto.link/your-alias, the referrer is recorded at the redirect hop itself — server-side, before any header can be stripped by the destination context — and the visitor is forwarded on instantly.

That is why redirect-level tracking sees AI traffic GA4 misses. Every Sinkto.Link link gets a per-link analytics view with the referrer breakdown for each click: chatgpt.com, perplexity.ai, gemini.google.com show up as rows in the referrer report even when the same visitor's GA4 session collapsed to Direct. You also get country and city, device, browser, a time-series of clicks, and all five UTM parameters captured on the redirect — free, with unlimited links. Start with a free Sinkto.Link account →

What GA4 Still Can't Tell You

Even with all four methods running, gaps remain. GA4 cannot retroactively audit Direct sessions — a misfiled June session stays misfiled forever. The AI Assistant channel only knows the sources Google has recognized, so newer or niche assistants lag until Google's definitions catch up. Sessions from surfaces you have no page analytics on at all — a partner's site, an app listing, a PDF an AI tool quoted you in — are invisible to GA4 by definition, because GA4 only measures pages where your tag runs. And GA4 has no reliable way to separate an AI agent fetching your page from a human browsing it; that is a separate problem we cover in bots vs. buyers: how to read agentic traffic.

A 15-Minute Setup That Catches Most AI Traffic

• Minutes 0–5: Build the AI-domain regex segment in GA4 Explore and save it. Check whether your property shows the AI Assistant channel in Traffic acquisition yet (rollouts phase in; custom channel groupings need a manual add).
• Minutes 5–10: Pick the one URL you share most often, create a free Sinkto.Link short link with a readable custom alias, and replace the raw URL wherever you distribute it.
• Minutes 10–15: Open the link's referrer report and familiarize yourself with the per-click breakdown — country, device, browser, referrer — so an AI domain stands out the day it appears.

Then repeat for the links you seed in AI-visible content. If you want the broader playbook — UTM conventions, agent filtering, GEO campaign measurement — it is all in our complete guide to AI link management.

Frequently Asked Questions

Why does ChatGPT traffic show up as Direct in GA4?

GA4 names a session's source from UTM parameters or the browser's referrer header. ChatGPT's app and webview often send no referrer, and Google's AI Mode explicitly marks outbound links noreferrer. With neither signal, GA4 falls back to Direct. ChatGPT does append utm_source=chatgpt.com to many outbound links, which is why some sessions attribute correctly — but coverage is inconsistent, so a share always leaks into Direct.

Does GA4 have a native AI channel now?

Yes. GA4 rolled out a dedicated AI Assistant channel in the Default Channel Group in mid-May 2026 (reported live May 13). It automatically classifies sessions from recognized AI assistants like ChatGPT, Gemini, Claude, and Copilot in Traffic acquisition reports. It only recognizes known AI referrers and UTMs, though — sessions whose referrer was stripped still file as Direct.

How do I create an AI traffic segment in GA4?

Open Explore, start a free-form report, and create a segment where Session source matches the regex chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai|grok\.com. Save it and apply it to acquisition and landing-page reports. It surfaces AI sessions that arrived with a referrer or UTM; it cannot recover sessions that carried neither.

Can short links track ChatGPT traffic when GA4 can't?

Yes, because the measurement happens at the redirect hop rather than after landing. Sinkto.Link records each click's referrer server-side before forwarding the visitor, so chatgpt.com or perplexity.ai appear in the link's referrer dashboard even when the same session collapses to Direct in GA4. You also get country, city, device, browser, click time-series, and any UTM parameters — free, on unlimited links.

Is ChatGPT traffic real people or bots?

Both. Real users click through from answers, but AI agents and prefetchers also fetch links programmatically, and they can fire JavaScript-based analytics just like a browser. Treat sudden spikes with zero downstream engagement skeptically, and separate agent-looking sessions from human ones before reporting. We break down the signals in our agentic traffic guide.

Next Steps

AI referrals are only going to grow, and every month they spend inside "Direct" is a month of uncredited channel performance. Build the GA4 segment today, check the AI Assistant channel, and put one tracked redirect in the path of the audience you most want to measure.

Create your free Sinkto.Link account →

Related reading: ChatGPT's UTM and branded links update · AI agent traffic: bots vs. buyers · How to track link clicks

Updated: August 2026. GA4 behavior — including the AI Assistant channel rollout and ChatGPT's UTM tagging — and competitor features verified August 2026. Sinkto.Link capabilities described reflect the live product. Have feedback? Contact us.