How to Track AI Traffic in GA4

By Amit Patel

GA4’s default channel groupings were built before AI assistants became a meaningful referral source, and they still don’t isolate that traffic — a click from a ChatGPT answer or a Perplexity citation typically lands in Organic Search, Referral, or Direct depending on how the link was constructed, blending it invisibly into channels it doesn’t belong in. This guide covers building a custom channel group that separates it out.

Why This Matters

If AI-referred visitors behave differently — different engagement rate, different conversion rate, different content preferences — blending them into Organic Search hides that difference entirely and can lead to wrong conclusions about “organic” performance overall. Separating the channel is the only way to actually see whether this traffic source deserves distinct treatment in content or measurement strategy going forward.

Known AI Referrer Patterns

ChatGPT’s in-answer links typically carry a referrer or landing parameter tied to chat.openai.com or chatgpt.com; Perplexity referrals commonly show perplexity.ai as the referrer; Gemini referrals can arrive via gemini.google.com or blend into google.com’s own referrer depending on surface. These referrer domains and patterns shift as each product evolves its link format, so treat any specific list as a starting point to verify against your own raw referrer data (Admin > Traffic acquisition, sorted by session source) rather than a permanent rule.

Building a Custom Channel Group

Under Admin > Data display > Channel Groups, create a new custom channel group with a rule matching Session source contains any of your known AI referrer domains, placed above the default Organic Search rule so it takes precedence in the evaluation order. GA4 evaluates channel group rules top to bottom and stops at the first match, so an AI-referral rule placed below Organic Search will never fire — ordering is not cosmetic here, it’s functional.

The Real Limits of This Approach

This method only catches sessions where the AI product’s own link carries an identifiable referrer — many AI-assistant surfaces (voice interfaces, some in-app browsers, copy-pasted URLs from an answer) don’t pass a referrer at all and land in Direct traffic, invisibly. Treat any AI-traffic number built this way as a floor, not a ceiling: the true volume of AI-influenced visits is very likely higher than what a referrer-based channel group can ever detect.

Frequently Asked Questions

The Bottom Line

A custom channel group is the only practical way to see AI-assistant traffic as its own category in GA4 today, but treat the resulting number as a conservative floor — real AI-influenced traffic almost certainly runs higher than what referrer matching alone can detect.