Skip to main content

Understanding Competitive Presence in Scrunch

Learn why the aggregate Competitor Presence percentage is higher than individual competitor percentages.

Quick Answer

If you're seeing an aggregate Competitive Presence percentage (like 40%) that looks very different from any individual competitor's percentage (like Competitor A at 16%, Competitor B at 12%), that's expected. The aggregate and the individual percentages measure different things, and they're not designed to add up.

Looking for the exact Explorer name or API field for a metric? The Scrunch Metrics Reference lists every metric, breakdown and filter with the API field it maps to.

The individual percentages show how often each specific competitor is mentioned by name (Mentions Rate). The aggregate is either a pooled, volume-weighted mention rate across all tracked competitors (what Explorer calls Market Presence), or a normalized share of mentions across the tracked set (Share of Voice).

These percentages overlap. Multiple competitors can appear in the same response, so you can't add the individual numbers together or simply average them to get the aggregate.


How Competitive Presence Works

The worked examples in this article (like "40% aggregate, 16% top competitor") are illustrative. They show why overlapping mentions make simple math misleading, but they don't correspond to one single Explorer metric that counts "any competitor mentioned" as a strict union. The two real, selectable metrics are Market Presence (API field: market_presence_percentage), a pooled, volume-weighted mention rate across your brand and every active competitor, and Share of Voice (API field: competitor_share_of_voice), where every entity's slice is normalized to sum to 1. Individual competitor numbers come from Mentions Rate (API field: competitor_presence_percentage).

Aggregate Competitor Presence

Where you'll see it: In Explorer, using the Market Presence or Share of Voice metric, broken down by competitor. Explorer allows up to 5 metrics, 3 breakdowns, and 8 filters in a single view.

What it measures: This aggregates all AI responses, across every tracked platform (including ChatGPT), where one or more competitors are mentioned by name, regardless of whether your brand is also mentioned. This helps identify areas where competitors are more prominently featured.

How it's calculated (illustrative): Responses with one or more competitor mentions, divided by total responses.

Example:

  • You collect 100 AI responses

  • 39 of those responses mention at least one competitor

  • Illustrative result: 39% aggregate competitor presence


Individual Competitor Percentages (Mentions Rate)

Where you'll see it: In Explorer, using the Mentions Rate metric (API field: competitor_presence_percentage) with a Competitor breakdown, or in the competitor trend charts.

What it measures: How often each specific competitor is mentioned by name in AI responses, across every tracked platform. This uses the same name-detection logic as brand Mentions Rate, so brand and competitor numbers are directly comparable. Citations of a competitor's domain don't count toward this rate; that's tracked separately by Citations Rate (competitor_citation_rate).

How it's calculated: Responses mentioning Competitor A, divided by total responses.

Example:

  • You collect 100 AI responses

  • Competitor A appears in 16 of them → 16% Mentions Rate

  • Competitor B appears in 12 of them → 12% Mentions Rate

  • Competitor C appears in 10 of them → 10% Mentions Rate

Explorer's rate charts show the underlying sample size in the tooltip, for example "16% (16 of 100 responses)", so you can always check the response count behind a percentage.


Why the Math Doesn't Line Up

The aggregate isn't an average of the individual competitor percentages. In Explorer, the pooled metric, Market Presence (market_presence_percentage), represents the pooled, volume-weighted mention rate across all tracked competitors, not a simple count of responses where any competitor appears.

The individual percentages (Competitor A at 16%, Competitor B at 12%, etc.) show how often each specific competitor is mentioned by name (Mentions Rate).

Why They Don't Match

Competitor mentions overlap. A single response can include:

  • Multiple competitors at once

  • The brand and competitors together

  • Only some competitors

  • Only the brand

  • None of them

So if you looked at 100 responses:

  • Competitor A might appear in ~16

  • Competitor B in ~12

  • Competitor C in ~10

But around 39-40 responses might include at least one competitor (the illustrative aggregate).

Because many of those mentions happen in the same responses, you can't add the individual percentages together or average them to reconstruct the aggregate.


The Overlapping Circles Analogy

Think of it like overlapping circles (a Venn diagram):

