Skip to main content

Scrunch Metrics Reference: Explorer Names and API Fields

Every Explorer metric, breakdown and filter, with the API field it maps to and what it measures.

Scrunch names each measurement in two places: the Explorer picker and the API field the Query API and MCP return. This page ties the two together, plus the breakdown dimensions and filters each metric supports.

For a quick lookup, the table at the top of each section is all you need.

Need these definitions programmatically instead of from the UI? The Scrunch MCP's get_metric_glossary tool returns the same field definitions, so an AI assistant connected to Scrunch quotes the same numbers this page does.


How to read a metric entry

Every metric follows the same shape, so you can skim to the piece you need:

Field

What it tells you

Definition

A plain-English, one-sentence description of what the metric counts.

Formula

The exact numerator/denominator or scoring rubric behind the number.

Why it matters

The business question this metric answers.

When to use it

When to reach for this metric instead of a similarly-named one.

Watch out for

The most common misreading of this specific number.

Metrics with easily-confused siblings (the Citation family especially) get the full entry below their family's table. Simpler, harder-to-misread metrics get a shorter version that skips fields with nothing new to say.


How Explorer maps to the API

Every metric in Explorer has an entity scope — Brand, a Competitor, a Sub-brand, or (for some metrics) a pooled "All" — and the field name changes with it, via a prefix swap:

Entity scope

Field prefix

Example (Mentions Rate)

Your brand

brand_

brand_presence_percentage

A competitor

competitor_

competitor_presence_percentage

A sub-brand

sub_brand_

sub_brand_presence_percentage

Pooled "All" (brand + every active competitor)

market_

market_presence_percentage

Pooled "All" (sub-brands)

sub_brand_market_

sub_brand_market_presence_percentage

Entity-agnostic (no prefix at all)

—

citation_rate, responses, weighted_index

The tables below show the brand-scoped field. Swap brand_ for competitor_ or sub_brand_ for that entity's version of the same metric, or for market_ (or sub_brand_market_) when a metric supports a pooled "All" scope.

Which endpoint actually returns this field

Scrunch has three ways to pull this data, all drawing from the same fields:

API

Endpoint

Use it for

Docs

Query API (simple)

GET /v1/{brand_id}/query

Straightforward dimension + metric pulls, BI tools that prefer URL params

Query API (structured)

POST /v2/query/{brand_id}

Post-aggregation thresholds (having), negated filters, period-over-period comparison in one call

Responses API

GET /v1/{brand_id}/responses

Raw response text, individual citations, per-response detail — not aggregated

The GET and structured (POST) Query endpoints share the same dimensions and metrics — structured just accepts a richer JSON body. Every metric, breakdown, and filter on this page works through both. The Scrunch MCP's query_metrics tool wraps the structured endpoint, and get_metric_glossary returns these same field definitions programmatically. The Responses API differs in kind: it returns one row per AI response rather than an aggregate, so it can't answer "what's our rate" directly — combine it with the Query API per Metrics you cannot reproduce from the Responses API if you're building your own data mart from responses.


Metrics

Mention

In Explorer, pick

API field

Endpoint

Mentions Rate

brand_presence_percentage

Query (GET / structured)

Mentions Total Responses

brand_unique_responses

Query (GET / structured)

Mentions Unique Prompts

brand_unique_prompts

Query (GET / structured)

Formerly called Brand Presence. Mentions Rate is the same calculation once labeled "Brand Presence" (or "Presence %") on the dashboard, Home page, and Data Studio connector — renamed for clarity, not recalculated.

Mentions Rate

  • Definition: Share of responses whose text names your brand — regardless of tone, and regardless of whether you're also cited as a source.

  • Formula: brand_presence_percentage = (responses naming the brand) ÷ (total responses). Brand and competitor mentions use the same detection logic, so the two are directly comparable.

  • Why it matters: The core "are we part of the conversation at all" number — the widest, simplest AI-visibility signal, and usually the first one teams track.

  • When to use it: Default choice for overall AI visibility tracking. Reach for Citations Rate instead when the question is "is AI pulling from our content as a source," not "is AI talking about us."

  • Watch out for: Citations of your domain do not count here — a page of yours can be cited without your brand ever being named in the answer text. That's tracked separately, by Citations Rate.

Mentions Total Responses

Responses naming the brand, one count per response regardless of how many times the name appears. A volume complement to the rate above — not comparable period-over-period the way a rate is, since raw counts scale with how many responses you collected.

