Perplexity share of voice tracking
Perplexity share of voice benefits from the cleanest input data we have, so intervals tighten faster here than on any other engine at the same n.
How it renders
Derived from mentions and citations across the sample set.
Sampling
This is the field where n matters most. At n=1 the metric is noise; at n=30 the interval is typically tight enough to defend in a client report.
Gotcha
What the API returns
A single collection call against Perplexity for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "perplexity",
"field": "share_of_voice",
"prompt": "best ai visibility tracking tool",
"country": "GB",
"language": "en",
"n": 30,
"share_of_voice": [
{
"brand": "Nostimates",
"share": 0.34,
"ci95": {
"low": 0.2,
"high": 0.52
},
"n": 30
},
{
"brand": "Competitor",
"share": 0.21,
"ci95": {
"low": 0.1,
"high": 0.38
},
"n": 30
}
]
}Response fields
| Key | Type | Notes |
|---|---|---|
| brand | string | Brand from the configured competitor set. |
| share | float | Point estimate across the sample set. |
| ci95 | object | 95% Wilson interval as { low, high }. |
| n | integer | Samples behind the estimate. |
| delta_prior | float | null | Change against the previous run of the same prompt set. |
What it costs
Derived at no extra credit cost, but it scales with n — the interval is bought with samples.
See credit pricing →Perplexity share of voice FAQ
- Does Perplexity need fewer samples?
- Often yes. Cleaner extraction and lower volatility mean n=20 frequently reaches an interval that takes n=30 elsewhere.
- How should I weight Perplexity in a blended report?
- By your client's audience. It punches below Google on volume and above it on B2B relevance.
Get a defensible Perplexity share quickly
This is the fastest engine to stand up. We'll price it against your prompt set today.
Other Perplexity data
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →