---
title: "AI Visibility Metrics Dictionary"
description: "Founders and marketing leaders waste weeks reconciling conflicting dashboards because they never agreed on what \"visibility\" means — write a single…"
answer_summary: "Founders and marketing leaders waste weeks reconciling conflicting dashboards because they never agreed on what \"visibility\" means — write a single…"
canonical: "https://nqz.ai/blog/playbook-ai-visibility-measurement-dictionary-define-metrics-before-reporting"
published_at: "2026-07-27T06:37:55.192Z"
updated_at: "2026-09-10T13:23:38.503Z"
author: "nqzai Editorial Team"
category: "Playbook"
tags: ["playbook","growth"]
image: "https://nqz.ai/blog/covers/playbook-ai-visibility-measurement-dictionary-define-metrics-before-reporting.webp"
---

# AI Visibility Metrics Dictionary

Founders and marketing leaders waste weeks reconciling conflicting dashboards because they never agreed on what "visibility" means — write a single dictionary that defines the label, formula, data source, and action trigger for every metric before you look at a single chart.

## Quick Answer

- If your CEO and your product team read the same number differently → write a shared dictionary entry with a label, formula, and context for that metric → because "50,000 mentions" means nothing until everyone agrees what's in the denominator.
- If you're defining "Share of Voice" or any ratio metric → specify exactly what's in the denominator (which competitors, whether generic category mentions count) → because two teams computing SOV differently will get two different, both-defensible numbers.
- If a metric comes from a single data source (e.g., only Twitter) → label it as such rather than calling it "total mentions" → because an unstated data-source limitation is the fastest way to lose credibility with a skeptical stakeholder.
- If you're about to put a metric in a board deck → require a written definition and a named owner first → because an undefined metric in front of investors is a debate waiting to happen.
- If you don't have historical data to set a baseline → use a short pilot period to establish one rather than inventing a target → because a threshold with no basis is worse than no threshold at all.

## The Problem

Most AI companies track "visibility" as a vague blend of impressions, mentions, and search volume, but each stakeholder interprets those numbers differently. The CEO sees "50,000 mentions" and thinks the brand is everywhere; the product team sees the same number and asks how many of those are from real users versus bots; an investor reads "share of voice up 20%" but doesn't know whether the denominator is the entire AI category or just the top five competitors. Without a shared dictionary, the same data point triggers three different strategic debates — and none of them are productive.

**Direct answer:** The root cause is that teams rush to reporting before they define what each metric means, how it's calculated, what data source it comes from, and what action it should drive — and that gap is what a written measurement dictionary is for.

Teams that skip this step tend to build custom dashboards with metrics no one has validated against a standard definition, which produces a reporting culture that rewards "looking good" rather than "being right."

## Core Framework

Every metric must be defined in three layers: **the label** (what you call it), **the formula** (how you calculate it), and **the context** (what it actually means for your business).

### Key Principle 1: Measurement Before Meaning

Take "Share of Voice" as an example. The label is "Share of Voice." The formula is `(Brand Mentions / Total Category Mentions) × 100`. The context is "this metric tells us how much of the AI conversation we own, but it does not tell us whether those mentions are positive or negative." Without the context layer, a rising share of voice can be a crisis signal (people are talking about a bug) or a win (people are praising a new feature). The dictionary forces the team to agree on the context before the number appears in a slide.

### Key Principle 2: Granularity Over Precision

Most AI visibility metrics are aggregates — total mentions, average sentiment, top-line share of voice — and aggregates hide signal. A better approach is to define metrics at the channel level (Twitter vs. LinkedIn vs. Reddit), the topic level (product features vs. pricing vs. ethics), and the time grain (daily, weekly, monthly). For example, "Sentiment Score" should be defined as "average sentiment across all mentions, reported separately for each channel and each product category," which prevents a single "good" sentiment number from masking a terrible spike on one channel.

### Key Principle 3: Attribution Is Part of the Definition

**Direct answer:** Visibility metrics are useless if you can't connect them to actions, so every entry in the dictionary needs a "likely cause of a large move" note — e.g., "if this metric moves more than 10% in a week, the likely cause is a press release, a viral post, a competitor launch, or a platform algorithm change" — otherwise the team burns hours re-deriving the same explanation every time a number jumps.

## Step-by-Step Execution

### 1. Map Every Visibility Metric to a Business Objective

