Perplexity behaves more like a search engine than a chatbot: it answers a question, then shows its work with a numbered list of cited sources, each a clickable outbound link. That citation model is good news for marketers — Perplexity actively sends people to the pages it draws from, and those clicks generally arrive with a referrer your analytics can read.
Perplexity as a traffic source
Each Perplexity answer is built from sources it found, and those sources appear as outbound citations users click to read the full thing. When someone clicks a citation pointing at your page, you get a genuine referral visit.
The link Perplexity shows is your canonical URL, not a wrapped or rewritten tracking link. That’s why there’s nothing to configure — and, as covered below, why tagging is actively counterproductive.
How its traffic appears in analytics
Perplexity clicks typically arrive with a perplexity.ai referrer, and your analytics classifies them from it. Where they land differs by tool:
- In GA4: under Referral, source
perplexity.ai. GA4’s native AI Assistants channel fills from a list of assistant referrers, and Google names ChatGPT, Gemini, Deepseek, Copilot, and Grok. Perplexity isn’t among them, and Google doesn’t publish the list exhaustively. So the traffic is correctly sourced and fully visible — just not in the AI Assistants row. - In AnyTrack: the Campaign Report assigns every session a channel from the referrer and URL parameters, with conversions attached.
Some clicks arrive with no referrer at all and land in (direct)/(none). That slice is unrecoverable by any means.
Getting Perplexity into an AI channel — the right way
If you want one row that answers “how much traffic came from AI assistants,” widen the definition in GA4’s admin rather than tagging your pages:
- In Admin → data stream reporting settings, create a custom channel group (you get a limited number, so plan the whole thing at once).
- Add a channel named AI Assistants.
- Give it a condition catching both halves: session medium exactly matches
ai-assistant— which picks up everything GA4 already detected — OR session source matchesperplexity.ai(andclaude.ai, which is in the same position). - Order it above Referral and Direct. Rules evaluate top-down and first match wins.
This reads referrer data GA4 already collected. It doesn’t ask you to publish a falsified medium on your own pages.
For how the receiving end classifies all this, see Google Analytics .
Limitations and gotchas
- No click ID, no macros. There’s no
gclid/fbclidanalog and no click-time substitution — and none is needed, because the referrer identifies the source. - You can’t tag a link the model composes. There is no convention that injects parameters into a URL generated inside someone else’s product.
- Referrer-less clicks are a hard floor. They land in Direct and nothing recovers them. Report the AI number as a known undercount.
- Custom channel groups aren’t retroactive. They apply going forward. Historical sessions stay classified as they were.
- Server-side capture is the durability fix. It preserves sessions that did carry a referrer but would otherwise be lost to ad blockers, consent gates, and fast bounces.
Verification
- Find the referral row. In GA4, open Traffic acquisition and switch the dimension to Session source.
perplexity.aishould appear under Referral without any setup. - Confirm your canonical URLs are bare. Open the pages Perplexity is most likely to cite and check the address carries no
utm_parameters. - Test the custom channel group. After creating it, confirm
perplexity.aisessions move into your AI Assistants channel and out of Referral, and that the rule sits above Referral in the ordering.
Perplexity’s citation-first design means the traffic is there and already attributed. The work isn’t tagging — it’s reading the right report. For the full strategy, read how to track ChatGPT, Perplexity, and Gemini traffic, why AI search needs no convention of its own, and how GA4’s native AI Assistants channel works.
