You can’t improve what you can’t see, and most analytics setups hide AI traffic. Visits from ChatGPT, Perplexity, and other assistants get mixed into generic referrals or vanish into “Direct.” Meanwhile, bold claims circulate about how valuable AI SEO visitors are. This guide covers the practical setup in GA4, the blind spots that remain, and how to judge conversion claims with a cool head.
What GA4 now does by default
For a long time, GA4 had no AI channel. That has partly changed. One analytics guide reports a built-in “AI Assistant” channel live since 13 May 2026, and another confirms it reports tools like ChatGPT, Gemini, and Claude separately from Referral. Check this in your own property, since rollouts and naming can differ. seoquickmadx
The same guide lists real limits: the channel does not backfill history, so earlier sessions stay in Referral and Direct, it does not recover sessions without a referrer, and it reportedly excludes Perplexity. Because these details come from third-party write-ups, confirm them against your reports before relying on them. For that reason, a custom channel group is still worth building.
Build a custom AI channel group
The setup takes about ten minutes. In GA4, go to Admin, then Data display, then Channel groups, and create a new group with an “AI Traffic” channel. Set the condition to Source matches regex. A starting pattern, adapted from published guides, is:
chatgpt.com|chat.openai.com|perplexity.ai|claude.ai|copilot.microsoft.com|gemini.google.com
Two practical notes. A looser pattern is helpful because a rule that matches only exact domains may miss variants like www.perplexity.ai. And order matters: GA4 assigns traffic to the first matching rule, so if Referral sits above AI Traffic, your AI visitors will be classified as generic referrals before the AI rule is checked. Place the AI channel above Referral, then review the source list quarterly, since new assistants appear often. rightblogger1clickreport
The blind spots
No setup captures everything. The main gaps:
- Missing referrers. Many AI clients strip or omit the referrer for privacy or technical reasons, and Claude’s web app is inconsistent. One breakdown notes that the ChatGPT mobile app does not pass a referrer and lands in Direct.
- Google’s AI features. AI Overviews traffic is folded into Organic Search with no separation.
- The size of the hidden pool. Loamly’s analysis of 446,405 visits reported that 70.6% of AI traffic arrived without referrer headers and showed up as Direct. That is a vendor’s dataset, so read it as a warning about undercounting rather than a precise rate.
The honest conclusion: what GA4 shows is a floor, not the total.
A three-bucket attribution model
Because exact tracking is impossible, Sarkar SEO suggests reporting AI influence in three buckets. This is our own working approach, not an industry standard.
- Confirmed. Sessions with a recognizable AI referrer, captured by your channel group.
- Probable. Direct sessions that land on deep, specific pages with no marketing history, especially when a page you recently saw cited in an AI tool shows a matching bump. Label this an inference, never a measurement.
- Influenced. Evidence that AI shaped the decision without leaving a trail: branded search growth, demo or contact forms with a “How did you hear about us?” field that includes an “AI assistant” option, and mentions during sales calls.
Report the buckets separately. Merging them would inflate the number and invite doubt.
Tag what you control
For links you place yourself, such as a profile or a shared resource, use consistent UTM conventions. One guide suggests setting utm_source to values like chatgpt, claude, perplexity, or gemini. Tagging won’t help for organic citations, but it keeps your own campaigns from muddying the data.
Weighing the conversion claims
Studies suggest AI visitors are valuable, but the numbers vary so widely that none should be quoted as fact.
- A study of 312 B2B firms by Opollo found a 14.2% conversion rate for AI referrals versus 2.8% for Google organic.
- Other 2026 analyses report signup conversion around 15.9% for ChatGPT-referred traffic and 10.5% for Perplexity.
- SE Ranking found AI visitors spent 68% more time on site than traditional search visitors.
Treat the pattern with caution. Many of these figures are published by tools that sell AI visibility, and definitions of “conversion” differ. Visitors who click through from an AI answer have already been pre-qualified by a conversation, so some of the lift probably reflects selection, not a magic channel. Volumes are also small, which makes percentages jumpy. Your own data matters more than any average.
Platform share varies too. Conductor data puts ChatGPT at 87.4% of AI referral visits, while SE Ranking’s study gives it 74.8%, with Gemini at 11.6% and Perplexity at 7.2%. Another source shows ChatGPT at 55 to 60% and Perplexity at 18 to 22%. That spread is itself the lesson: check your mix.
A monthly reporting routine
- Export sessions, engaged sessions, and conversions for the AI channel.
- Compare against organic search using the same conversion definitions.
- List landing pages receiving AI visits and note which topics they cover.
- Review Direct traffic to deep pages for suspicious growth.
- Add form responses and sales mentions to the “influenced” bucket.
- Pair this with your manual prompt tests, so you can connect citations to visits.
Keep the report to one page. Leadership needs a trend and a decision, not a data dump.
Common mistakes
- Reporting a tiny, noisy sample as proof of high conversion.
- Forgetting to reorder channel rules.
- Counting every Direct visit as AI-driven.
- Ignoring bot activity. AI crawlers are not human visitors, and one analytics vendor advises blocking them from analytics and tracking them in bot management instead. clickport
- Treating the channel as the only scoreboard for AI SEO.