What Are Product Metrics? Key Metrics, Frameworks, and Examples

Product metrics are measurable figures that give teams insights into how well a product is performing, what users do, and the effect on the business; they cover acquisition, activation, engagement, retention, conversion, satisfaction, and revenue. In this guide, we will look at the key product metrics, the AARRR framework, North Star and guardrail metrics, some real-life examples, and the way in whichproduct owners can use them to measure and improve product success.

Key Highlights of product metrics

• Product metrics are measures of product health and of user behaviour, for example, acquisition, activation, engagement, retention, satisfaction, conversion, and monetization.

• The AARRR framework classifies the metrics as pertaining to Acquisition, Activation, Retention, Revenue, and Referral.

• The top product teams make use of leading indicators such as activation and feature adoption together with lagging indicators such as revenue and churn.

Introduction

Modern product teams have access to more behavioural data than ever. Every click, search, purchase, session, feature interaction, and cancellation can potentially become a data point. The challenge is no longer simply collecting data. It is knowing which data matters.

A team could track hundreds of events and still struggle to answer basic questions: Are customers reaching the product's "aha" moment? Which features create repeat usage? Why are users abandoning onboarding? Is retention bettered by a recent release? New customers are often more valuable than the old ones.

This is why product metrics should be viewed as decision-making tools, not just as numbers on a dashboard.

Recent product analytics research illustrates how difficult retention can be. Amplitude's analysis of more than 10,600 digital products found that the median digital product saw 98% of new users become inactive within two weeks (Amplitude, the 7% retention rule). Its benchmark analysis also found that the top 10% of products retained 26% of users at month one compared with 6.5% for the median product. Amplitude

The lesson is straightforward: getting users is only the beginning. Product teams need to understand what happens after acquisition.

What Are Product Metrics?

Product metrics are measurable metrics that assess how users engage with a product and if the product provides the anticipated value. They can capture user behaviour, product adoption, customer satisfaction, business results, or progress through a specific stage of the customer journey.

Some of the examples of product metrics are as follows:

• Activation rate

• Daily Active Users (DAU)

• Monthly Active Users (MAU)

• DAU/MAU ratio

• Feature adoption

• Retention rate

• Churn rate

• Conversion rate

• NPS

• CSAT

• Monthly Recurring Revenue (MRR)

• Average Revenue Per User (ARPU)

Product metrics are most useful when they answer a specific product question.

For example, instead of asking, "How many people use our app?" a product team might ask, "What percentage of users who complete onboarding return and perform the core action within seven days?"

The second question produces a metric that is much easier to act upon.

Product Metrics Definition

Here is a practical product metrics definition:

Product metrics are measurable indicators that help teams understand user behaviour, customer value, and progress towards desired outcomes. These product performance metrics can reveal whether a product is meeting user needs and business objectives. They may be given in the form of counts, percentages, ratios, rates, averages, or monetary values.

For example:

Activation rate = Activated users ÷ New users × 100

If 2,000 people sign up for a product and 800 complete the defined activation event:

Activation rate = 800 ÷ 2,000 × 100 = 40%

The calculation is simple, but it's difficult to define what exactly "activated" means.

In the case of a SaaS product designed for project management, activation would involve setting up a project and inviting at least one teammate; for a banking app, it would consist of carrying out the first transaction; and for a collaboration tool, it would be creating a workspace and sending a message. Hence, the metric should be based on realized product value rather than just on activity.

Product Metrics vs Vanity Metrics

Not every number deserves a place among the product success metrics a team tracks. For instance, vanity metrics can seem impressive but offer minimal guidance about what should happen next. 

For example:

• Total downloads

• Total registered users

• Number of website visits

• Total page views

• Social media followers

Suppose an app has 500,000 registered users. That sounds impressive. But if only 20,000 users were active during the month and only 5,000 completed the core action, the registration figure tells an incomplete story.

A useful metric should ideally be:

1. Relevant to the product objective.

2. Actionable by the team.

3. Consistently measurable.

4. Connected to customer or business value.

5. Useful for making comparisons over time or between segments.

That’s not to say vanity metrics are totally of no use when it comes to sign-ups, downloads, and traffic. The problem is when you use them as proof of product success without looking at what happens afterwards.

Why Product Metrics Matter

Product metrics put assumptions into the open. Let’s say a team believes the more streamlined onboarding flow will drive better activation. Instead of arguing whether the new design “feels better," the team can use an A/B testing approach:

Current onboarding: Version B

Version B: smoother onboarding

The main metric is activation rate.

Guardrail metric: early churn/support calls

If Version B increases activation and does not have a negative impact in other areas, then the team has evidence that the change is working.

