The words teams use for KPI work, defined plainly in one place: the new ones this category introduces, and the analytics terms they sit next to.
This glossary defines 30 terms for running business KPIs, each in one sentence first. It covers the terms the Agentic KPI Ops category introduces, such as AI Operator and closing the loop, and the analytics terms they sit next to, such as mix shift and implied conversion rate. Where a term has a post of its own, the definition links to it.
Agentic KPI Ops: the practice of running business KPIs with AI Operators that carry the work from a change in the number through to an action and a check on it, with people setting the goals and guardrails. It applies the operating discipline that FinOps, RevOps and MLOps brought to their fields to business KPIs. More in What is Agentic KPI Ops?
AI Operator: an AI agent that takes ongoing responsibility for one KPI. It watches the number, investigates what changed, looks for upside, drives the next action inside the guardrails a team sets, and checks whether the action worked.
AgentOps: the practice of operating AI agents in production, measuring the agent itself: cost, latency, failure rate and output quality. AgentOps is about operating AI agents; Agentic KPI Ops is about using AI Operators to drive business outcomes, and a company can need both.
KPI (key performance indicator): a metric a business uses to judge performance, such as conversion rate or add-to-cart rate.
Guardrails: the limits a team sets on what an Operator may do on its own, what needs a person's approval, and what stays with a person.
Closing the loop: carrying one piece of KPI work all the way to a resolution, including a documented "nothing to do here", rather than stopping at an explanation.
Weekly business review (WBR): the recurring meeting where leadership reviews the numbers that run the business. More in how to automate the weekly business review for ecommerce.
KPI war room: an ad hoc cross-team meeting convened to explain a significant metric change. More in alternatives to the KPI war room.
Triage protocol: a fixed order of checks run before any theory about a KPI change is investigated.
Triage: a full investigation of a KPI movement across its segments, drivers and signals, which ends in a cause a person can check.
Hypothesis: a specific, testable claim about why a metric moved.
Falsifiable: a claim is falsifiable if you can state in advance an observation that would prove it false. More in our post on Popper.
Verdict: the result of testing a hypothesis: confirmed, refuted or inconclusive, with the evidence behind it.
Inconclusive: an honest verdict when the evidence does not settle a question, reported instead of a guess.
Grounding: tying every claim to data fetched during the investigation, not recalled from a model's training.
Data in place: reading the systems a company already has, without moving or copying the data into the vendor's own store.
Conversion rate: orders divided by sessions for a given period.
Implied conversion rate: the conversion rate that follows from two other reported numbers, such as orders and clicks. When it cannot be true, a measurement is usually broken.
Mix shift: a change in a blended rate caused by traffic moving between segments rather than by any segment's own rate changing. More in why did our ecommerce conversion rate suddenly drop?
Denominator effect: a change in a ratio caused by a change in how the bottom number is counted.
Channel reclassification: a change in how a reporting tool groups traffic into channels, which can look like a real shift in media.
Basis point: one hundredth of a percentage point. An 80 basis point drop is 0.80 of a percentage point.
Diff: a cell by cell comparison between two sources that should agree. More in how to check an AI analytics tool's numbers against your own reporting.
Revenue leak: revenue a retailer should be earning from existing traffic but is not, because something between the visit and the order is broken or misrouted. More in how to find revenue leaks on a large retail website.
Dead-end session: a visit that lands on a product page where the item cannot be bought.
Upside: revenue or conversion a business could gain from a KPI that is not visibly broken.
Anomaly detection: automatic identification that a metric has left its expected range, usually by forecasting the range statistically.
Product analytics: analysis of behavior inside a product or site, built on a stream of events.
Digital experience analytics: analysis of what a session actually looked like, including replay, heatmaps, errors and friction.
Semantic layer: a governed model that defines what each business metric means, so that different questions return consistent numbers. How these tools differ is in Mixpanel alternatives for enterprise retail.
What is Agentic KPI Ops?
The practice of running business KPIs with AI Operators that carry the work from a change in the number through to an action and a check on it, with people setting the goals and guardrails.
What is an AI Operator?
An AI agent that takes ongoing responsibility for one KPI: it watches the number, investigates what changed, looks for upside, drives the next action inside the guardrails a team sets, and checks whether the action worked.
What is the difference between Agentic KPI Ops and AgentOps?
AgentOps is about operating AI agents and measuring the agent itself. Agentic KPI Ops is about using AI Operators to drive business outcomes. They are different disciplines, and a company can need both.
What is a mix shift?
A change in a blended rate caused by traffic moving between segments rather than by any segment's own rate changing.
What is an implied conversion rate?
The conversion rate that follows from two other reported numbers, such as orders and clicks. When it cannot be true, a measurement is usually broken.
What does closing the loop mean for a KPI?
Carrying one piece of KPI work all the way to a resolution, including a documented "nothing to do here", rather than stopping at an explanation.
What is a revenue leak?
Revenue a retailer should be earning from existing traffic but is not, because something between the visit and the order is broken or misrouted.
Next step: If one of these terms describes a problem you have on a KPI right now, book a demo and bring it.
Salman is the co-founder and CEO of Augmeta. He writes here when he has something he can't shake — usually about why teams keep mistaking dashboards for understanding, and what it would take to fix that.