Each competitor is its own circle, and they intersect a lot. The illustrative aggregate is the total area covered by any circle, not the size of one specific circle.

The pooled metrics show the combined competitive footprint. Market Presence tells you the volume-weighted mention rate across the whole tracked set, and Share of Voice tells you each entity's normalized share of that footprint, even though competitors might be appearing together in the same responses.


What This Tells You

This is actually a very useful signal, once you know which metric you're looking at.

When the Aggregate is High, But No Single Competitor Dominates

Example: a high aggregate competitor presence, but the highest individual Mentions Rate is much lower

What it means:

  • The competitive landscape is fragmented

  • No single competitor consistently owns the conversation

  • Multiple competitors are getting visibility, but in different responses

  • There's an opportunity to break through since no one dominates

When One Competitor is Close to the Aggregate

Example: a high aggregate competitor presence, and one competitor's Mentions Rate is close to that same level

What it means:

  • One competitor is dominating most of the competitive visibility

  • They're the clear category leader in AI responses

  • Other competitors are barely showing up


How Presences Can Overlap

Scenario (illustrative): A single AI response about "best project management tools"

The response might mention:

  • Your brand

  • Competitor A

  • Competitor B

  • Competitor C

This one response contributes to:

  • Your brand's Mentions Rate ✓

  • Competitor A's Mentions Rate ✓

  • Competitor B's Mentions Rate ✓

  • Competitor C's Mentions Rate ✓

  • The illustrative aggregate competitor presence (only once) ✓

So four competitors appeared, but this illustrative aggregate only increases by 1 response, not 4. There isn't a single Explorer metric that literally counts responses once this way; use Market Presence or Share of Voice for real, selectable numbers, and expect them to be calculated differently than this walkthrough.


Visual Representation and Chart Transitions

The Competitive Presence chart in Explorer initially uses a bar graph to display early data points during the first few collection cycles. This approach ensures clarity while results are still being gathered. Once sufficient data is collected, the chart automatically transitions to a line graph, enabling you to track trends over time. There's no need for manual adjustments; the system handles the transition seamlessly.


Frequently Asked Questions

Is this a bug? The percentages don't add up!

No, this is not a bug. The aggregate and individual competitor percentages measure different things, and they're designed to overlap because multiple competitors can appear in the same response.

Can I average the individual competitor percentages to get the aggregate?

No. The aggregate is not an average of individual competitor percentages. It's a different calculation:

  • Individual percentages (Mentions Rate): How often each specific competitor appears

  • Aggregate (Market Presence): the pooled, volume-weighted mention rate across all tracked competitors, not a count of responses where at least one competitor appears

Because competitors often appear together in the same responses, averaging the individual percentages will give you the wrong number.

Why is the aggregate so much higher than any individual competitor?

This pattern typically points to a fragmented competitive landscape: many different competitors are getting visibility across different responses, but no single competitor dominates. This is common in crowded categories. Keep in mind that Market Presence and Share of Voice are pooled and normalized calculations, so check which metric you're viewing before comparing it directly to an individual competitor's Mentions Rate.

Can competitor percentages add up to more than 100%?

Yes! If you added up all individual Mentions Rate percentages, you could theoretically get over 100% because they overlap. That's exactly why the pooled metrics exist separately: Market Presence represents the pooled, volume-weighted mention rate across all tracked competitors, not a simple count of responses where any competitor appears.

Should I be concerned if the aggregate is high?

Not necessarily. Look at the individual competitor breakdown (Mentions Rate):

  • If one competitor is close to the aggregate, they're likely dominating; focus on them

  • If it's fragmented across many, there's an opportunity to break through since no one owns it

  • Compare to your own brand's Mentions Rate to see how you stack up

How does this relate to citation metrics?

Great question! This follows the same logic as citation metrics. In the legacy Citations dashboard, this was called Citation Share (the donut) versus Citation Consistency (row-level). In Explorer today, the equivalent views are Citations Total broken down by Citation Source Owner (matching the donut's composition) and Citations Share of Voice (the row-level rate).

  • Competitive Presence works the same way: the aggregate and individual numbers are measuring different things

  • In both cases, the metrics overlap because multiple entities can appear in the same response

Did this answer your question?