Mentions Unique Prompts

Distinct prompts with at least one brand-mentioning response. A coverage question ("how much of our prompt set are we showing up for") rather than a rate question.


Sentiment

In Explorer, pick

API field

Endpoint

Sentiment Average

brand_sentiment_score

Query (GET / structured)

Sentiment Average

  • Definition: The average tone of responses that mention your brand, expressed as a single 0–100 score.

  • Formula: Each qualifying response scores positive = 100, mixed = 50, negative = 0; brand_sentiment_score is the mean across responses that mention the brand. Responses scored "Unclear" (the none band) are excluded from the average, not counted as a middle value.

  • Why it matters: Tells you not just whether you're mentioned but how — an early-warning signal for competitive disadvantage (AI naming you while recommending someone else).

  • When to use it: Track this as your headline sentiment number. For the underlying distribution (positive vs. mixed vs. negative), break down by Sentiment band instead of inferring it from the average — 85 does not mean "85% positive."

  • Watch out for: AI responses are rarely outright negative about a brand — most negative-band responses reflect a competitor being recommended instead, not explicit criticism. A falling Sentiment Average usually signals competitive framing, not reputational attack. See Understanding Sentiment in Scrunch for the full walkthrough.


Position

In Explorer, pick

API field

Endpoint

Position Average

brand_position_score

Query (GET / structured)

Position Average

  • Definition: How prominently your brand appears within responses that mention it, as a single 0–100 score.

  • Formula: Among responses that mention the brand: top-of-response = 100, middle = 50, bottom = 0; brand_position_score is the mean. Calculated only over responses where the brand appears — an absent response doesn't pull the number down.

  • Why it matters: A rough analogue to SEO ranking position — how close to the top of the answer you land, not just whether you appear.

  • When to use it: Track placement trends over time or across platforms; break down by Position bucket for the Top/Middle/Bottom distribution instead of the averaged score. Don't over-index on the absolute score alone — as with SEO, attention drops off sharply after a response's first section, and it's unclear how much of a long answer users actually read.

  • Watch out for: Like Sentiment Average, this only covers responses where the brand is already mentioned — it says nothing about how often you're mentioned at all. Read Mentions Rate and Position Average side by side rather than combining them into one "dominance" number.


Rank

In Explorer, pick

API field

Endpoint

Rank Average

brand_avg_rank

Query (GET / structured)

Rank Average

  • Definition: On average, how far into the response your brand's first mention falls, relative to other entities mentioned in the same response.

  • Formula: brand_avg_rank averages the first-occurrence mention rank (1 = mentioned first) over responses where the brand received a rank; unranked responses are skipped, not scored as bad. Lower is better — Explorer's delta indicator flips its good/bad coloring accordingly.

  • Why it matters: A finer-grained signal than Position's three tiers: are you the first brand AI names, or the fourth?

  • When to use it: Use alongside Position Average when list-style responses ("here are 5 options for X") are common in your category and simple top/middle/bottom buckets feel too coarse.

  • Watch out for: This is a raw number (e.g. 2.3), not a 0–100 score like Sentiment or Position — don't read it on the same scale.


Citation

In Explorer, pick

API field

Endpoint

Citations Rate

brand_citation_rate

Query (GET / structured)

Citations Share of Voice

brand_citation_share_of_voice

Query (GET / structured)

Citations Total

brand_citation_count

Query (GET / structured)

Citations Unique Responses

brand_citation_unique_responses

Query (GET / structured)

Citations Unique Domains

brand_citation_unique_domains

Query (GET / structured)

Citations Response-Domain Pairs

citation_unique_response_domains (entity-agnostic)

Query (GET / structured)

Most "the numbers don't match what I remember" questions trace back to this family, because five of its six metrics answer subtly different questions.

⚠️ If Citations Rate looks lower than the "citation rate" you remember from before Explorer: the legacy dashboard's headline citation number used a citing-responses-only denominator. That calculation now lives in Explorer as Citations Share of Voice, not Citations Rate. Citations Rate is a new default metric introduced with Explorer, using a wider all-responses denominator instead. Both numbers are correct — they're just answering different questions.

See Understanding Citation Metrics in Scrunch for the full comparison.

