Segment AI-Agent Traffic in GA4 (and Why It Lands in Direct)

Google added an "AI Assistant" channel to the GA4 Default Channel Group on 13 May 2026, with broad availability across properties reached by early June. It requires no setup: when a session's HTTP referrer matches Google's own list of recognized AI-assistant domains, GA4 assigns the session medium ai-assistant and the reserved campaign value (ai-assistant), and buckets it under the new channel alongside Organic Search, Paid Search, Direct, and Referral in the standard channel precedence order.

That is a real improvement over the prior state, where any AI-assistant click-through landed in plain Referral, indistinguishable from a link from any other website. But the mechanism is the same fallback logic GA4 has always used for channel assignment - it reads a referrer header against a list. It does not detect an agent by behavior, by header signature, or by anything happening after the click. If the referrer isn't there, or isn't on the recognized list, the channel doesn't fire.

For the slice of agent traffic that does carry a referrer - just not one on Google's built-in list - a custom channel group closes the gap without touching the Default Channel Group other reports depend on.

1. Admin > Data display > Channel Groups > Create custom channel group.
2. Add a new channel above where Direct or plain Referral would otherwise match - GA4 evaluates channel-group rules top to bottom and stops at the first match, so ordering decides the outcome.
3. Define the rule on Session source, using a regex condition matching the referrer domains you want to catch beyond Google's default list - perplexity.ai is the clearest current gap; add any other assistant domain your traffic actually shows once you've checked it.
4. Name the channel something explicit ("AI Agent Referral," not "Other") so it doesn't get missed in a dropdown later.
5. Save. This channel group only reclassifies sessions that already sent a referrer-carrying hit - it does not, and cannot, create visibility into the referrer-less or API-driven traffic covered in section 02.

Direct is GA4's catch-all, not a real acquisition channel - it means "no stronger signal was present." Two distinct agent behaviors both land there for that reason, not because GA4 misidentified anything:

• No referrer sent. Many agent browsing clients and headless fetchers don't send an HTTP referrer header at all, or strip it. GA4 applies the exact same rule to that session as it would to a human who typed the URL directly - no referrer, no UTM, no click ID, so Direct.
• No hit sent. An agent that completes a purchase, a form submission, or any other action through a direct API call to your backend never opens a browser tab and never runs your GA4 tag. There is no session for GA4 to assign to any channel, Direct included, because no event ever reached the property.

Neither case is a channel-group problem. A channel group can only relabel a hit GA4 already has; it can't manufacture a hit that was never sent. Capturing agent activity that arrives with no referrer and no client-side execution is exactly the problem server-side capture solves - firing the event from your own server, tag server, or request log, with the agent identified from headers or a signed signature rather than a referrer, and attached at collection time instead of guessed at afterward. That build is covered in capturing agent traffic server-side when no JavaScript fires - the piece this GA4 setup is meant to feed into, not replace.

1. Reports > Acquisition > Traffic acquisition > change the primary dimension to your new custom channel group (or add it as a secondary dimension alongside Session default channel group). A passing result shows sessions bucketed under your named agent channel instead of Direct or Referral.
2. Realtime report > Traffic acquisition card. Trigger a test visit carrying a known-agent referrer (or a manually set UA/header matching one you're targeting). A passing result surfaces under your custom channel within roughly 30 seconds - if it still shows under Direct or Referral, the rule order or regex condition is wrong, not the concept.
3. For the referrer-less/API gap specifically: once the server-side bridge is sending events, check Admin > DebugView for hits carrying your agent-identifying parameter (for example a custom parameter distinguishing server-fired agent events from browser-fired ones). A passing result shows the parameter present and populated on the server-sent event; its absence means the bridge isn't attaching agent context, not that GA4 failed to receive anything.