Product Metrics That Matter: North Star, Activation, Retention and More

Which product metrics to track and why — North Star metric, input metrics, AARRR funnel, activation, retention cohorts, engagement, revenue metrics, guardrails and avoiding vanity metrics.

By Danyal Ahmed - Data Scientist · · 5 min read

Product teams drown in dashboards but starve for insight. Page views, signups and "total users" go up and to the right while the business quietly struggles. Good product metrics do three things: they reflect real value delivered to customers, they connect to business results, and they're actionable, so teams can influence them through the work they do.

Key takeaways

  • Define a North Star metric that captures the core value customers get, plus the input metrics that drive it.
  • Activation (reaching the "aha" moment) and retention (coming back) are the most important early indicators of product health.
  • Analyze retention with cohorts, not aggregate totals.
  • Pair every goal metric with guardrail metrics so improvements don't come at hidden costs.
  • Avoid vanity metrics: numbers that look good but don't inform decisions.

The North Star framework

A North Star metric is the single metric that best captures the value your product delivers to customers, which in turn leads to durable business results.

Good North Star metrics:

  • Reflect customer value, not just company value.
  • Are leading indicators of revenue and retention.
  • Are measurable and understandable across the company.
Product type Possible North Star
Team collaboration tool Weekly active teams collaborating (e.g., 3+ members active)
Marketplace Successful transactions per week
Streaming service Hours of content consumed by subscribers
B2B analytics SaaS Accounts with weekly insights viewed by decision-makers
AI writing assistant Documents where AI suggestions were accepted

A North Star is supported by input metrics that teams can directly influence:

textNorth Star: Weekly active collaborating teams
  ├─ New teams activated per week       (acquisition + onboarding)
  ├─ % of teams inviting ≥ 3 members     (breadth)
  ├─ Collaborative actions per team      (depth)
  └─ Week-over-week team retention       (frequency / habit)

Individual teams own input metrics; the North Star aligns everyone.

The AARRR funnel ("pirate metrics")

A useful lens for the customer lifecycle:

Stage Question Example metrics
Acquisition Do people find us? Visitors by channel, signup conversion, CAC
Activation Do they experience the core value? % reaching the aha moment, time to value
Retention Do they come back? Cohort retention (D1/D7/D30, W1/W4/W12)
Revenue Do they pay? Conversion to paid, ARPU, MRR, expansion
Referral Do they tell others? Invites sent/accepted, viral coefficient, NPS

Early-stage products should obsess over activation and retention. Pouring acquisition into a leaky bucket just burns money.

Activation: the "aha" moment

Activation measures whether new users experience the core value. Define it as a specific behavior correlated with long-term retention:

  • "Created a project and invited a teammate within 7 days."
  • "Connected a data source and viewed a dashboard."
  • "Completed a first successful automation run."

Find it by comparing retained vs churned users' early behaviors (correlation isn't causation, so validate with experiments). Then design onboarding to get users there faster. Time to value is a key companion metric.

Retention: the truth-teller

Retention shows whether the product delivers ongoing value. Measure it with cohort analysis: group users by signup week or month and track what fraction remain active over time.

textSignup cohort   Week 1   Week 4   Week 8   Week 12
Jan W1          62%      41%      35%      33%
Jan W2          60%      43%      37%      36%
Feb W1          68%      49%      44%      43%   ← improved onboarding shipped

What to look for:

  • Flattening curves: a curve that levels off means a core of users finds lasting value. A curve that decays toward zero means you haven't found product-market fit for that segment (product-market fit).
  • Cohort improvements after product changes.
  • Segment differences: retention by persona, company size or acquisition channel often reveals your best-fit customers.

Define "active" meaningfully (performed the core action, not just "logged in"), at a frequency that matches natural usage: daily for messaging, weekly for team tools, monthly for invoicing.

Engagement metrics

  • DAU/WAU/MAU and the DAU/MAU ratio (stickiness), when daily use is natural.
  • Feature adoption: the percentage of active users using a feature, and whether adopters retain better.
  • Depth: actions per session, or key actions per week.
  • Breadth: seats active per account (critical for B2B expansion).

Revenue and business metrics

  • MRR/ARR, split into new, expansion, contraction and churned.
  • Net revenue retention (NRR): revenue retained from existing customers including expansion. Above 100% means existing customers grow.
  • Gross revenue churn and logo churn.
  • ARPU / ARPA (average revenue per user/account).
  • CAC, payback period and LTV:CAC ratio.
  • For AI products, gross margin per user, since inference costs vary with usage (LLM cost optimization).

Guardrail metrics

Every optimization can backfire. Pair goal metrics with guardrails:

Goal metric Guardrails
Increase trial signups Activation rate, spam/fake accounts
Increase notifications clicked Unsubscribe rate, uninstall rate
Increase AI feature usage Accuracy/complaint rate, cost per user
Reduce support tickets CSAT, recontact rate, churn
Faster checkout Refund rate, fraud rate

Guardrails are essential in experiments (A/B testing done right).

Vanity metrics vs actionable metrics

Vanity metrics look impressive but don't guide decisions: total registered users (ever), page views, app downloads, social followers.

Actionable metrics reflect behavior and respond to your changes: activation rate, cohort retention, conversion rates by step, revenue per account.

Test: If this number changed tomorrow, would we do anything differently? If not, it's probably vanity.

Qualitative metrics

Numbers need context:

  • NPS or CSAT, with the open-text comments (the comments matter more than the score).
  • Customer effort score for support and onboarding flows.
  • Interview themes tracked over time (product discovery).

Making metrics useful

  1. Instrument deliberately: define a clean event taxonomy (project_created, member_invited) with consistent properties; document it.
  2. Trust the data: validate tracking, and reconcile with backend data (data quality guide).
  3. Build a small set of core dashboards (the North Star plus inputs, funnel, retention cohorts), reviewed on a regular cadence.
  4. Set targets tied to goals (for example, as OKR key results) (roadmap planning).
  5. Segment everything: averages hide the story.

FAQ

What's the difference between a North Star metric and a KPI?

A North Star is the single metric that best represents the core customer value your product delivers and aligns the whole organization. KPIs are the broader set of key indicators, including revenue, costs and operational metrics, that leadership monitors.

What is a good retention rate?

It varies widely by product type, price point and customer segment. The more useful question is whether your retention curves flatten (a stable core of users) and whether they improve cohort over cohort.

How do I find my product's activation metric?

Compare early behaviors of users who retained against those who churned, identify actions strongly associated with retention, choose a specific and time-bound behavior, and validate that helping more users do it actually improves retention.

How many metrics should a product team track?

A few that matter: one North Star, three to five input metrics the team influences, and relevant guardrails. Keep broader dashboards available for diagnosis, but focus attention on a small set.