Product metrics also help teams discover problems earlier and feedproduct discovery: reduced activation can surface onboarding friction before it shows up as churn or lower revenue.

This is why product analytics are becoming increasingly important. It takes behavioural data and ties it to questions about conversion, engagement, retention, and customer value, instead of simply reporting traffic or page views. Amplitude

The AARRR Product Metrics Framework

The AARRR product metrics framework organizes the customer journey into five stages:

Acquisition → Activation → Retention → Revenue → Referral

The framework is useful because it drives teams to look beyond acquisition and assess the complete product lifecycle.

Acquisition

Acquisition measures the ways users discover and enter the product. Common acquisition metrics include:

• Website visitors

• App installs

• Sign-ups

• Trial starts

• Cost per acquisition

• Acquisition by channel
   

For example, a SaaS company might generate 10,000 visitors from paid advertising and 1,000 trial sign-ups.

Its visitor-to-trial conversion rate is:

1,000 ÷ 10,000 × 100 = 10%

However, acquisition should not be judged in isolation. If paid traffic produces many trials but very few retained customers, a cheaper acquisition channel may actually be more valuable.

Activation

The activation process determines if users perceive the initial value of the product.

This is usually one of the most important stages since the fact that someone has registered doesn't mean that they understand the product.

For example:

First collaboration: New user → Sign up → Create project → Invite colleague

Since the act of setting up a project and inviting a teammate are highly predictive of continued usage, these actions might be the activation event.

A recent benchmark study carried out by Amplitude has shown that early activation is closely linked to longer-term retention. This demonstrates the importance of keeping a record of the activities users carry out immediately after they have been acquired.

Retention

Retention refers to whether or not users continue to use the product after their first experience with it. The following is a simple way of calculating retention.

Retention rate = Users retained at end of period / Users in starting cohort x 100

Say, for example, 1,000 users sign up in January, and 300 of them are still active in February:

Monthly retention = 300/1,000 * 100 = 30%

It is important to focus on retention, particularly in the case of subscription products since ongoing revenue relies on customers still believing they are getting value.

Revenue

Revenue metrics tie monetization to product usage. The examples include:

• “Monthly recurring revenue”

• ARRR

• revenue per user

• Customer Lifetime Value

• Income from expansion

• Revenue Retention Net

• Conversion rate

For example, if a SaaS product has 1,000 customers paying an average of $50/month:

MRR = 1,000 x $50 = $50,000

Revenue is important, but product teams should remember that revenue is often a lagging indicator. Activation, adoption, or retention changes can precede the visibility of the financial impact.

Referral

Referral is the metric for how well existing customers help to bring new customers to the product.

Here are some of the examples:

• Referral rate

• Invitations mailed

• Conversion rate from referral

• % of new users referred

• Viral Coefficients

Key Product Metrics by Category

The following product metrics examples by category provide a practical starting point for product teams.

Engagement and Stickiness (DAU, MAU, DAU/MAU)

DAU represents Daily Active Users, while MAU represents Monthly Active Users.

The DAU/MAU ratio is commonly used as a measure of product stickiness:

DAU/MAU = DAU ÷ MAU × 100

Suppose a product has:

• DAU = 20,000

• MAU = 100,000

Then:

DAU/MAU = 20%

A higher ratio generally indicates that users return more frequently, although there is no universally "good" DAU/MAU benchmark. Usage frequency depends heavily on the product category. For example, a messaging application may reasonably expect frequent daily use, while accounting software may provide substantial value through weekly or monthly use.

Other product engagement metrics include

• Sessions per user

• Session frequency

• Feature adoption

• Time to value

• Core actions per user

• Frequency of key workflows

Retention and Churn

Product retention metrics show how effectively a product keeps users engaged over time, while churn metrics reveal how many customers stop using the product. 

A simple customer churn formula is:

Customer churn rate = Customers lost during period ÷ Customers at start of period × 100

If a SaaS company begins the month with 2,000 customers and loses 100:

Churn rate = 100 ÷ 2,000 × 100 = 5%

Retention and churn should also be segmented.

For example, a product might have:

• 8% churn among small customers

• 3% churn among mid-market customers

• 1% churn among enterprise customers

That difference can lead to very different product decisions.

Teams should also investigate why customers churn. A rising churn rate may result from poor onboarding, missing features, pricing changes, performance problems, or a mismatch between the product and customer needs.

Conversion and Funnel Metrics

Conversion metrics show how users move between important stages. A SaaS funnel might look like:

Website visitor → Sign-up → Activated user → Trial → Paid customer

If 10,000 visitors generate 1,000 sign-ups and 200 paid customers:

• Visitor-to-sign-up conversion = 10%

• Visitor-to-paid conversion = 2%

