How to Define Your North Star Metric (With Examples for SaaS, Marketplace, and Consumer)
The north star metric concept is widely discussed and frequently misapplied. Most companies either pick a metric that's too easy to move (like 'visits' or 'signups'), too hard to measure, or so focused on revenue that it becomes indistinguishable from a financial KPI. A well-chosen north star metric captures the value your product delivers to users — and predicts long-term revenue as a consequence.
🧮 Free tool: Analytics Maturity Assessment — no signup required
Open tool →What makes a good north star metric
A north star metric should satisfy three criteria. First, it should measure value delivered to the customer — not just activity. 'Messages sent' isn't necessarily a north star; 'messages that received a reply within 24 hours' is closer, because it captures whether the communication is actually working. Second, it should predict long-term revenue without being a direct revenue metric. Revenue is an outcome of value delivery; if you optimize directly for revenue, you're optimizing for extraction rather than value — and users notice. Third, it should be movable by the product team. 'Number of enterprise contracts signed' isn't a product metric; it's a sales metric. The product team should be able to run experiments that visibly move the north star.
North star metric examples by business model
Different business models have different north stars. For SaaS productivity tools, common choices are weekly active teams (not just users — teams, because team adoption predicts enterprise retention), or 'projects completed this week' for project management tools. For consumer social products, it's typically a quality engagement metric: 'users who both posted and consumed content in the last 7 days' rather than raw DAU. For marketplaces, the north star is often 'successful transactions per week' — note that this is a double-sided metric, capturing value for both buyers and sellers simultaneously. For e-commerce, it might be 'repeat purchasers as a percentage of 90-day active buyers.' The pattern: all of these measure value exchange or task completion, not just presence.
The relationship between north star and input metrics
The north star metric is not the only metric that matters — it's the single metric the whole company aligns around. Supporting it is a set of input metrics that the team directly works to move: activation rate, feature adoption, engagement frequency, and so on. These input metrics are the levers; the north star is the outcome. A useful structure: the north star is reviewed weekly as a health check on the business. Input metrics are reviewed daily by product and growth teams and are the primary subject of experimentation. If your north star is 'weekly active teams,' your input metrics might be 'activation rate for team use cases,' 'team invitation conversion rate,' and 'multi-user session frequency in week 1.'
Common mistakes when picking a north star metric
The most common mistake is picking a vanity metric — something that looks impressive but doesn't predict actual business health. 'Total registered users' is the canonical example: it only goes up (you never delete users), it's easy to inflate with low-quality acquisition, and a company can have millions of registered users while its retention curves head toward zero. Another common mistake is picking a metric that's manipulable without delivering real value — 'time in app' can be inflated by adding friction, 'pages visited' can be inflated by breaking single pages into multiple. A good test: can someone game your north star metric in a way that looks good but makes the product worse for users? If yes, it's the wrong metric.
How to get organizational alignment on the north star
The hardest part of the north star exercise isn't choosing the metric — it's getting leadership and cross-functional teams to actually use it. The most common failure mode: the north star gets announced, then promptly ignored in favor of the metrics each team was already using (revenue for finance, sign-ups for marketing, tickets closed for support). To avoid this: the north star has to appear in the weekly leadership review, it has to be the reference point for roadmap prioritization ('how does this feature move our north star?'), and it has to be the primary metric in your growth team's sprint reviews. The organizational muscle of using a single shared metric is more valuable than the specific metric chosen.
Need expert help with growth analytics?
Adasight works with scaling D2C and SaaS companies to build the analytics foundations and experimentation programs that drive measurable growth.
Talk to Adasight →Frequently asked questions
What is a north star metric?
A north star metric is the single metric that best captures the value your product delivers to customers and predicts the long-term health of your business. It's not a revenue metric — it's a product value metric that, when it grows, revenue follows. Well-known examples include Airbnb's 'nights booked,' Facebook's 'daily active users who post or engage,' and Slack's 'messages sent within an organization per day.'
What is the difference between a north star metric and an OKR?
An OKR (Objective and Key Result) is a goal-setting framework that defines what you're trying to achieve in a given period and how you'll measure progress. The north star metric is a persistent, directional single metric that stays constant over years. OKRs may reference the north star as an objective, and key results are the input metrics you'll move to get there. The north star is a compass; OKRs are the quarterly navigation decisions.
How often should you change your north star metric?
Rarely — if you're changing it more than once every 2-3 years, you likely haven't found the right one yet, or your business model is in active transformation. The north star should be stable enough that the whole organization can build intuition around it. That said, north stars do evolve: Facebook's shifted from DAU to more quality-adjusted engagement metrics as the business matured. The trigger for re-evaluation is when the metric no longer captures what most creates value for your users.