Practical guide · Search topic: track Claude AI referral traffic
How to track Claude referral traffic
Tracking Claude referrals starts with your analytics source report. Filter the received referrer values for Claude-related domains, then check the landing pages and what visitors did next. This gives a view of clicks that reached your site, not the full set of Claude recommendations.
What the query can—and cannot—measure
Keep the original source field in your report even if you also group it into an AI channel. The raw value makes the rule auditable if domains change. If the report shows no Claude visits, check the date window, tracker deployment and filters before concluding that no one clicked.
A practical way to do it
Compare by date and landing page, and use a meaningful conversion event if one exists. For a tiny sample, read the individual aggregate rows rather than presenting a precise conversion rate as stable evidence.
A useful checklist
- Filter the referrer/source list for Claude-related values.
- Check the landing page and session outcome.
- Verify the measurement setup before interpreting zero.
Limits to keep in mind
Referrer presence varies. A Claude mention may produce no click, and a click may be classified as direct when source information is absent.
Questions
Does this show Claude answers that mention my brand?
No. It shows only attributable visits to your site.
Should I use a custom channel?
You can, if the rule is documented and preserves the raw source value.
Sources and further reading
Related pages
AI search referrals · quietstats cookie-free analytics Goals and funnels · quietstats cookie-free analytics Methodology: how quietstats counts visitors, visits, bounce rate and duration
Put your traffic in context
Explore the product, its measurement method and pricing before choosing a tool.