Step 1: Custom GA4 channel group for AI Assistants
In GA4 → Admin → Data Display → Channel Groups, create a custom group with an 'AI Assistants' channel matching these source patterns: chat.openai.com, chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, you.com, bing.com/chat. Place the channel above 'Referral' in priority so AI traffic is captured before falling into the generic referral bucket.
This single change typically surfaces 40–60% of previously invisible AI-assistant traffic in our audits.
Step 2: Server logs catch what GA4 misses
Server logs (Cloudflare, Vercel, AWS, Nginx) capture every HTTP request including the Referer header, even for visits where client-side GA4 attribution failed. Filtering server logs weekly for the same AI referrer hosts surfaces an additional 20–40% of AI traffic that GA4 attributes to 'Direct'.
The gap between server-log AI traffic and GA4 AI Assistants channel traffic is your true measurement undercount. Most sites we audit show a 30–50% gap.
Step 3: Search Console CTR-drop patterns for AI Overviews
Google AI Overview clicks are bundled inside organic Google traffic in GA4, with no native breakdown. The available proxy is to monitor Search Console queries where impressions stayed flat or grew but CTR dropped 30%+ versus the prior period. These queries are likely losing clicks to AIO-featured answers.
Track brand search volume month-over-month as the trailing indicator of AI exposure you can't directly attribute. Sites cited frequently by AI assistants typically see 15–40% year-over-year brand search growth independent of paid brand activity.