| utm_source | perplexity |
| utm_medium | ai-assistant |
| utm_campaign | (set per campaign) |
| utm_id | (set per campaign) |
| utm_term | (set per campaign) |
| utm_content | (set per campaign) |
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 — it means Perplexity actively sends people to the pages it draws from. The catch is the same one every AI surface shares: there’s no console where you configure tracking.
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 visit — a genuine referral that Perplexity’s interface deliberately encourages.
The link Perplexity shows is your canonical URL, not a wrapped or rewritten tracking link. So the UTMs that exist on a Perplexity citation are exactly the ones already on the page when Perplexity indexed it. Tag nothing, and the visit arrives untagged.
How its traffic appears in analytics
Like other assistants, Perplexity clicks can arrive with a missing or opaque referrer. When that happens, client-side analytics can’t attribute the session and GA4 files it as (direct)/(none) — lumped in with people typing your URL directly. Your Perplexity traffic is real but invisible inside Direct.
When a referrer is present, it’s typically perplexity.ai. That’s a useful confirmation, but it’s not guaranteed on every click, so the reliable signal is the UTM you put in the URL yourself.
The UTM convention to apply
You tag the canonical links you control that Perplexity may cite — the URLs in your published content, the pages you expose to crawlers, anywhere a link of yours could become a Perplexity source.
| Parameter | Value | Why |
|---|---|---|
utm_source | perplexity | Identifies the answer engine. Lowercase — casing creates duplicate rows. |
utm_medium | ai-assistant | The value GA4’s native AI Assistants channel recognizes. Especially important for Perplexity, which GA4 doesn’t auto-detect by referrer. |
utm_campaign | (optional) | Add only when the link belongs to a specific initiative. |
For how the receiving end handles this — how GA4’s native AI Assistants channel recognizes utm_medium=ai-assistant, and why the bare value ai still sits in Unassigned — see Google Analytics .
Limitations and gotchas
- No click ID, no macros. There’s no
gclid/fbclidanalog and no click-time substitution. Pre-placed UTMs are the whole game. - You can’t tag a link the model composes itself. If Perplexity surfaces a URL it constructed rather than your tagged canonical, your parameters won’t ride along.
- Casing splits reports.
Perplexityandperplexityare two sources in GA4. Lowercase everything, everywhere. - Use
ai-assistant, notai. GA4’s native AI Assistants channel recognizesutm_medium=ai-assistant; the literalaiisn’t recognized and still parks in Unassigned. Perplexity isn’t auto-detected by referrer either, so the tag is what classifies it. - Referrer is unreliable.
perplexity.aiconfirms a click when it shows; it won’t always show. Treat the UTM as primary.
Verification
- Inspect a tagged citation target. Open one of your tagged canonical URLs and confirm
utm_source=perplexity&utm_medium=ai-assistantsurvives any redirect chain. - Confirm the AI Assistants channel. Tagged sessions should classify under GA4’s native AI Assistants channel. If they land in Unassigned instead, the medium is probably the bare
airather thanai-assistant. - Cross-check
perplexity.ai. Where the referrer appears, confirm it aligns with your UTM-tagged sessions so you know the convention holds.
Perplexity won’t give you a tracking parameter, but its citation-first design means the traffic is there to be measured — if you tag the links you own. For the full strategy, read how to track AI traffic across ChatGPT, Perplexity, and Gemini, the UTM convention for the AI search era, and whether AI referral traffic should get its own GA4 channel.