• Sign-up-to-paid conversion = 20%
   

Looking at the complete funnel is more informative than tracking only the final conversion rate. A sharp drop between sign-up and activation, for example, points toward a different problem than a drop between trial and paid subscription.

Satisfaction (NPS, CSAT)

Behavioural metrics like NPS, CSAT tell you what customers do. Satisfaction metrics help explain how they feel about the experience.

NPS (Net Promoter Score) asks customers how likely they are to recommend a company or product on a 0-to-10 scale.

• 9–10 = Promoters

• 7–8 = Passives

• 0–6 = Detractors

The formula is:

NPS = % Promoters − % Detractors

This means NPS can range from -100 to +100. Bain & Company, which developed the Net Promoter System with Fred Reichheld and Satmetrix,defines the score using this promoter-minus-detractor calculation (Bain, Measuring Your Net Promoter Score).

CSAT (Customer Satisfaction Score) usually asks customers to rate their satisfaction after an interaction or experience.

For example, a product team could ask:

"How satisfied were you with the new reporting experience?"

NPS and CSAT are useful, but they should not replace behavioural data. A customer can report satisfaction while rarely using a feature, just as a frequent user may encounter serious frustrations.

North Star, Guardrail, and Input Metrics

A strong measurement system usually contains different types of metrics rather than one number.

The North Star Metric represents the core value a product delivers to customers and provides a shared direction for the product organization. TheNorth Star Framework pairs this metric with input metrics teams can influence directly.

For example, consider an online learning platform.

North Star Metric:
 Weekly lessons successfully completed

Input metrics:

CSAT (Customer Satisfaction Score) usually asks customers to rate their satisfaction after an interaction or experience.

• New learners completing onboarding

• Lessons started per user

• Lesson completion rate

• Weekly active learners

• Course recommendation engagement

Guardrail metrics:

• Customer complaints

• Refund rate

• Support tickets

• Content error rate
   

The North Star should not become a target that teams optimize at any cost. Guardrails help prevent a local improvement from damaging another part of the customer experience.

For example, a team could increase "lessons completed" by making lessons shorter. The metric might rise while actual learning quality falls. A learning-quality or satisfaction guardrail could expose that problem. Check here to know more about identifying and applying a North Star Metric. 

How to Choose the Right Product Metrics

There is no universal list of product metrics that every organization should track. The right combination depends on:

• Product type

• Business model

• Customer journey

• Product maturity

• Current strategic goal

• Available data

• Decisions the team needs to make

A newly launched product, for example, may be heavily focused on activation and retention. A more mature SaaS platform might be focused on growth revenue, adoption, churn, and customer lifetime value.

Tie Metrics to Outcomes and the Product Goal

You should start with the outcome rather than the metric. Suppose the product goal is:

Increase paid customer retention over the next two quarters.

Relevant metrics might include:

• Monthly customer retention

• Churn rate

• Product adoption

• Feature adoption among retained customers

• Support issue rate

• NPS or CSAT

• Net Revenue Retention

Total traffic to your website is a totally unrelated metric, and while it’s nice to have as context, it shouldn’t be the main success metric.

Metrics can also be segmented by customer type, geography, acquisition channel, plan, device, or cohort through product analytics. This can expose trends obscured by numbers. Platforms for this are built to analyze user behaviour at the event and journey level. 

Product Metrics Examples

Here are practical product metrics examples across different product types.

For product metrics for SaaS, a useful measurement model could include:

Acquisition: trial sign-ups
 Activation: users completing the core setup
 Engagement: weekly active accounts
 Retention: logo or customer retention
 Monetization: MRR, ARPU, expansion revenue
 Advocacy: referral rate or NPS

The key is to connect these numbers. For example, if users who invite three teammates during their first week have significantly higher retention, invitations become a potentially valuable input metric.

A product metrics dashboard can then show the relationship between acquisition, activation, engagement, retention, and revenue rather than displaying disconnected numbers.

Product Metrics vs KPIs vs OKRs

Product metrics, KPIs, and OKRs are related but not interchangeable.

Product metrics measure specific aspects of product behaviour or performance.

KPIs (Key Performance Indicators) are selected measures used to monitor important business or organizational performance.

OKRs (Objectives and Key Results) combine a qualitative objective with measurable results used to define and track progress.

For example:

Objective:
 Improve the onboarding experience for new customers.

Key Result:
 Increase activation from 35% to 50%.

Product metrics:

• Onboarding completion rate

• Time to first value

• Activation rate

• Drop-off at each onboarding step

• Seven-day retention

Here, activation rate may be a product metric and a key result at the same time.

