AI referrals
AI referrals are visits that Cleotic recognises as arriving from an AI assistant. Open Sources -> AI traffic and choose Referrals only to inspect them.
These are recorded visit events, not a count of unique people or sales. They show detected traffic to your site rather than all occasions when an assistant may have recommended you.
How detection works
Server-side integrations inspect the referring URL and recognised utm_source values. Browser tracking can detect a recognised AI referrer through its beacon. WordPress also offers an optional frontend beacon for referrals on cached pages.
Recognised sources include ChatGPT, Claude, Perplexity, Gemini, Copilot, Meta AI, You.com, Le Chat, Grok, Character.AI, and DuckDuckGo AI.
Choose a setup in AI traffic tracking. A site with only browser tracking has different coverage from a site forwarding eligible server requests.
Review referrals by page
- Select the date range and domain you want to inspect.
- Set Traffic to Referrals only.
- Use provider or source filters to focus on an assistant.
- Open a page row for recent matching evidence.
Check which pages receive visits and whether the pattern persists after a content change. Referral data does not identify the exact answer or prompt that caused every visit.
Why counts may be incomplete
Some assistants and browsers remove referral information. A visit with no recognised referrer or campaign source may not be attributed to AI. Caches, blocked browser requests, and provider filtering can also affect coverage.
A regular direct visit will not normally appear as an AI referral. A connected site with no referral rows can still be working correctly.
AI share also needs eligible total pageviews. If your integration sends AI events only, the share is incomplete even when referral events are visible.