Microsoft Copilot share of voice tracking
Copilot share of voice is cheap to compute because collection here is cheap. It belongs in a coverage table, not on the cover slide.
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 Microsoft Copilot for the share of voice field, sampled n times and returned as one object per prompt.
{
"engine": "copilot",
"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 →Microsoft Copilot share of voice FAQ
- How much does Copilot share matter?
- As coverage completeness, meaningfully. As a driver of traffic, far less than the Google surfaces.
- What n is enough?
- Twenty is generally plenty given the surface's stability and low cost.
Cover Copilot without over-reporting it
We'll add it to your engine mix with reporting context built in.
Other Microsoft Copilot data
Across every engine
Compare how share of voice behaves on every engine we track.
Share of voice across all engines →