KPIs for Product Managers

These are the KPIs a product manager tracks for adoption, engagement and retention. They show whether people reach value in the product and keep coming back.

The KPIs to track

Where the data usually lives

A product analytics tool or event database, the application database, support tickets and customer feedback.

Measurement mistakes to avoid

  • Activation should be a behaviour that predicts retention, not just sign-up.
  • Retention should be measured by sign-up cohort, not across all users.
  • Event tracking changes silently when the product changes; check that events still fire.

Questions to ask your data

You can type these as plain questions. SchemaChat turns each one into SQL against your connected database or uploaded file, runs it, and shows the SQL and the figures it used so you can check the answer before you share it. Check that the result matches how your business defines each KPI.

  • What share of new sign-ups reached the activation event within a week?
  • Which features are used by the fewest active users?
  • How does day 30 retention compare across sign-up months?
  • Where do users drop out of onboarding?

Frequently asked questions

What are the most important KPIs for product managers?
Activation Rate, Time to Value, Onboarding Completion Rate, Feature Adoption Rate, Daily Active Users (DAU), Day-30 Retention, DAU/MAU Stickiness, Crash Rate.
Where does the data for these KPIs usually come from?
A product analytics tool or event database, the application database, support tickets and customer feedback.
What commonly goes wrong when measuring them?
Activation should be a behaviour that predicts retention, not just sign-up.