Doubao share of voice tracking
Doubao share of voice is reported over successful collections only, with the access success rate stated alongside, because account attrition on this surface is real and hiding it would distort the figure.
How it renders
Derived across successful samples, with a 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 Doubao for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "doubao",
"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 →Doubao share of voice FAQ
- What is a normal Doubao success rate?
- Lower than any other engine we run. We publish the number in every delivery.
- Do you farm accounts to improve it?
- No. We run genuine accounts at low rate and accept the lower throughput.
Get Doubao share with the success rate attached
We will quote realistic throughput rather than a number we cannot hit.
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →