Why AI visits hide in Referral and Direct
GA4 files a visit by where it came from. A click from a chat answer that brings its referrer along becomes chatgpt.com / referral and lands in Referral, next to every blog that ever linked you. Three more ways GA4 AI referral traffic goes missing:
- No referrer at all. Apps, in-app browsers and copied links often arrive without one. GA4 calls that Direct, and no filter can pull it back out.
- A UTM with no medium. ChatGPT adds
utm_source=chatgpt.comto many links. Without autm_mediumnext to it the medium is (not set), and the session can end up in Unassigned. - Google's own AI. Clicks from AI Overviews and AI Mode count as Organic Search; Google's channel definitions say so. There's no way to split them from regular Google clicks.
GA4's built-in AI Assistant channel
In 2026 Google added an AI Assistant channel to GA4's default channel group. Its definition names ChatGPT, Gemini, DeepSeek, Copilot and Grok as examples, leaves out AI Overviews and AI Mode, and doesn't publish the full list of assistants it recognises. Fine as a start. The catch is you can't read that list: if an assistant you care about still shows up under Referral, it isn't on it.
Your own channel fixes that. You pick the hostnames, you can read them, and it matches on the session source, so the UTM-tagged ChatGPT visits count too. Put it above Referral, and above Google's AI Assistant channel if your list has one, so each AI visit lands in one bucket, not two.
What to do with the number
Traffic is the end of the chain. Before anyone clicks, an answer has to name you or cite your page. The AI citation tracker records which pages the engines cite; the AI rank tracker records who gets named, and in what order. If your AI numbers sit near zero, first make sure AI crawlers get into your site at all.