Start with the three objectives that matter for AI companies: **awareness** (is the target audience hearing about you?), **credibility** (are influencers and experts endorsing you?), and **demand** (are prospects searching for you or clicking through?). For each objective, list the metrics that could plausibly serve it:

- Awareness: total mentions, reach, impressions, share of voice.
- Credibility: sentiment score, influencer mention ratio, average authority of citing domains.
- Demand: branded search volume, direct traffic from third-party articles, click-through rate on social mentions.

Then cut any metric that doesn't tie to at least one objective. Founders often keep vanity metrics like "impressions" because they're easy to get, but if impressions don't link to credibility or demand, they're noise.

**Action:** Create a table with columns Metric Name, Business Objective, and Action Triggered:

| Metric Name | Business Objective | Action Triggered |
|-------------|-------------------|------------------|
| Share of Voice (SOV) | Awareness | Increase by 5% → allocate more PR budget |
| Sentiment Score | Credibility | Drop below threshold → launch crisis comms |
| Branded Search Volume | Demand | Grow month-over-month → invest in content marketing |

### 2. Write a One-Sentence Definition and a Formula for Every Metric

Avoid jargon. For "Share of Voice," write: "The percentage of all mentions of AI companies in our defined category that mention our brand." Then write the formula, e.g. `(Our mentions) / (Our mentions + top competitor mentions + generic category mentions) × 100`, and specify the denominator explicitly: which competitors are included, and how you define "generic category mention" (e.g., mentions of "artificial intelligence" without a brand name). Many teams define SOV using only brand mentions and miss the generic category, which inflates the number.

**Action:** For each metric, write a definition paragraph and a formula, plus any classification method used — for example, "sentiment is classified via an NLP model with a confidence threshold of 0.7; mentions below that threshold are dropped."

### 3. Define the Data Source and Collection Method for Each Metric

A metric is only as good as its data pipeline. For each one, specify:

- **Data source** (e.g., a social listening tool, a news feed, a review site).
- **Collection frequency** (e.g., every few hours for social, daily for news).
- **Filtering rules** (exclude likely bots, job postings, non-English mentions).
- **Post-processing** (deduplication by URL, merging of threads).

Many AI visibility metrics get reported from a single source but labeled as "total mentions." The dictionary must admit the limitation.

**Action:** Create a second table: Metric, Data Source, Collection Frequency, Exclusion Rules.

### 4. Set Thresholds and Action Triggers

A metric without a threshold is a number without a decision. For each one, define a baseline (e.g., a trailing 30-day average), an alert threshold (e.g., a large move in a week), and the action taken when it's crossed (e.g., "if SOV drops for two consecutive weeks, marketing runs a targeted paid campaign"). Calibrate thresholds with your own historical data where you have it; where you don't, start with a conservative provisional threshold and tighten it once you have a baseline.

**Action:** Add Baseline, Alert Threshold, and Action columns to the metric table.

### 5. Document the Metric's Lifecycle

Every metric should have a review date. The AI visibility landscape changes fast — new platforms emerge, sentiment models drift, competitor sets evolve. Include a "last reviewed" and "next review" date, and name who owns the metric.

**Action:** Add Owner, Last Reviewed, and Next Review columns.

### 6. Validate the Dictionary Against a Real Data Set

Before rolling the dictionary out company-wide, run it against your last 60 days of data. Check whether the numbers make sense — for example, if your SOV formula includes generic category mentions, check that they aren't an unreasonably large share of the total. This step catches errors in data-source selection and formula logic.

**Action:** Schedule a validation sprint with the data team, produce a sample report, and flag any discrepancy larger than 10% versus the old report.

### 7. Train the Team and Enforce Compliance

The dictionary is useless if people don't use it. Run a short training session for every stakeholder who sees visibility reports, and make it a rule: no metric appears in a board deck unless it's in the dictionary.

**Action:** Publish a one-page cheat sheet in the company knowledge base, and get sign-off from leadership that the dictionary is the official standard.

## Common Mistakes

- Using "impressions" without defining the denominator or the platform — a Twitter impression and a video impression are not comparable.
- Treating sentiment as a single number without context — a 0.6 sentiment score might be great for a product launch but terrible for a crisis response; define sentiment relative to topic and channel.
- Ignoring data-quality thresholds — scraping mentions without filtering bots, spam, or non-English content inflates SOV with noise.
- Mixing cumulative and periodic metrics — "mentions this month" and "mentions all time" are different things and shouldn't be reported side by side without a label.
- Defining metrics without cross-functional buy-in — marketing, product, and investor relations each defining "share of voice" their own way guarantees future disagreement.

