Vanity Metrics: The Data That Feels Good and Lies

A founder reviews the weekly dashboard: traffic up 45%, signups up 30%, app sessions up 22%, feature events up 60%. It looks like growth. MRR is flat, churned MRR is rising, ARPU is down, NRR is below 100%, runway is slightly shorter than last week. The dashboard was lying — not because the numbers were fabricated, but because the numbers that moved most visibly were exactly the ones least connected to business health.

That is the vanity metrics trap. Numbers that create the feeling of momentum without the reality of it. For most SaaS founders, vanity metrics do not just distract — they delay the right decision. They make it easier to postpone fixing onboarding, ignore churn, avoid pricing work, and keep shipping “growth” while the business quietly stalls.

What are vanity metrics?

Vanity metrics are numbers that look impressive but do not change decisions. A more precise definition: a vanity metric can move significantly without telling you whether the business is getting healthier or weaker.

The phrase was popularised in lean startup circles but the pattern predates the term. Any number that is easy to increase, satisfying to screenshot, and hard to connect to revenue or retention qualifies. The metric itself is rarely the problem — the problem is how much weight it gets on the founder’s dashboard relative to what it can actually explain. For the full list of SaaS metrics that actually belong on a founder dashboard, that guide covers what each one is for.

Vanity metrics vs actionable metrics is the distinction that matters:

Metric	Usually vanity or actionable?	Why
Total site traffic	Usually vanity	Can grow while conversion and revenue stay flat
Total signups	Often vanity without activation data	Signups alone do not prove value delivery
MRR	Actionable	Directly measures recurring revenue health
Revenue churn rate	Actionable	Measures business leakage in dollars, not counts
Feature click events	Usually vanity without outcome context	Activity is not value
CAC payback period	Actionable	Tells you if acquisition economics are sustainable
App sessions	Usually vanity	Usage without retention or revenue context is decorative
Churned MRR	Actionable	Surfaces how much recurring revenue is leaving and why

The table is not absolute — context always matters. Traffic from a single high-intent source tied to a specific trial conversion is actionable data. Total traffic from six mixed sources with no conversion tracking is largely vanity. The metric does not decide; the definition does.

Why founders keep tracking vanity metrics

The addiction is not irrational. It has three real causes.

Vanity metrics are easier to improve than real business metrics. Increasing traffic, signups, or raw usage events is mechanically simpler than improving retention, expanding revenue per account, or tightening CAC payback. Founders who are under pressure to show movement naturally gravitate toward the numbers that move fastest.

They create an illusion of progress. A dashboard full of upward arrows feels like momentum even when the revenue engine is stalling. A founder can spend weeks celebrating charts that make the company feel healthy while the actual health metrics quietly deteriorate. This is the most dangerous form of the trap because it is entirely self-reinforcing — the good feeling reduces the urgency to investigate harder.

They are available before the important metrics are clean. Traffic and signups are trivial to instrument. Clean MRR, NRR, ARPU, and churn rates require consistent recurring-revenue definitions, proper Stripe data handling, and discipline around what counts and what does not. Founders over-weight what they can measure immediately, then never go back to build the harder metrics.

A fourth factor: vanity metrics are socially useful. They are what you post on X after a launch, what goes in the investor update to show momentum, what gets shared in the indie hacker community. There is nothing wrong with that — the problem starts when the social number also runs the operating dashboard.

Track the metrics that matter, not the ones that feel good. See your real numbers from Stripe →

The most common vanity metrics in SaaS

Total traffic is not a business metric on its own. It becomes meaningful when connected to trial activation rate, paid conversion rate, or MRR generated by channel. Traffic that rises while all three of those metrics stay flat is a campaign result, not a business result.

Total signups matters far less than the activation rate inside that signup cohort. The sequence is: traffic → signup → activation → paid → retained → expanded. If signups increase and nothing downstream improves, you have bought more noise. The useful number is activated signups in the first 7 or 30 days — the version that predicts whether new users will eventually generate recurring revenue.

Total users and total accounts are among the most frequently inflated numbers in SaaS dashboards. A bloated total-account count can hide a product with almost no retained, paying users underneath. The right questions: how many are active? how many are paying? what is the retained cohort at 30, 60, 90 days? how many have ever expanded?

Feature usage events — messages sent, API calls made, workflows triggered, sessions started — are where AI-assisted and product-led products are especially vulnerable. Activity volumes can grow while retained revenue shrinks if the usage is concentrated in non-paying or low-value cohorts. Usage becomes useful data when tied to retained accounts, upgrade events, or activation milestones. a16z’s 16 SaaS Metrics draws the line clearly between activity metrics and the revenue-linked metrics that actually matter.

Social and launch metrics have a legitimate place in awareness tracking. They belong nowhere near a founder’s operating analytics dashboard alongside MRR, churn, and runway. If you want a clean list of metrics that actually deserve dashboard space, the SaaS metrics for founders guide covers exactly that.

