Product-led growth metrics: why they don't match your revenue dashboard
Activation is up 12% this quarter. Engagement looks healthy. Then finance closes the month and MRR growth is flat. Both dashboards can be telling the truth at once.
Your activation rate is up 12% this quarter. Your product analytics tool says engagement is healthy and time-to-value is dropping. Then finance closes the month and MRR growth is flat. Both dashboards can be telling the truth at the same time, because they are built from two different datasets that were never connected in the first place.
Quick answer
Product-led growth (PLG) metrics like activation rate, time-to-value, and product-qualified leads (PQLs) live in product analytics tools such as Mixpanel, Amplitude, or PostHog. Revenue metrics like MRR, expansion revenue, and net revenue retention (NRR) live in a billing system. Neither tool natively maps usage events to dollar movements, so a PLG dashboard can look strong while revenue growth stalls, or vice versa. Closing the gap requires connecting usage data to billing data directly, not adding another analytics tool.
Why product analytics tools stop short of revenue
Tools built for product-led growth are genuinely good at what they measure: activation, feature adoption, session frequency, funnel drop-off. A 2026 survey of 200 B2B software products by ChartMogul and Growth Unhinged found that Mixpanel, Amplitude, and Google Analytics were the three most cited "most impactful" tools for measuring and improving conversion, with ChartMogul the top-ranked tool actually built to track revenue.[1] That split is the whole problem in one data point: the tools people reach for to understand user behavior are rarely the tools that hold the revenue ledger.
This isn't a tooling failure so much as a scope one. A product analytics platform knows when a user completed onboarding, invited a teammate, or hit a usage limit. It generally does not know what that account is being billed, whether it's on a monthly or annual plan, whether a recent usage spike triggered an overage charge, or whether the account downgraded last billing cycle. Those facts live in the subscription and billing system, and most companies never wire the two together beyond an occasional CSV export.
The five-stage chain from usage to revenue
Every PLG funnel eventually has to cross into a real revenue event. Mapping each product stage to the MRR movement it should produce is the fastest way to see where the disconnect happens.
Signup and activation
A signup is not revenue. Activation, typically defined as reaching a first meaningful value moment, is also not revenue. Both are leading indicators. The mistake is treating a rising activation rate as if it guarantees a rising MRR; it only guarantees a larger pool of accounts that are eligible to convert.
Product-qualified lead (PQL)
A PQL is a usage-based signal (seat count, feature usage, API calls) suggesting an account is ready to pay or expand. This is the first stage where product data should genuinely predict a revenue event, but only if someone is tracking whether PQL-flagged accounts actually convert at a higher rate than the rest of the funnel. Most teams generate the PQL list and never close the loop back to billing.
Free-to-paid conversion
This is the first hard revenue event: a new MRR line item. The ChartMogul/Growth Unhinged study found a median free-to-paid conversion rate of 8% across the 200 products surveyed, but trials requiring a credit card upfront converted at roughly 30%, more than five times the rate of trials that didn't.[1] The mechanism matters as much as the product experience.
Expansion (seats, usage, tier upgrades)
This is where PLG's economics are supposed to shine, expansion revenue from an existing account growing its usage or seat count without a new sales cycle. It only shows up correctly on a revenue dashboard if usage-based or seat-based billing events are tied back to the account's subscription record in real time, not reconciled manually at renewal.
Contraction and churn
Downgrades, seat reductions, and cancellations are revenue events too, and they are the ones product teams are least likely to see coming, because a usage dip inside a product analytics tool doesn't automatically generate an alert inside the billing system, or vice versa.
Why ownership fragmentation makes this worse
Part of why this disconnect persists is organizational, not just technical. The same ChartMogul/Growth Unhinged survey asked respondents which team owns each growth metric. Product teams own activation 49% of the time, but they own free-to-paid conversion only 26% of the time, with sales (28%) more often holding that number.[1] Whoever owns activation is rarely the same person accountable for whether that activation actually turned into revenue, which means the two dashboards get built, maintained, and reviewed by different teams with different incentives to reconcile them.
Maxio's own list of the metrics it considers essential for a PLG model includes PQLs, activation rate, time-to-value, engagement, retention, free-to-paid conversion, expansion revenue, and churn rate side by side, treating product and revenue metrics as one connected list rather than two separate reports.[2] That's the right instinct. The gap is usually in the underlying data, not the metric definitions.
The metrics that actually connect usage to revenue
A revenue-connected PLG metrics stack needs a smaller, sharper set of numbers than the usual product analytics checklist, each one expressed in dollars, not just percentages.
Free-to-paid conversion rate, tracked in new MRR, not just percent converted. A 1 percentage point improvement in conversion translates to roughly a 15% increase in new revenue per trial cohort, according to the same ChartMogul analysis, which is a far more useful number for a growth leader's forecast than the raw conversion percentage alone.[1]
Expansion MRR by trigger type. Seat growth, usage overage, and tier upgrades are three different expansion mechanisms with different retention implications. Lumping them into one "expansion revenue" line hides which lever is actually working.
Net revenue retention, segmented by self-serve versus sales-assisted cohorts. A blended NRR number can mask a self-serve segment that's contracting while a sales-assisted segment expands enough to cover it. See our breakdown of how NRR compounds over time for the underlying mechanics.
Time-to-first-dollar, not just time-to-value. Time-to-value measures when a user experiences the product's core benefit. Time-to-first-dollar measures when that benefit converted into a billing event. The gap between the two is often where deals stall.
What it takes to close the gap
Closing this gap doesn't mean replacing a product analytics tool. It means giving the billing and revenue side of the business the same real-time visibility the product team already has into usage. That requires three things working together: subscription data that reflects plan changes and usage triggers as they happen rather than at the next invoice run, an MRR/ARR/NRR dashboard that breaks movements into new, expansion, contraction, and churned categories rather than one net number, and a pricing model flexible enough that usage growth actually shows up as billable expansion instead of being absorbed for free. Revvly's modular pricing engine supports usage-based and tiered billing specifically so that product usage translates into a real MRR movement rather than an internal metric no one outside product ever sees. For companies whose expansion motion already runs on usage-based pricing, the mechanics of how that revenue shows up are covered in our usage-based pricing guide.
None of this requires the product team to give up its analytics stack. It requires the revenue side of the business to stop treating billing data as something that only gets reconciled once a month.
Evaluation checklist
Before assuming a PLG metrics gap is a dashboarding problem, check the following:
- Does your free-to-paid conversion number get tracked in dollars of new MRR, not just a percentage?
- Can you break expansion revenue down by seat growth, usage overage, and tier upgrade separately?
- Is NRR segmented by self-serve versus sales-assisted accounts, or is it one blended figure?
- Does a usage spike or drop trigger any signal on the revenue side, or only inside the product analytics tool?
- Whoever owns your activation number, do they also see what happens to that cohort's MRR three months later?
Frequently asked questions
What is a product-led growth (PLG) metric? A PLG metric measures user behavior inside the product, such as activation rate, time-to-value, feature adoption, or product-qualified leads (PQLs). These metrics predict revenue outcomes but are not revenue events themselves.
Why doesn't my product analytics dashboard match my MRR? Product analytics tools track usage events; billing systems track subscription and revenue events. Unless usage data is connected directly to billing data, the two dashboards are built from separate sources and can diverge, especially around expansion and contraction.
What's the difference between a PQL and a paying customer? A product-qualified lead (PQL) is an account whose usage pattern suggests it's ready to convert or expand. It becomes revenue only once that signal actually results in a paid conversion or an upgrade, which is a separate event that should be tracked back to the PQL that predicted it.
Can a tool like Mixpanel or Amplitude track revenue on its own? Mixpanel and Amplitude are built to track user behavior and were rated among the most impactful tools for measuring conversion in a 2026 industry survey, but they are not billing systems and don't natively hold subscription or invoicing data.[1] Revenue tracking still requires a connection to the billing system of record.
How should expansion revenue be broken down for a PLG business? Expansion revenue should be split by trigger, seat growth, usage-based overage, and plan or tier upgrades, since each has a different retention profile and requires a different growth motion to sustain.
What is time-to-first-dollar and how is it different from time-to-value? Time-to-value is when a user experiences the product's core benefit. Time-to-first-dollar is when that benefit converts into an actual billing event. Tracking the gap between the two shows where conversion is stalling after activation.
Does fixing this require replacing our product analytics tool? No. It requires connecting existing usage data to billing and subscription data so revenue movements can be attributed back to the product behavior that drove them, typically through a unified revenue platform rather than a new analytics tool.
Sources
- Kyle Poyar, "The SaaS Conversion Report: What's working to improve free-to-paid conversion," ChartMogul and Growth Unhinged, 2026. https://chartmogul.com/reports/saas-conversion-report-2/
- "PLG SaaS: The Shift Toward a Product-Led Growth Model," Maxio, 2026. https://www.maxio.com/blog/the-power-of-product-led-growth
Frequently asked questions
What is a product-led growth (PLG) metric?
A PLG metric measures user behavior inside the product, such as activation rate, time-to-value, feature adoption, or product-qualified leads (PQLs). These metrics predict revenue outcomes but are not revenue events themselves.
Why doesn't my product analytics dashboard match my MRR?
Product analytics tools track usage events; billing systems track subscription and revenue events. Unless usage data is connected directly to billing data, the two dashboards are built from separate sources and can diverge, especially around expansion and contraction.
What's the difference between a PQL and a paying customer?
A product-qualified lead (PQL) is an account whose usage pattern suggests it's ready to convert or expand. It becomes revenue only once that signal actually results in a paid conversion or an upgrade, which is a separate event that should be tracked back to the PQL that predicted it.
Can a tool like Mixpanel or Amplitude track revenue on its own?
Mixpanel and Amplitude are built to track user behavior and were rated among the most impactful tools for measuring conversion in a 2026 industry survey, but they are not billing systems and don't natively hold subscription or invoicing data. Revenue tracking still requires a connection to the billing system of record.
How should expansion revenue be broken down for a PLG business?
Expansion revenue should be split by trigger, seat growth, usage-based overage, and plan or tier upgrades, since each has a different retention profile and requires a different growth motion to sustain.
What is time-to-first-dollar and how is it different from time-to-value?
Time-to-value is when a user experiences the product's core benefit. Time-to-first-dollar is when that benefit converts into an actual billing event. Tracking the gap between the two shows where conversion is stalling after activation.
Does fixing this require replacing our product analytics tool?
No. It requires connecting existing usage data to billing and subscription data so revenue movements can be attributed back to the product behavior that drove them, typically through a unified revenue platform rather than a new analytics tool.
Samuel builds the systems that turn billing events into trustworthy revenue numbers. He writes about retention, pricing, and the operational details that decide whether the metrics hold up.