Measure the people Perplexity sends to your website.
See attributable Perplexity referrals, the pages those visitors use, and separate server-side requests from PerplexityBot and Perplexity-User.
Perplexity analytics should distinguish people who click a cited result from Perplexity's own retrieval and indexing requests. Chad connects human referrals to website behavior while reporting crawler requests as a separate metric.
Clicks and retrieval are different signals
A crawler reading a pricing page does not prove that a person later visited or bought. Chad preserves that boundary in reports and queries.
- Perplexity referral: an attributable human browser visit from Perplexity.
- Perplexity-User: a page fetch initiated to answer a user request.
- PerplexityBot: a crawler request used to discover and index public web content.
Follow the visit beyond the landing page
With the browser tracker installed, Chad can connect an observed Perplexity referral to anonymous sessions, top pages, goals, funnels, and attributed revenue when those features are configured.
Track crawler demand at the server
Install the optional server adapter to observe known crawler requests that browser JavaScript cannot see. Ask in Slack, Teams, or through the read-only MCP server which public paths Perplexity requested.
Common questions
Can Chad see which Perplexity answers cite my site?
Chad measures observed referrals and crawler requests. It does not claim to monitor every answer or citation produced by Perplexity.
Why do Perplexity clicks sometimes appear as Direct?
Some AI products or browser flows may suppress referrer information. Without a valid attribution signal, Chad reports the visit conservatively.
Does PerplexityBot run the website tracker?
Generally no. Crawler activity requires server-side request tracking.