Visitors from ChatGPT, Perplexity, Gemini, and Claude are already landing on your site, but GA4 is filing most of them under "Referral" or "Direct" where they vanish into noise. That hides the real payoff of your GEO work. This guide walks you through building a dedicated AI Search channel group in GA4 so you can see AI-referred sessions cleanly, compare their behavior to organic search, and prove the ROI of showing up in AI answers.
You will end with a custom channel that captures the major AI platforms, a way to sanity-check it, and a plan for the Bing and Copilot traffic that resists tracking.
Key takeaways
- AI-referred visitors arrive pre-qualified: they read a summarized answer, then clicked for detail, so they convert differently from cold organic traffic and deserve their own channel. - GA4 does not have an AI Search channel by default; you build one with a custom channel group that matches the AI referral domains. - The core domains to capture in 2026 are `chatgpt.com`, `openai.com`, `perplexity.ai`, `gemini.google.com`, `bard.google.com`, `claude.ai`, `anthropic.com`, and `copilot.microsoft.com`. - Copilot and Bing Chat traffic often masks itself inside `bing.com` or Direct, so treat those numbers as a floor, not the full picture. - GEOly pairs the on-site GA4 view with the off-site half of the funnel, connecting AI visibility to sessions through its GA4 integration.
Step 1: Know the AI referral domains you are hunting for
Before touching GA4, list the domains AI platforms actually send clicks from. As of 2026 the main ones are ChatGPT (`chatgpt.com`, `openai.com`), Perplexity (`perplexity.ai`), Google Gemini (`gemini.google.com`, and legacy `bard.google.com`), Claude (`claude.ai`, `anthropic.com`), and Microsoft Copilot (`copilot.microsoft.com`).
Microsoft is the awkward case. Copilot and Bing Chat traffic frequently shows up under `bing.com` mixed with ordinary Bing search, or falls into Direct entirely. You can still capture the clean `copilot.microsoft.com` referrals; just know the Microsoft slice is understated.
Gotcha: this list drifts as platforms launch new surfaces and share domains. Revisit it each quarter and add any new referrers you spot in your raw referral report.
Step 2: Create a custom channel group in GA4
In GA4, open Admin, then under the property column find Data settings and Channel groups. Create a new custom channel group, name it something like "AI Search default," and start from a copy of the default grouping so you keep the standard channels intact.
Add a new channel at the top of the ordering called AI Search. Ordering matters: GA4 assigns each session to the first channel whose conditions match, so AI Search must sit above Referral and Organic Search or those channels will swallow the traffic first.
Gotcha: a custom channel group is not retroactive in every report and can take up to a day or two to populate fully. Do not panic if the channel looks empty an hour after you create it.
Step 3: Write the matching conditions
Define the AI Search channel with a condition on the session source. Set "Session source" to match a regex that covers your domain list, for example:
`chatgpt\.com|openai\.com|perplexity\.ai|gemini\.google\.com|bard\.google\.com|claude\.ai|anthropic\.com|copilot\.microsoft\.com`
Using "matches regex" keeps the rule in one line and easy to extend. When a new AI referrer appears, you add it to the same pattern rather than creating another channel.
Gotcha: escape the dots in the regex (`\.`) so `chatgpt.com` does not accidentally match unintended strings. And confirm you are matching source, not medium, since AI referrals usually carry a `referral` medium.
Step 4: Reinforce tracking with UTMs where you control the link
You do not control the link ChatGPT renders, but you do control links you place in AI-friendly locations, and any citations you can influence. Wherever you can append parameters, tag them with a consistent `utm_source` (for example `utm_source=chatgpt&utm_medium=ai`) so those sessions land in your channel deterministically instead of relying on referrer detection.
This matters because some AI clients strip or mask the referrer, which is exactly why Copilot leaks into Direct. UTMs are your fallback signal.
Gotcha: keep UTM values lowercase and consistent. `ChatGPT` and `chatgpt` become two different sources in GA4 and split your data.
Step 5: Build a report and watch behavior, not just volume
Volume is only half the story. Create an exploration or a comparison in the Traffic acquisition report filtered to your AI Search channel, and put engagement rate, average engagement time, and conversions next to your Organic Search channel.
The pattern you are looking for: AI-referred sessions often show higher intent because the visitor already read a summary and clicked for specifics, frequently landing straight on pricing or product pages rather than top-of-funnel content. Watching conversions by landing page tells you which AI answers are sending buyers, not browsers.
For the full analytics build, including a Looker Studio dashboard on top of this channel, see the deep guide on [tracking GEO and analyzing AI traffic in GA4 and Looker Studio](/blog/how-to-track-geo-analyze-ai-traffic-ga4-looker-studio).
Step 6: Close the loop with off-site visibility
GA4 tells you what happened after the click. It cannot tell you how often you appeared in AI answers, whether you were cited, or how a competitor's Share of Model compares. That off-site half is where GEOly fits: it tracks your visibility, mentions, and citations across ChatGPT, Gemini, Perplexity, Copilot, and Grok, then connects that to on-site sessions through its GA4 integration.
Read together, the two halves answer the real question: not just "how much AI traffic did I get," but "which AI answers drove it, and where am I losing the ones I should be winning." Learn more about the platform in [what GEOly AI is](/blog/what-is-geoly-ai).
How to verify your channel works
Send yourself a test: open your site from a real Perplexity or ChatGPT answer that links to you, complete a session, then wait a day and check whether that session appears under AI Search rather than Referral. Cross-check the raw source/medium report to confirm the domain matched your regex. If the test session lands in the right channel, your grouping is live.
FAQ
Why does AI traffic show up as Direct? Some AI clients strip the referrer, and app-based flows often carry no source at all, so GA4 defaults them to Direct. UTMs on links you control are the fix.
Will this channel change my historical data? Custom channel groups apply going forward and can reprocess some reports, but do not assume full retroactive coverage. Set it up early.
Is Copilot trackable at all? Partially. Clean `copilot.microsoft.com` referrals are captured; the portion that blends into `bing.com` or Direct is harder to isolate without a dedicated GEO tool.
Do I need a separate channel per platform? No. One AI Search channel with a regex is simplest. If you want per-platform splits, use a secondary dimension on session source inside the report instead of many channels.
How does GEOly help beyond GA4? It measures the off-site side GA4 cannot see, your appearance and citations in AI answers, and ties it back to traffic. See the guides from [GEOly AI](/blog/author/geoly-ai).
