Full Answer

Google launched the AI Assistant channel in GA4 on May 13, 2026, automatically grouping traffic from ChatGPT, Gemini, DeepSeek, Copilot, and Grok into a single reporting bucket. The channel relies on referrer-header matching against a fixed list of domains, and any platform not on that list falls through to generic Referral or Direct.

The gap is not trivial. Perplexity alone accounts for 7.73% of AI referral share (Statcounter, April 2026), and Claude adds another 2.66%. Together with Meta AI, Mistral, Kimi, Doubao, Poe, You.com, and Phind, the undetected platforms represent a growing segment of AI-sourced visits that GA4 silently mislabels. For WooCommerce stores seeing rising direct traffic with unusually high conversion rates, a portion of that traffic is likely AI-referred and invisible to the native channel.

The second blind spot is agentic commerce. AI shopping agents making purchases through MCP integrations or headless browser sessions arrive without referrer headers entirely, so even a perfectly configured AI Assistant channel cannot attribute them. Server-side event tracking with source-level tagging is the only reliable way to close both gaps — capturing the platforms GA4 misses and the agent transactions it cannot see. Fixing GA4 AI traffic attribution covers the practical implementation.