DeepSeek share of voice tracking
DeepSeek share of voice is computed over the samples where the engine actually answered, with account-blocked runs excluded rather than silently counted as an absent brand.
How it renders
Derived across successful samples, with a collection success rate reported alongside.
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 DeepSeek for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "deepseek",
"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 →DeepSeek share of voice FAQ
- How do you handle blocked runs?
- They are excluded from the share denominator and reported as a separate success rate.
- What sample size does DeepSeek need?
- n=30 is usually enough, but the effective n is lower after exclusions, so we oversample.
Report Chinese share of voice defensibly
We will show you the success rate alongside the share so the number survives scrutiny.
Other DeepSeek data
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →