Data AnalyticsFundamentalsbeginner
Updated:

KPIs and Metrics: What Analysts Track

4 min read

A metric is any measurement; a KPI is a metric tied to a goal. Learn the difference, see examples, and how analysts pick and calculate the ones that matter.

TL;DR – Quick Answer

A metric is any quantifiable measurement, such as page views or number of orders. A KPI, or key performance indicator, is a metric chosen because it directly tracks progress toward a specific goal. Every KPI is a metric, but only the few metrics tied to important objectives earn the KPI label. Analysts calculate, monitor and report both.

On This Page

A metric is any quantifiable measurement — page views, order count, response time — while a KPI, or key performance indicator, is a metric singled out because it directly tracks progress toward an important goal. The relationship is one of selection: every KPI is a metric, but only the handful of metrics tied to critical objectives earn the KPI label. Confusing the two, or promoting an impressive-looking metric to KPI status when it drives no decisions, is one of the most common analytical missteps, and untangling them is a core early skill.

KPIs and metrics are the raw material of descriptive analytics, so this page sits close to the types of data analytics and the wider data analytics fundamentals.

Metrics: any measurement

A metric is simply something you can count or measure. Number of website sessions, average cart value, tickets resolved per day, email open rate — all are metrics. They are neutral facts; on their own they carry no judgment about whether the business is doing well. A metric becomes meaningful only when placed against a goal or a comparison point.

KPIs: metrics that matter

A KPI is a metric elevated because it measures something the business genuinely cares about. If the goal is to grow a subscription product, churn rate — the share of customers who cancel — becomes a KPI, because reducing it is central to success. A good KPI is specific, tied to a goal, has a target, and is actionable — the team can actually move it. It usually carries a time frame too: "reduce monthly churn to under 3 percent this quarter."

The danger is the vanity metric — a number that looks impressive but informs no decision, like total lifetime registrations when most of those users are inactive. Vanity metrics create a false sense of progress. Good analysts steer teams toward actionable KPIs that connect to outcomes.

A worked example

This snippet computes two classic KPIs — conversion rate and average order value — from a small sample.

import pandas as pd

# illustrative daily sample data
df = pd.DataFrame({
    "day": ["Mon", "Tue", "Wed"],
    "visitors": [1000, 1200, 900],
    "orders":   [50, 72, 45],
    "revenue":  [12500, 19800, 11250],
})

df["conversion_rate"] = (df["orders"] / df["visitors"] * 100).round(1)
df["avg_order_value"] = (df["revenue"] / df["orders"]).round(0)

print(df[["day", "conversion_rate", "avg_order_value"]])

Expected output:

   day  conversion_rate  avg_order_value
0  Mon              5.0            250.0
1  Tue              6.0            275.0
2  Wed              5.0            250.0

Raw visitors and orders are metrics. Conversion rate (orders divided by visitors) and average order value (revenue divided by orders) become KPIs when the business goal is to improve sales efficiency — they turn neutral counts into indicators of performance you can set targets against. Tuesday's jump in both is exactly the kind of signal a KPI is meant to surface.

How analysts use KPIs and metrics

Analysts spend much of their time defining, calculating and reporting these numbers. A big part of the job is helping stakeholders choose the right KPIs — pushing back when someone wants to track a vanity number, and proposing an actionable one instead. Once chosen, KPIs live on dashboards, monitored over time and compared against targets. When a KPI moves unexpectedly, diagnostic analysis kicks in to explain why, connecting this work to data-driven decision making. The discipline of tracking a small, meaningful set of numbers is what keeps a team focused.

A helpful concept is the distinction between leading and lagging indicators. A lagging KPI reports an outcome after it has happened — last month's revenue, for instance. A leading KPI signals what is coming — the number of qualified sales conversations this week, which predicts revenue weeks ahead. Lagging indicators confirm results; leading indicators let a team steer before the result is locked in. Good dashboards pair the two, so a team both knows how it did and can see where it is heading in time to react.

Pairing every KPI with the right context also prevents misreading. A conversion rate means little without knowing the traffic behind it, and a churn number means little without the customer base it applies to. Analysts add value by always presenting a KPI next to its denominator, its target, and its trend over time, so a single figure never gets mistaken for the whole story.

Common mistakes

  • Tracking too many KPIs. Dozens of headline numbers dilute focus; a handful per team keeps attention where it belongs.
  • Chasing vanity metrics. Impressive totals that drive no decision waste effort and mislead.
  • KPIs with no target. A number without a goal or time frame cannot tell you whether you are winning.
  • Ignoring the denominator. Reporting raw orders without visitors hides whether performance actually improved or traffic just grew.

In interviews

Interviewers frequently ask "What is the difference between a KPI and a metric?" and follow with "What KPIs would you track for this business?" A strong answer defines both, stresses that a KPI is a metric tied to a goal and made actionable, and then proposes specific, sensible KPIs for the scenario — conversion rate for an e-commerce site, churn for a subscription product. Mentioning vanity metrics and the value of tracking few, focused KPIs shows practical judgment beyond definitions.

Where this fits in your learning path

KPIs and metrics are what descriptive analytics actually reports, so this page builds directly on the types of data analytics. It also leads into data-driven decision making, where well-chosen KPIs become the basis for real decisions. Together they show how raw measurements turn into the numbers a business steers by, a central theme of the data analytics hub.

Frequently Asked Questions

What is the difference between a KPI and a metric?
A metric is any number you can measure, while a KPI is a metric selected because it tracks a key business goal. Page views is a metric; if your goal is engagement, average session duration might be a KPI. Every KPI is a metric, but only goal-critical metrics become KPIs.
What makes a good KPI?
A good KPI is specific, measurable, tied to a clear goal, and actionable, meaning a team can influence it. It should have a target and a time frame so you know whether you are on track. Vanity numbers that look impressive but drive no decisions make poor KPIs.
What are examples of common KPIs?
Common KPIs include monthly recurring revenue, customer churn rate, conversion rate, customer acquisition cost, and average order value. Which ones matter depends entirely on the business goal. A subscription company watches churn closely, while a store watches average order value.
What is a vanity metric?
A vanity metric looks impressive but does not inform decisions or reflect real progress, such as total registered users when most are inactive. It can mislead teams into feeling successful without being so. Good analysts favor actionable metrics tied to outcomes over vanity numbers.
How many KPIs should a team track?
Fewer is usually better, often a handful per team, so attention stays on what matters. Tracking dozens of KPIs dilutes focus and makes it unclear which numbers actually drive decisions. Supporting metrics can sit beneath a small set of headline KPIs.

Want to Build Your Career in Data Analytics with AI?

Join CodeBegun and train with working industry engineers — Check the Data Analyst training details

Apply for Demo Class →
Siva Prasad Galaba
Founder, CodeBegun · Staff Engineer

Founder of CodeBegun. 15+ years building Java systems at companies like Crunchyroll. Teaches Java, Spring Boot and system design the way the industry actually works, and mentors students through projects, mock interviews and placement preparation.

Technically reviewed by CodeBegun Technical TeamLast reviewed 16 July 2026 LinkedIn
Chat with us