Google AI Mode share of voice tracking
Share of voice in AI Mode is computed across the fan-out result, so a brand can hold a strong share here while being absent from AI Overviews on the identical query.
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 Google AI Mode for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "google_ai_mode",
"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 →Google AI Mode share of voice FAQ
- Should AI Mode and AI Overviews share be combined?
- No. Report them side by side. Merging them conceals the disagreement that makes the data useful.
- What n do you recommend for AI Mode?
- Thirty as a floor. Fan-out makes this surface noisier than AI Overviews at equivalent n.
Report AI Mode share separately, and defensibly
We'll size sampling for AI Mode's noise profile and price it against your prompt set.
Other Google AI Mode data
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →