Share of Voice (SOV)

Share of voice measures a brand's presence in a category — impressions, spend, mentions — against total category activity. Competitive research is only valuable when it changes a decision. Public ad libraries show you what rivals are running and roughly how long it has been live — a strong proxy for what is working, because losers get switched off. The mistake is copying execution instead of reading strategy. Read it next to Competitive Spend, Competitor Analysis.

The calculation itself is simple — SOV = Brand Ad Presence ÷ Total Category Presence × 100 — and the judgement is entirely in the inputs and the window you choose. Sample systematically: the same set of competitors, on the same cadence, across the same placements. Record the offer, the hook, the format and how long the asset has been in market. Turn the pattern into a hypothesis you can test in your own account, not into a lookalike file. Worked through: Your brand runs 12,000 ad impressions in a market where the top 5 competitors run 100,000 total = 12% SOV.

Track longevity and repetition rather than volume. An asset live for eight weeks is a stronger signal than fifty assets launched last Tuesday. Watch relative presence over time so you can tell a genuine push apart from routine rotation. Why this matters commercially: SOV above natural market share correlates with future market share gains — the Byron Sharp / Ehrenberg-Bass insight.

Once a pattern is worth testing, Xeli turns it into a template applied across your own catalog in a single run, so you can be in market with your version of the idea inside a day instead of briefing it for a week. In the context of competitive intelligence, that means the concept stops being something a person re-applies by hand every campaign and becomes a rule the system enforces on every asset it produces.

The recurring problems are predictable: measuring sov only in owned channels; ignoring share of search as a real-world sov proxy; comparing sov without adjusting for market share. Each of these is a process gap rather than a knowledge gap — which is why the fix is usually a checklist, a template or an automated rule instead of more training.