The 20% rule: the fastest vanity metric filter

The most practical test for any metric is this:

If this number changed by 20% this week, what would I do differently?

Apply it to each metric currently on your dashboard.

MRR down 20% → investigate acquisition, churn, and pricing immediately. Real action follows. Revenue churn up 20% → review cancellation reasons and failed payments today. Runway down 20% → reduce burn and freeze experiments.

Now apply it to the usual vanity suspects: page views up 20%, total signups up 20%, feature events up 20%. The honest answer for most products: probably nothing would change in the immediate decisions. These numbers might influence investigation but not operating decisions in the same week.

That is the line. The 20% rule is crude. It works because it forces the founder to articulate the decision chain — if the metric does not sit at the start of a decision chain, it does not belong on the core dashboard.

Vanity metrics examples founders should watch for

“Traffic is up 60%.” Is activation up? Is trial-to-paid rate up? Is MRR from organic sources up? If not, the traffic spike is marketing data, not business data. File it in a secondary analytics view and do not let it displace churn from the main screen.

“We had 2,000 signups this month.” How many activated within 7 days? How many converted to paid within 30 days? How many retained at 60 days? Without those numbers, the 2,000 is noise dressed as growth. A product with 2,000 signups and 3% activation is in a much worse position than a product with 800 signups and 25% activation.

“Users sent 500,000 messages.” Common in AI and chat products. If those 500,000 messages are distributed across retained paying accounts who are generating expansion MRR, this is useful. If half of them are from free users who have never converted, the message count is masking a monetization problem.

“We crossed 10,000 accounts.” What is the active rate? What share are paying? What is average revenue per active account? A 10,000-account milestone with 8,000 dormant, non-paying accounts is not the same as 10,000 active accounts with healthy ARPU. The total count obscures which version is true.

“We had 100k API calls.” Impressive on the surface. Meaningless without context on: which accounts generated them, whether those accounts are paying, whether the pricing model is tied to API volume, and whether infra costs tracked with them. David Skok’s SaaS metrics framework is explicit that raw activity volume belongs in the diagnostic layer, not the core dashboard.

The vanity metrics meaning founders need: signal score

A crude scoring approach for metric selection:

Signal Score = actionability + revenue_link + retention_link + predictiveness − vanity_bias

Rate each dimension 1–5 and subtract vanity bias (how likely the metric is to flatter without informing).

Total signups scored:

actionability = 2 (downstream activation needed before action)
revenue_link = 2 (weak without paid conversion data)
retention_link = 1 (no direct link)
predictiveness = 2 (weak predictor of MRR)
vanity_bias = 5 (easy to inflate, great for screenshots)
Signal Score = 2

Churned MRR scored:

actionability = 5 (immediately actionable — review cancellations, run dunning)
revenue_link = 5 (direct dollar measurement)
retention_link = 5 (measures retention failure in revenue terms)
predictiveness = 4 (predicts NRR and LTV trajectory)
vanity_bias = 1 (impossible to inflate, hard to celebrate)
Signal Score = 18

This is how a metric’s score justifies its position on the founder dashboard.

How to save useful top-of-funnel metrics from becoming vanity

Not every top-of-funnel metric should be deleted — some should be redefined. Bessemer’s State of the Cloud report distinguishes “efficiency metrics” from vanity counts and consistently links the efficient SaaS companies to revenue-linked tracking rather than activity counts.

Better than total traffic: traffic-to-trial activation rate by source, traffic-to-paid conversion by source, MRR generated per acquisition channel. These connect the volume number to the revenue outcome and make it decision-grade.

Better than total signups: activated signups (completed key onboarding step within 7 days), paid signups in the period, retained signups at 30 days. Any of these is more informative than the raw count.

Better than total feature events: feature usage among retained paying accounts, feature usage among accounts that later expanded, feature usage in the 7 days before an upgrade event. These connect activity to the business outcome the activity is supposed to produce.

The founder dashboard ignore list

Unless tightly connected to a revenue or retention outcome, these metrics should stay out of the main founder dashboard:

Total page views, social impressions, raw engagement metrics, total accounts created (including dormant), total sessions, broad feature event counts, downloads, app opens, and any metric that was relevant during launch week and was never re-evaluated after.

This is not “never measure these.” It is “do not give them first-screen real estate at the expense of MRR, churned MRR, ARPU, NRR, and runway.”

The vanity filter system: five steps

Step 1: Label every metric. Tag each one: core, diagnostic, vanity, or optional context. This alone forces clarity on what the dashboard is actually for.

Step 2: Apply the 20% question. If it changes by 20%, does a decision change? If not, it is not core.

Step 3: Move weak metrics out of the founder view. Secondary analytics dashboards, weekly reports, or campaign-specific views are appropriate homes. They do not belong next to churned MRR and runway.

