How to Track AI Search Traffic in GA4

AI search engines now send measurable referral traffic to websites, but Google Analytics 4 does not break it out for you. By default, a visit from ChatGPT or Perplexity lands in the generic "Referral" bucket, mixed in with newsletters and partner links — and some of it is misclassified entirely. If you cannot see AI traffic as its own channel, you cannot prove that your AEO and GEO work is paying off. This guide shows how to isolate it.

Why AI traffic is invisible by default

When a user clicks a citation inside an AI answer, the click arrives at your site with a referrer — usually the AI engine's hostname. GA4 records that hostname as the session source, but it has no built-in "AI" channel, so the traffic scatters:

• Most AI referrals land in "Referral", sourced as chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, and similar hostnames.
• Some gets misclassified. Certain assistants route through proxy domains or carry query terms that GA4's default rules push into "Organic Search" or "Unassigned," so the true source is obscured.
• Zero-click answers leave no referral at all. When an engine answers without a click, there is nothing for GA4 to record — which is why citation tracking and a zero-click search strategy matter alongside referral analytics.

The fix is to teach GA4 to recognize AI hostnames and group them into a channel you control.

Step 1: Confirm AI traffic is arriving

Before building anything, verify the sources exist in your data.

1. Open Reports → Acquisition → Traffic acquisition.
2. Change the primary dimension to Session source / medium.
3. In the search box, type each engine in turn: chatgpt, perplexity, gemini, copilot, claude.

If you see sessions against those hostnames, you have AI traffic to track. Note which engines actually send you clicks — that tells you where your citations are converting to visits.

Step 2: Build a custom AI channel group

A custom channel group reclassifies traffic in your reports without touching the raw data, so it is safe and reversible.

1. Go to Admin → Data display → Channel groups.
2. Click Create new channel group — do not edit the default group, so you preserve historical comparisons.
3. Name it something clear, like AI Search.
4. Click Add new channel, name it AI Engines, and add a condition:
   • Dimension: Source
   • Match type: matches regex
   • Value: the regex below.
5. Drag the new channel to the top of the list, above Organic Search and Referral. GA4 assigns each session to the first channel it matches, so AI must rank first or its traffic gets claimed by Referral.
6. Save the channel and the group.

The AI source regex

.*(chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|edgeservices\.net|bing\.com/chat|you\.com|search\.brave\.com).*

Keep this regex in a doc and revisit it quarterly. New engines launch and existing ones change hostnames, so treat the pattern as a living list, not a one-time setup.

Step 3: Create a reusable AI segment

Channel groups work in standard reports; for deeper analysis, build a matching segment in Explorations.

1. Open Explore and start a blank exploration.
2. Create a new Session segment named AI Traffic.
3. Condition: Session source matches regex, using the same pattern as above.

With the segment applied, you can compare AI visitors against the rest of your traffic on any metric — engagement rate, conversions, pages per session — to see whether AI-referred users behave differently from organic search visitors.

Step 4: Report on what matters

Counting sessions is the floor, not the goal. The questions worth answering:

• Which engines send the most traffic? Break the AI channel down by source to see whether ChatGPT, Perplexity, or Gemini is your strongest referrer, and weight your citation work accordingly.
• Which pages earn AI clicks? Cross AI traffic with landing page to learn which articles get cited and clicked. Those are your templates — reverse-engineer what makes them quotable and apply it elsewhere.
• Do AI visitors convert? Compare the AI segment's conversion rate to organic. AI-referred users often arrive with high intent because the engine has already pre-qualified them with an answer.
• Is the trend rising? Track AI sessions month over month. A rising line is the clearest proof that your AI search visibility investment is compounding.

What GA4 still cannot tell you

Referral analytics only captures clicks. They miss the larger story of AI visibility:

• Impressions without clicks. When an engine cites you but the user does not click, you gained authority and brand exposure that GA4 never sees. Pair referral data with direct citation tracking — periodically asking the engines your target questions and logging whether you appear.
• Brand lift. Being named in an answer builds recognition that shows up later as direct or branded-search traffic, not as an AI referral.

Treat GA4 as one instrument in a fuller measurement stack: referral traffic for clicks, citation spot-checks for visibility, and search-console data for the queries feeding the engines.

The bottom line

GA4 will not surface AI search traffic on its own — you have to build the channel. A custom channel group with a maintained hostname regex, a matching segment, and a few focused reports turn invisible AI referrals into a trackable line you can grow. Set it up once, revisit the regex quarterly, and you will finally be able to prove that getting cited is sending real, high-intent visitors to your site.

FAQ

Why doesn't GA4 show AI search traffic by default? GA4 has no built-in "AI" channel, so referrals from engines like ChatGPT and Perplexity fall into the generic "Referral" bucket, and some get misclassified as Organic Search or Unassigned. You have to create a custom channel group that recognizes AI hostnames to isolate the traffic.

What source names do AI engines use in GA4? Common ones include chatgpt.com, openai.com, perplexity.ai, gemini.google.com, claude.ai, and copilot.microsoft.com. Copilot sometimes appears via a proxy domain such as edgeservices.net, so include proxy hostnames in your regex.

Will a custom channel group change my historical data? No. Channel groups reclassify how sessions are displayed in reports, not the underlying event data, and creating a new group leaves the default group intact. The change is safe and reversible.

Can GA4 measure AI citations that don't get clicked? No. GA4 only records sessions that include a click, so zero-click citations are invisible to it. To capture those, supplement referral analytics with direct citation tracking — periodically querying the engines and logging whether your site appears as a source.

How often should I update the AI traffic regex? Review it quarterly. New AI engines launch and existing ones change hostnames or add proxy domains, so the pattern needs occasional additions to stay accurate.