Reactivation MRRWin-back Revenue
Recurring revenue recovered from previously churned customers.
Put this metric to work: explore FlowMRR's MRR movement analytics to track revenue movements, retention and forecasts from your Stripe account, or see how FlowMRR compares as a Baremetrics alternative for Stripe.
The fifth MRR movement, often hidden inside 'new'. In FlowMRR a reactivation is judged on the person (email first, Stripe customer ID as fallback): a customer back from zero on any product who has paid before, even under a new Stripe customer record. It is valued at what they pay on return, and no time window applies. Tracking it separately reveals the ROI of win-back campaigns and whether churned customers are recoverable at all.
Formula
Reactivation MRR = Σ MRR of customers who paid nothing last month but paid at some point beforeWorked example
12 previously churned customers resubscribe this month at an average $180/mo → Reactivation MRR = $2,160.
Other definitions you will see
Some tools apply a win-back window, often 12 months, and book later returns as new MRR. Others match returns on the Stripe customer record or the subscription, so a customer who comes back under a new record counts as new. Some report no reactivation leg at all and fold it into new MRR.
Illustrative comparisons
Share of new + reactivationThese unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.
Why it matters
Reactivation is some of the cheapest revenue you can win: these customers already know the product. A healthy reactivation stream means your churn is often pausable, not permanent — and it justifies investing in win-back emails, downgrade-instead-of-cancel flows, and exit surveys. Folding it into 'new MRR' hides that lever entirely.
Common mistakes
- Counting reactivations as brand-new logos, which inflates new-business performance.
- Reading every return the same way — a customer back after 18 months is not the same signal as one back after 1, so segment returns by time away.
- Ignoring why they left, so they churn again for the same reason.
Calculating it from Stripe data
A reactivation is a customer who paid nothing last month but paid at some point before. To find them you need full history: compare each customer's MRR this month with last month's, and for those coming from zero, check whether they ever paid earlier. Count it on the customer, not the subscription. A returning customer usually starts a new subscription with a new ID, and often a new Stripe customer record too, so match on email or your own account ID; otherwise the return is booked as a brand-new customer. FlowMRR judges this on the person (email first, Stripe customer ID as fallback): someone back from zero on any product is a reactivation.
Reactivation MRR is what the customer pays when they come back, on the same basis as MRR: monthly-normalised, forever coupons deducted. If they return at a lower price than before, the difference is not contraction; the old amount already left as churn. A former customer who restarts with a trial is reactivated in the month they first pay again, not when the trial starts. Someone who never paid, for example a trial that never converted, is new when they finally pay.
Some returns are not win-backs. In FlowMRR a paused subscription that resumes is booked as contraction then expansion, without churn or reactivation. An unpaid subscription whose invoice is finally paid never ended in Stripe, so it is a recovered payment rather than a returning customer. Decide whether you limit reactivations to a time window: FlowMRR applies none, so a customer back after two years counts like one back after two months. If you want to separate the two, segment by time away instead of moving long absences into new MRR.
Reading the result
Read reactivation against the pool it comes from: reactivated customers in a period ÷ customers who churned before it gives a win-back rate, which is more telling than the amount alone. Split it by why customers left. Customers who churned involuntarily, after a card failed, often return once they update their payment method; customers who cancelled voluntarily return when something changed, such as a feature, a price or their own needs.
Keep reactivation as its own leg in net new MRR and never subtract it from churn: netting the two hides how many customers actually leave. Rising reactivation alongside rising churn can mean customers are cycling (cancelling in quiet months and returning in busy ones), which points to an annual or pause option rather than to stronger retention.
Frequently asked questions
Is reactivation MRR counted as new MRR?
It should not be. New MRR comes from customers who have never paid; reactivation MRR from customers who paid before, stopped and came back. Folding the two together overstates acquisition and hides how much revenue comes from former customers.
How long after churning does a returning customer count as a reactivation?
Under the usual definition there is no limit: any customer who paid before and paid nothing last month is a reactivation when they pay again. Some teams set a window, such as twelve months, and treat later returns as new; if you do, apply it consistently and state it.
How do I track win-back revenue from Stripe?
Compare each customer's MRR month by month across all their subscriptions and customer records, grouped by email or account ID. A customer going from zero to a positive amount who has paid before is a reactivation; their new MRR is the win-back revenue for that month.
Do reactivated customers count in NRR?
Only if they belong to the starting cohort. A customer who was paying at the start of the 12-month window, left and returned counts at what they pay at the end. A former customer who was not paying at the start of the window stays out, even if they returned during it.