Qwen share of voice tracking
Qwen share of voice is reported separately for commercial and informational prompts, each with its own interval, because a single blended figure hides the only distinction that matters on this engine.
How it renders
Derived across the sample set, split by prompt intent.
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 Qwen for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "qwen",
"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 →Qwen share of voice FAQ
- Why split by intent on Qwen specifically?
- Because Alibaba's commerce data drives the commercial answers and the open web drives the informational ones. They are effectively two engines.
- What sample size?
- n=30 per intent bucket, not n=30 across both.
Report Qwen share the way it actually behaves
We will scope both intent buckets and quote the credits for each.
Other Qwen data
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →