Short answer
Clicks on Perplexity citations usually arrive with perplexity.ai as the referrer, so they appear as that source in GA4, Plausible or DataBull. PerplexityBot indexes pages for Perplexity search and follows robots.txt; Perplexity-User fetches pages when someone asks a question. Neither is a visitor. DataBull files Perplexity under its AI channel with the revenue it brings.
How a Perplexity visit arrives
Perplexity answers with numbered citations, and clicking one opens your page. From the website, the browser normally sends perplexity.ai as the referrer, so the visit shows up under that source with no setup. Unlike ChatGPT, Perplexity doesn't document a UTM tag of its own, so you depend on the referrer.
That means the usual gaps apply: a link opened from an app that sends no referrer, or a URL copied out of an answer, arrives as a direct visit. If you share your own link inside a Perplexity page or Space, add ?ref=perplexity so it's counted either way.
PerplexityBot and Perplexity-User
Perplexity documents two user agents, and they do different jobs:
| User agent | What it does | robots.txt |
|---|---|---|
PerplexityBot | Indexes pages so they can appear in Perplexity's results. Perplexity says it is not used to train AI foundation models. | Followed. Allow it if you want to be cited. |
Perplexity-User | Fetches a page when a user's question needs it, and may link to it in the answer. | Generally ignored, because a person asked for the page. |
Neither is a visitor. JavaScript analytics doesn't count them, and DataBull's bot filter drops both before anything is stored. If you see them in server logs, that's Perplexity reading your page, not a person reading it.
Perplexity also publishes the IP ranges its bots use. If a firewall or bot-protection rule blocks unknown crawlers, check it isn't blocking PerplexityBot, or your pages can't be indexed no matter what robots.txt says.
In Google Analytics 4
Look under Reports → Acquisition → Traffic acquisition with Session source as the dimension and search for perplexity. GA4's AI Assistant channel, added in 2026, groups recognized assistants for you, but Google doesn't publish its full list, and the channel only applies from its launch onward. A custom channel group with a regex on the source covers both gaps; the ChatGPT guide has the steps and a regex that includes Perplexity.
In DataBull
Perplexity is part of the AI channel, next to ChatGPT, Claude, Gemini and Copilot, and has its own row under referrers. Because DataBull is connected to your payments (Stripe, Polar, Dodo Payments or Creem), that row shows revenue, sales and conversion rate, and the lifetime value of the customers Perplexity first brought you. Click it to filter every report: which pages Perplexity visitors land on, how far they read, and how long they take to buy. More on the AI channel.
Reading the numbers
Perplexity visits tend to come in small numbers, so judge them on a month, not a day. Three questions are worth answering:
- Which pages does Perplexity send people to? Those are the pages it cites. If one of them is out of date, fix it first: its text is what readers saw quoted.
- Do they stay? Compare reading time and pages per visit with your search traffic. Someone who clicked a citation was usually checking a specific claim, so a short visit isn't always a bad one.
- Do they pay? Conversion rate and revenue per visitor tell you whether Perplexity is a channel worth writing for, or just a source of curious clicks.
What helps Perplexity cite you
- Let PerplexityBot crawl. It's the only way into Perplexity's index. Changes to robots.txt can take up to a day to apply.
- Answer questions plainly. Perplexity quotes specific passages. A page that states the answer near the top, with the facts written out rather than buried in images, is easier to cite.
- Keep facts current and consistent. Prices, limits and features that match across your site and your docs are less likely to be quoted wrong.
None of these guarantees a citation. Measure what arrives, and judge it by sales rather than visits.
Checked in October 2026 against: Perplexity: crawlers, Google Analytics: traffic-source dimensions, Google Analytics: custom channel groups. Spotted something out of date? Tell us.