Citations Rate

  • Definition: Share of all responses (whether they cite anything or not) that cite at least one URL you own.

  • Formula: brand_citation_rate = (responses citing ≥1 brand-owned URL) ÷ (total responses). Domain-based — matched against your registered brand websites — and independent of whether your brand is mentioned by name in the text.

  • Why it matters: Tells you whether your content is a source AI draws from, as distinct from whether AI talks about your brand at all.

  • When to use it: Explorer's default, all-responses denominator for "how often are we cited." Use Citations Share of Voice instead when you want to know how you compare among responses that cite something — a smaller, more competitive denominator.

  • Watch out for: Being mentioned isn't the same as being cited, and being cited isn't the same as being cited prominently — track Mentions Rate, Citations Rate, and Position Average as separate signals rather than assuming they move together.

Citations Share of Voice

  • Definition: Of the responses that cite anything at all, the share that cite a source you own.

  • Formula: brand_citation_share_of_voice = (responses citing a brand-owned source) ÷ (responses citing any source at all). Each citing response counts once toward this share, no matter how many of your pages it cites.

  • Why it matters: Measures how reliably you show up when citations happen at all — a coverage/consistency signal, distinct from raw volume.

  • When to use it: Most teams find this more actionable than Citations Rate for strategic tracking, since it isolates your performance from swings in how often AI cites anything at all in your category. Use Citations Total instead when the question is raw competitive volume, not consistency.

  • Watch out for: A high Citations Total alongside a comparatively low Citations Share of Voice usually means AI cites you deeply (several pages) in a smaller set of responses — a sign of content depth, not underperformance.

Citations Total

  • Definition: The raw count of citation occurrences pointing at a brand-owned URL, across all responses.

  • Formula: brand_citation_count = total citation events where the source is brand-owned. If one response cites four of your pages, that's four toward this count.

  • Why it matters: A volume measure — useful for competitive positioning ("we account for X citations vs. competitor Y's Z") and for tracking overall citation volume in your category.

  • When to use it: Pair with a Citation Source Owner breakdown for the brand/competitor/other composition of your citation volume. Reach for Citations Unique Responses instead if repeat citations within one response are inflating this number beyond what you want to compare.

  • Watch out for: Multiple citations in one response all count separately here, so this number can look large relative to Citations Share of Voice — a count-based vs. response-based distinction, not a bug (see the side-by-side comparison in Understanding Citation Metrics in Scrunch).

Citations Unique Responses

  • Definition: Distinct responses that cite at least one brand-owned source.

  • Formula: brand_citation_unique_responses = COUNT(DISTINCT response) where a brand-owned citation is present.

  • Why it matters: The numerator you'd use to hand-verify Citations Rate or Citations Share of Voice against a specific response count.

Citations Unique Domains

  • Definition: Distinct brand-owned hosts that appear in at least one citation.

  • Formula: brand_citation_unique_domains = COUNT(DISTINCT domain) among brand-owned citations, www-stripped.

  • Why it matters: How many different pages or sections of your site are earning citations, versus concentration on one URL.

Citations Response-Domain Pairs

  • Definition: The number of distinct (response, domain, owner) combinations across all citations.

  • Formula: citation_unique_response_domains — entity-agnostic. A response citing one domain under four URLs counts once; a response citing six different domains counts six. Owner is part of the key, so subdomains with mixed owners split across owner slices.

  • Why it matters: The reconciliation field — use it, broken down by Citation Source Owner or Citation Domain, whenever a citation count needs to match a per-source-and-owner grain exactly, since Citations Total (a raw URL count) uses a different grain.

  • When to use it: Pair with a domain-grain breakdown. Don't pair it with a Citation URL or Domain Topics breakdown — those change the counting unit and the totals stop reconciling.


Citation Mention Rate

In Explorer, pick

API field

Endpoint

Citation Mention Rate

brand_citation_mention_rate

Query (GET / structured)