## Metrics to Track

- **Share of Voice (SOV)** — percentage of all category mentions that are your brand. Formula: (your mentions) / (your mentions + competitor mentions + generic category mentions). Data source: a social listening tool.
- **Weighted Sentiment Score** — average sentiment weighted by mention authority (domain authority or follower count). Formula: (sum of sentiment × authority) / (sum of authority).
- **Influencer Share of Voice** — percentage of mentions from higher-follower accounts. Formula: (influencer mentions) / (total mentions).
- **Branded Search Volume** — monthly search volume for your brand and product names, tracked via a search-data tool.
- **Topical Diversification Score** — number of distinct topics (product, funding, ethics, hiring) in which your brand is mentioned in a period.
- **Response Rate** — percentage of mentions replied to by your brand's official account.

## Checklist

- [ ] Each metric is mapped to a specific business objective (awareness, credibility, demand).
- [ ] A one-sentence, jargon-free definition is written for every metric.
- [ ] A formula is documented, including the denominator and any weighting.
- [ ] Data source and collection method are specified (source, frequency, filters).
- [ ] Exclusion rules are defined (bots, spam, non-English).
- [ ] Thresholds and action triggers are set (baseline, alert, action).
- [ ] An owner and review date are assigned to each metric.
- [ ] The dictionary is validated against historical data.
- [ ] The team is trained on how to read and use the dictionary.
- [ ] Compliance is enforced: no metric in a board deck unless it's in the dictionary.

## How to Implement the Dictionary in One Week

**Day 1:** Gather the heads of marketing, product, data, and investor relations. List every visibility metric currently used in any report, and for each one ask "what objective does this serve?" Kill any metric without a clear answer.

**Day 2:** Write the one-sentence definition and formula for the remaining metrics in a shared spreadsheet, and assign a data owner and source to each.

**Day 3:** Define thresholds. Pull historical data where you have it and set a baseline; for new metrics, start with a conservative provisional threshold.

**Day 4:** Validate the dictionary against your last 60 days of raw data, fix any formula or data-source mismatches, and document what you found.

**Day 5:** Train the team, send the final dictionary, and require sign-off from stakeholders.

**Day 6 (bonus):** Build a dashboard in your BI tool that reads from the dictionary's definitions, and lock it so users can't quietly edit the formulas.

## FAQ

**What if we don't have historical data to set baselines?**

Run a short pilot (two to four weeks) to collect baseline data and set provisional thresholds. Refine them once you have a real trend to compare against.

**How often should we update the dictionary?**

On a fixed cadence — quarterly is a reasonable default. Update it sooner if you add a new product line, enter a new geography, or a platform meaningfully changes its API or algorithm.

**Can we use the same dictionary for social media and traditional press?**

Yes, but separate the metrics by channel — define "Share of Voice (Social)" and "Share of Voice (Press)" as two distinct entries, since they have different data sources, collection frequencies, and typical baselines.

**What if a metric is defined differently by a third-party tool we use?**

The dictionary overrides the tool's label. If your monitoring tool has its own "Share of Voice" definition, map its output to your dictionary's definition and note the mapping explicitly.

**How do we handle metrics that are only available in paid tools?**

Define the metric anyway, and note the data-source limitation plainly — for example, "branded search volume is estimated via a third-party API that covers desktop search; mobile traffic is not included." Transparency here prevents overconfidence in the number.

**What if the CEO wants to add a new metric mid-quarter?**

Route it through the dictionary owner, who writes the definition, sets the threshold, and validates the data source before it's added to any report.

## Where NQZAI Fits (and Where It Doesn't)

**Direct answer:** NQZAI is a B2B outbound, lead-gen, and SEO/GEO content platform, priced pay-as-you-go at $2 per million tokens with no subscription tiers — it does not have a purpose-built "metric builder" or social-listening ingestion product, so it won't automatically assemble this dictionary or validate it against your historical data for you.

Building and maintaining the dictionary above is a spreadsheet-and-data-pipeline exercise best done with your existing social listening tool, data warehouse, and BI tool. If your visibility work overlaps with content or search-facing work — writing pages that get accurately cited by search engines and AI assistants — that's the part of the workflow NQZAI is actually built for.

## Sources

1. [Moz, "What Is Domain Authority?"](https://moz.com/learn/seo/domain-authority) — background on the authority-weighting concept referenced in the Weighted Sentiment Score example above.