What are product metrics?

Product metrics are quantitative measurements that tell a product team how well a product is performing. They track user behavior, business outcomes, and product health, giving teams the evidence they need to make informed decisions about where to invest and what to change.

Good product metrics are not just data points — they are signals. They tell you whether users are finding value, whether the product is growing sustainably, and whether recent changes moved the needle in the right direction.

Why product metrics matter

Without metrics, product decisions rely on intuition and anecdote. These have their place, but they are not sufficient on their own. Metrics provide a common language that teams and stakeholders can use to discuss performance and prioritize trade-offs.

Metrics also create accountability. When a team commits to moving a specific number, it forces clarity about what success looks like and makes it harder to rationalize effort that is not producing results. They are not infallible — a metric can go up for the wrong reasons — but they are a necessary check on purely subjective judgments.

Leading vs. lagging indicators

One of the most important distinctions in product metrics is between leading and lagging indicators.

Lagging indicators measure outcomes that have already happened. Revenue, churn, and annual recurring revenue are lagging indicators. They tell you how the business performed, but they are slow to change and hard to act on in real time.

Leading indicators are early signals that predict future outcomes. Feature adoption, session frequency, and activation rate are often leading indicators. They change faster and give teams something actionable to influence before it is too late.

Effective product teams track both. Lagging indicators confirm whether the strategy is working at a business level; leading indicators give the team something to optimize week to week.

Frameworks for choosing metrics

North Star metric

The North Star framework organizes a product team around a single metric that represents the core value the product delivers to users. For a messaging app, it might be messages sent per day. For a project management tool, it might be tasks completed per active user.

The North Star is not a business metric like revenue — it is a user-value metric that the team can directly influence. The assumption is that consistently delivering user value will drive business outcomes over time.

HEART framework

Developed by Google, the HEART framework provides a structured way to think about user experience metrics across five dimensions: Happiness, Engagement, Adoption, Retention, and Task success. Each dimension can be measured with specific signals and metrics.

HEART is useful for teams that need to evaluate a product experience holistically rather than focusing on a single number. It surfaces trade-offs — a change that improves task success might reduce engagement, for example — that a single-metric approach would miss.

Pirate metrics (AARRR)

The AARRR framework — Acquisition, Activation, Retention, Referral, and Revenue — maps the customer journey from first discovery to ongoing loyalty. Originally coined for startups, it remains a practical way to diagnose where in the funnel a product is losing users.

Each stage has its own set of relevant metrics, and the framework helps teams identify which stage needs the most attention rather than optimizing for the wrong part of the funnel.

Common product metrics by category

Activation metrics

Activation metrics measure whether new users reach the moment where they first experience the product's core value. Common examples include time-to-first-key-action, onboarding completion rate, and day-one feature adoption.

Activation is often the highest-leverage metric for growth-stage products because improvements here compound — a better-activated user is far more likely to retain.

Engagement metrics

Engagement metrics measure how actively users are using the product over time. Daily active users (DAU), weekly active users (WAU), session length, and feature adoption rate all fall into this category.

The right engagement metric depends on the expected usage pattern. A daily productivity tool should optimize for DAU; a tax software product might measure annual active users and depth of feature use during tax season.

Retention metrics

Retention metrics measure whether users continue to use the product over time. Day-7 retention, day-30 retention, and monthly churn rate are common examples.

Retention is often called the most important product metric because it is a direct measure of whether the product is delivering ongoing value. Acquisition without retention is expensive and unsustainable.

Revenue metrics

Revenue metrics connect product performance to business outcomes. Monthly recurring revenue (MRR), average revenue per user (ARPU), and expansion revenue all fall into this category.

For product teams, revenue metrics matter most when they can be directly influenced by product decisions — pricing changes, upsell flows, or feature-gating strategies.

How to avoid vanity metrics

Vanity metrics are numbers that grow reliably but do not indicate that anything meaningful is happening. Total registered users is a classic example: it never goes down, it sounds impressive in a board meeting, and it tells you almost nothing about whether users are getting value.

The test for a vanity metric is simple: could this number go up while the product is actually getting worse? If yes, it is probably a vanity metric.

To avoid them, focus on metrics that can be acted on. Ask: if this number changes, what would we do differently? If the answer is "nothing," the metric is not worth tracking closely.

Rate metrics — retention rate, activation rate, conversion rate — are usually more meaningful than absolute counts because they normalize for changes in the size of the user base. A product with 10,000 highly retained users is healthier than one with 100,000 users who churn immediately.

Finally, be suspicious of metrics that are easy to game. If the team can hit a number without actually improving the product, it is the wrong number to optimize.