This is why discussions aboutOKR vs KPI should focus on purpose rather than treating the terms as competing measurement systems. An OKR describes what the organization wants to achieve and how progress will be judged; a KPI is typically an ongoing indicator of performance. 

Product Metrics in Agile and SAFe

Product metrics fit naturally intoAgile product developmentbecause Agile emphasizes feedback, learning, incremental delivery, and customer value. Instead of asking only:

"Did we complete the stories?"

A product team can ask:

"Did this increment improve the outcome we were trying to change?"

In SAFe, product owners and product managers work within a broader value-delivery system. Metrics link product strategy with execution by indicating whether the increments that have been delivered result in important customer and business outcomes. Meanwhile,Teams aiming to take on product ownership roles might considerSAFe POPM certification training.

Measuring Value Delivered Each Increment

Imagine a team releases a new self-service reporting feature. TraditionalAgile delivery metrics might show:

• 12 stories completed

• 30 story points delivered

• Release completed on schedule

An unrelated metric such as total website traffic may provide useful context, but it should not become the primary measure of success.

Product Metrics Examples

Product Metrics vs KPIs vs OKRs

OKRs (Objectives and Key Results) combine a qualitative objective with measurable results used to define and track progress.

For example:

Objective:
 Improve the onboarding experience for new customers.

Key Result:
 Increase activation from 35% to 50%.

Product metrics:

• Onboarding completion rate

• Time to first value

• Activation rate

• Drop-off at each onboarding step

• Seven-day retention

Here, activation rate may be a product metric and a key result at the same time. These numbers describe delivery, but they do not prove value. A product-oriented measurement approach could add:

• 45% feature adoption within 30 days

• 20% reduction in support requests about reporting

• 15% increase in weekly active accounts using reports

• 8% improvement in customer satisfaction among reporting users

Now the team can evaluate the increment based on its impact. This distinction matters because output is not the same as outcome. A team can deliver every planned feature and still fail to solve the customer's problem.

Product Owners can use metrics toprioritize the product backlog, validate assumptions, evaluate experiments, and communicate outcomes. These activities are closely connected to broaderSAFe POPM responsibilitiesand cover alignment of product decisions with business goals and providing customer value. 

Common Product Metrics Mistakes

Even experienced teams can misuse product metrics. Some of the most common mistakes include

1. Tracking too many metrics

A dashboard containing 80 metrics can create the illusion of analytical maturity while making prioritization harder. Start with a small set of metrics directly connected to the current product goal.

2. Optimizing vanity metrics

More downloads or registrations do not automatically mean a healthier product. Always ask what happens after the user takes the measured action.

3. Ignoring retention

Acquisition can hide a weak product experience. If 10,000 people sign up but 9,500 disappear after the first week, increasing acquisition may simply increase the number of users who leave.

4. Using averages without segmentation

An average retention rate can conceal major differences. For example, overall retention could be 40%, while:

• Enterprise customers retain at 70%

• SMB customers retain at 25%

Those segments may need completely different strategies.

5. Changing definitions

If "active user" means logging in one month and completing a core action the next month, trends become difficult to interpret. Metric definitions should be documented and consistently applied.

6. Confusing correlation with causation

Suppose highly retained customers use Feature X frequently. That does not automatically mean Feature X causes retention. The relationship could be reversed: highly engaged customers may simply use more features. Controlled experiments, cohort analysis, and otherdata analysis methods can help investigate these relationships.

7. Treating the North Star as the only metric

A North Star provides direction, but it should be supported by input and guardrail metrics. One number rarely explains the whole product.

8. Measuring after the decision

Metrics are most useful when they influence decisions before and after product changes. Teams should define success criteria before launching major experiments or features whenever possible.

Conclusion

Product metrics provide the evidence product teams need to understand whether a product is creating real value. The most effective approach is not to track every possible number. It is to build a measurement system that connects customer behaviour, product value, and business outcomes.

AARRR is a useful lens on the lifecycle: acquisition, activation, retention, revenue, and referral. Category-specific metrics like DAU/MAU, churn, conversion, NPS, and CSAT give a greater level of insight into specific parts of the customer journey. Then, a North Star Metric can provide the organization with a common definition of product value, and input and guardrail metrics can help teams to drive and protect that outcome.

Most importantly, action should be driven by metrics. If the activation is low, check the onboarding process. If retention is dropping, analyze the behaviours of retained and churned users. If feature adoption is poor, find out if the feature solves a meaningful problem. If revenue is growing but satisfaction is declining, investigate whether short-term gains are creating long-term risks.

They allow teams to discover why something happened and what actions they should take. In the case of teams that want to strengthen their product management and analytics capabilities, their objective should be simple too: to measure less, learn more, and always connect product decisions to customer value.