Citation Mention Rate

  • Definition: Of the URLs cited in AI responses, the share whose page content (not the AI's answer text) actually names your brand.

  • Formula: brand_citation_mention_rate = (distinct cited URLs whose page text mentions the brand) ÷ (distinct cited URLs). The denominator is cited URLs, not responses — a different grain from every other metric on this page.

  • Why it matters: A quick sanity check on why a third-party page is earning you a citation — is your brand actually named on the page AI pulled from?

  • When to use it: Use it to audit specific citing pages, not as a substitute for Mentions Rate — that's determined directly from what the AI said, not from what a cited page contains.

  • Watch out for: A "No" here doesn't mean your brand is missing from AI's answer — it only reflects whether Scrunch could detect your name in that page's plain-text HTML. Bot-blocking (Cloudflare, Datadome) and JavaScript-rendered content are common reasons for a false "No." See Understanding the "Brand Present" Column in Citations for the full explanation.


Influence Score

In Explorer, pick

API field

Endpoint

Influence Score

weighted_index (entity-agnostic)

Query (GET / structured)

Influence Score

  • Definition: How influential a cited source is, combining how often it's cited with how many different questions it's cited for.

  • Formula: weighted_index = (citations of this source ÷ total citations in the group) × (distinct prompts that cited it).

  • Why it matters: Separates a source influential across many different topics from one that got a single high-volume hit on one popular prompt.

  • When to use it: Requires a Citation Domain or Citation URL breakdown to mean anything — without one, there's no group to compute a share against and the chart returns no data. Reach for Citations Total instead for a simple citation-volume ranking with no prompt-diversity weighting.

  • Watch out for: Without the required breakdown applied, this metric is meaningless by design, not broken — always confirm a domain or URL breakdown is in place before reading the number.

  • Worked example: A source cited 30 times out of 300 total group citations (a 10% share), appearing across 12 distinct prompts → Influence Score = 0.10 × 12 = 1.2.


Share of Voice

In Explorer, pick

API field

Endpoint

Share of Voice

brand_share_of_voice

Query (GET / structured)

Share of Voice

  • Definition: Your brand's mentions as a share of total mentions across the active competitive set, normalized so every entity's slice sums to 1.

  • Formula: brand_share_of_voice — unlike Mentions Rate (each entity's own independent rate), Share of Voice is a normalized pie: every tracked entity's slice adds up to 100%.

  • Why it matters: Answers "of all the attention going to brands in our category, how much of it is ours" — a relative-share question, distinct from Mentions Rate's absolute-rate question.

  • When to use it: Use this for competitive-share reporting and pie/donut visuals. Reach for Mentions Rate instead for each entity's own independent visibility number — mentions overlap across entities, so individual Mentions Rates don't have to sum to 100%, and can exceed it. See Understanding Competitive Presence in Scrunch for why an aggregate presence number and individual competitor numbers don't add up.


Total Responses and Unique Prompts

In Explorer, pick

API field

Endpoint

Total Responses

responses (entity-agnostic)

Query (GET / structured)

Unique Prompts

unique_prompts (entity-agnostic)

Query (GET / structured)

Coverage metrics — "how much data do I have," not "how visible are we." Both are entity-agnostic (no brand/competitor scope to pick).

Total Responses and Unique Prompts

  • Total Responses: All responses collected in the selected range, regardless of which entities are mentioned. Use it to sanity-check sample size before trusting a percentage — Explorer's tooltips already show this alongside every rate (e.g. "43% (37 of 86 responses)").

  • Unique Prompts: Distinct prompts with at least one response in the range. Coverage of your monitored prompt set, not a mention-based count — use Mentions Unique Prompts instead if you want "how many prompts is the brand showing up for."

  • Watch out for: Neither is directly comparable period-over-period the way a rate is — a rising Total Responses count usually just means you added prompts or platforms, not that visibility changed.


Breakdowns

A breakdown splits a metric into one series per value. Apply up to 3 at once — not every breakdown works with every metric family; the notes below say which.

Breakdown

API dimension

Works with

Notes

Platform

ai_platform

All metrics

AI platform display name (OpenAI, Claude, Gemini, Perplexity, Microsoft Copilot, Google AI Overview, Google AI Mode, Meta, Grok).

Stage

stage

All metrics

Customer-journey stage; brand-specific, since stages are customizable per brand.

Persona

persona_name

All metrics

Topic

prompt_topic

All metrics

Prompt

prompt

All metrics

One series per unique prompt text.

Competitor

competitor_name

Mention, Sentiment, Position, Rank, Citation, Citation Mention Rate, Share of Voice

Explorer auto-flips a brand-scoped metric to its competitor binding when this breakdown is applied, so you don't have to change the metric's entity yourself. Not available alongside Influence Score or Total Responses / Unique Prompts (no competitor binding).

Citation Domain

domain

Citation, Citation Mention Rate, Influence Score only

Source-grain: only meaningful alongside a citation-family metric. High cardinality; the chart caps to top-25 series. Required (with Citation URL) for Influence Score to return data.

Citation Source Owner

owner

Citation, Citation Mention Rate, Influence Score only

Brand / competitor / other, three-way partition.

Citation URL

source_url

Citation, Citation Mention Rate, Influence Score only

Highest cardinality of all breakdowns; table-oriented. Alternate qualifying breakdown for Influence Score.

Citation Segment

citation_segment

Citation, Citation Mention Rate, Influence Score only

Your configured citation segments, plus an "Unsegmented" catch-all.

Domain Topics

source_topic

Citation, Citation Mention Rate, Influence Score only

The cited source's topic tags; "Untagged" when none are configured.

Content Delivery Status

content_delivery_status

Citation, Citation Mention Rate, Influence Score — brand scope only

Whether AXP is serving optimized content for the cited page. Not meaningful under a competitor or sub-brand entity — a competitor's citations can never match your own registered sites, so every row collapses into one bucket.

Sub-brand

sub_brand_id

Mention, Sentiment, Position, Rank, Citation (excl. Response-Domain Pairs), Share of Voice

Only available when every metric in the view can bind to a sub-brand — Explorer auto-flips compatible metrics onto the sub-brand grain the same way it does for Competitor.

Country

country

All metrics

Two-letter country code.

Tag

tag

All metrics

Position bucket

position_bucket

Brand, Competitor, and pooled "All" scopes

Top / Middle / Bottom third of the response. Not available on the sub-brand path.

Sentiment band

sentiment_band

Brand, Competitor, and pooled "All" scopes

Positive / Mixed / Negative / Unclear. Not available on the sub-brand path.

Rank

rank

Brand, Competitor, and pooled "All" scopes

Raw integer mention rank; "how often are we #1, #2, …". Not available on the sub-brand path.


Filters

Filters narrow the responses a metric is computed over. Apply up to 8 at once.

Filter

API dimension

What it filters on

Platform

ai_platform

AI platform display name.

Stage

stage

Customer-journey stage display name.

Branded query

branded

Whether the prompt names the brand explicitly.

Sub-brand type

ownership

Include brand or competitor sub-brands (defaults to both); usable only alongside sub-brand-scoped metrics.

Search enabled

ai_platform_search_enabled

Whether the model ran with web search enabled.

Position bucket

position_bucket

Top, Middle, or Bottom.

Sentiment band

sentiment_band

Positive, Mixed, Negative, or Unclear.

Persona

persona_name

The user persona a prompt was written for.

Topic

prompt_topic

The topic a prompt belongs to.

Prompt

prompt_id

A specific prompt template.

Country

country

Two-letter country code.

Tag

tag

User-authored prompt tag.

Competitor

competitor_name

A tracked competitor.

Source Type

source_type

Citation, Maps card, or Shopping card.

Citation Segment

citation_segment_id

A configured citation segment (filter-only — use the Citation Segment breakdown to group by segment name).

Citation URL

source_url

A specific cited URL.

Citation domain

domain

A specific cited domain.

Filter values that read differently in the API

A few filter options are labeled for readability in the product but stored under a different value. Send the stored value when filtering through the API.

Filter

Shown in Explorer

Sent to the API

Platform

ChatGPT

OpenAI

Platform

Copilot

Microsoft Copilot

Platform

Meta AI

Meta

Branded query

Branded

true

Branded query

Unbranded

false

Sub-brand type

Brand

own

Search enabled

Search-enabled

true

Search enabled

Model-only

false

Sentiment band

Unclear

none

Source Type

Maps card

map

Source Type

Shopping card

shopping


Limits

  • Up to 5 metrics in one view.

  • Up to 3 breakdowns at once.

  • Up to 8 filters at once.


Dimensions available through the API only

A handful of fields the MCP glossary and Query API accept aren't surfaced anywhere in Explorer today:

  • persona_id, competitor_id — the numeric IDs behind Persona and Competitor. Explorer always uses the name-based dimension (persona_name, competitor_name) instead.

  • source_domain — a citation host dimension computed on a different query path than Explorer's Citation Domain breakdown (domain); it can't be combined with citation metrics and isn't filterable. Prefer domain for anything Explorer-facing.

  • cited_competitor_name — the source-grain sibling of the Competitor breakdown, used only for citation metrics. Explorer's Competitor breakdown auto-substitutes this when a citation metric is active, so it never got a separate picker entry — a duplicate "Competitor" option tested as more confusing than helpful.

  • has_sponsored_ads (filter-only) — whether a response displayed a sponsored ad. This is gated behind a rollout flag and isn't yet available as an Explorer filter.


Developer docs

Did this answer your question?