Step 4: Add thresholds to core metrics. A metric without a threshold stays passive. Churned MRR with a threshold triggers investigation. Raw traffic with no threshold just looks like a graph.

Step 5: Review and delete monthly. A dashboard should get cleaner over time, not heavier. Remove any metric that has not influenced a decision in 30 days.

For the dashboard implementation, see SaaS Dashboard in a Day: The 8 Metrics That Don’t Waste Time.

JSON model: a vanity-metric filter rule system

{
  "dashboard_metrics": [
    {
      "name": "mrr",
      "category": "core",
      "signal_score": 18,
      "action_if_changes_20_pct": "Investigate growth and churn drivers immediately",
      "keep_on_founder_dashboard": true
    },
    {
      "name": "churned_mrr",
      "category": "core",
      "signal_score": 18,
      "action_if_changes_20_pct": "Review cancellation reasons and failed payment cohort",
      "keep_on_founder_dashboard": true
    },
    {
      "name": "arpu",
      "category": "core",
      "signal_score": 15,
      "action_if_changes_20_pct": "Review plan mix, discounting, and upgrade path",
      "keep_on_founder_dashboard": true
    },
    {
      "name": "total_signups",
      "category": "vanity_or_diagnostic",
      "signal_score": 2,
      "action_if_changes_20_pct": "No action unless activation or paid conversion also changes",
      "keep_on_founder_dashboard": false,
      "better_version": "activated_signups_7d"
    },
    {
      "name": "total_traffic",
      "category": "vanity_or_diagnostic",
      "signal_score": 3,
      "action_if_changes_20_pct": "No action unless tied to trial conversion or MRR change",
      "keep_on_founder_dashboard": false,
      "better_version": "traffic_to_trial_activation_rate"
    }
  ],
  "filter_rule": "If 20pct change triggers no immediate decision, remove from founder dashboard"
}

FAQ

What are vanity metrics?

Vanity metrics are numbers that appear to measure business health but do not reliably connect to revenue, retention, or decisions. Common examples include total page views, total signups, app sessions, social impressions, and broad feature event counts. They look like progress because they move visibly, but a business can generate improving vanity metrics while MRR, NRR, and ARPU all deteriorate simultaneously.

What is the vanity metrics meaning in SaaS specifically?

In SaaS, vanity metrics typically refer to any measurement that can be improved without improving the recurring revenue engine. Because SaaS health is measured through subscription metrics — MRR, churn, NRR, expansion, ARPU — a vanity metric is specifically one that moves independently of those outcomes. High traffic that does not produce activated trials is the classic SaaS vanity metric.

What are common vanity metrics examples?

The most common vanity metrics examples in SaaS are: total website traffic (without conversion context), raw signup volume (without activation rate), total registered users (without active or paying breakdown), app session counts, feature event volumes, social media impressions, and total API calls (without revenue linkage). Any of these can become useful with the right denominator or downstream outcome attached.

Are vanity metrics always useless?

No. They become problematic when they take primary-dashboard real estate at the expense of revenue and retention metrics. A vanity metric like total signups can be useful as a diagnostic when paired with activation rate. Social impressions can inform brand awareness measurement. The problem is using them as proxies for business health when they have no reliable connection to recurring revenue.

How do I know if a metric is vanity?

The 20% rule is the fastest test: if the metric changed by 20% this week, would any operating decision change? If the honest answer is no or only indirectly, the metric is probably vanity for your current stage. A secondary test: could the metric improve through an action that does not improve the business? If yes — if you could buy more traffic, inflate signups with a giveaway, or generate feature events from bot traffic — the metric is gameable and therefore dangerous as a primary signal.

What should founders track instead of vanity metrics?

The core founder shortlist: MRR, new MRR, churned MRR (split by voluntary and failed payment), NRR, ARPU or ARPA, CAC payback period, and runway. Add activation rate and trial-to-paid conversion rate if the product has a free trial. This set cannot be easily inflated, directly measures business health, and triggers clear decisions when any metric moves beyond a threshold.

How do vanity metrics relate to the SaaS metrics that matter?

Vanity metrics typically measure inputs (traffic, signups) or activity (events, sessions) without measuring business outcomes (revenue, retention, expansion). The SaaS metrics that matter — MRR, NRR, churn, ARPU — all sit at the outcome layer. Vanity metrics are often leading indicators that could theoretically connect to outcomes, but only when defined rigorously enough to hold that connection. Most founder dashboards promote them to outcome status prematurely.

How many metrics should be on a founder dashboard?

Most founders need 6 to 8 core metrics on the primary view. The right dashboard is smaller than most founders expect — MRR, new MRR, churned MRR, NRR, ARPU, runway, one trend chart, and one alert block is a complete founder operating view. Everything else lives in secondary views and is accessed when a core metric triggers investigation, not as standing dashboard real estate.

Your Stripe already has all the data. NoNoiseMetrics turns it into the 8 metrics that actually matter — free up to €10k MRR →