Skip to content
Acquisition

See where demand starts

People sent by an assistant are not crawlers.

Reveliqo recognises referral traffic from ChatGPT, Claude, Perplexity, Gemini and Copilot where it is technically observable — through referrer, UTM parameters or integration data. Coverage depends on what each assistant passes. These are human visits, held apart from AI crawler activity, which is bot traffic and belongs in Traffic Quality.

AI Referrals

  • Assistant referral detection and grouping
  • Separation from AI crawler traffic
  • Landing pages assistants send to
  • Conversions and revenue per assistant

How it helps

What AI Referrals gives you

1

Two things, one name

An assistant crawling your documentation and a person arriving from an answer share a brand name and nothing else. The crawler is identified at the edge by user agent and network, kept in Traffic Quality, and never counted as a visit here.

2

Observable, and stated as such

Detection depends on the referrer, parameter or integration data each assistant provides, and that varies by assistant and by surface. A visit that cannot be identified stays in Direct rather than being guessed into a group.

3

Measured like any other channel

Assistant referrals carry landing pages, conversions and revenue exactly as Organic Search does. Where the volume is small and the conversion rate is not, an outcome-ranked table shows it and a session-ranked one does not.

Connect a site today. Read tomorrow's brief instead of building it.

Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.

Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo