GA4 is useful for measuring visitors who arrive from AI services and then interact with your website. It is not a complete source of AI crawler traffic: many requests never execute the browser tag, and bot filtering can exclude activity.
Review human referrals
- Install and verify your normal GA4 tag and consent configuration.
- Open the traffic acquisition report and review session source/medium.
- Look for identifiable AI-service referral sources in the data your site actually receives.
- Compare landing pages, meaningful interactions, and conversions for those sessions.
- Keep the reporting date range and definitions consistent when comparing trends.
Some AI links omit a referrer or open in environments that hide it. Such visits may appear as direct traffic; a referral report does not count every AI-assisted visit. Do not label all direct traffic as AI traffic.
Measure crawlers separately
A browser-side user-agent check only sees clients that execute it. It cannot recreate requests missing from browser analytics. Use server/CDN logs or the answer.cloud Cloudflare Worker for request-level agent analytics.
Keep requests, human sessions, answer citations, and on-site chat interactions separate. Review GA4 traffic acquisition documentation and the visibility metrics guide before drawing conclusions from a single traffic source.