Guide
Cancellation Save Rate: Definition, Denominator, and MRR Weighting
“Save rate” sounds simple until three teams use three formulas. For voluntary cancel flows, agree on what counts as a save, who enters the denominator, and whether you weight by subscription value before you set targets.
Hub: cancellation flow analytics. Offer strategy context: SaaS retention offers.
Last updated October 23, 2026
What counts as a save
- Customer completes the flow still subscribed after accepting an in-flow offer (pause, discount, plan switch)
- Customer abandons cancel without completing — only if you can prove subscription status unchanged; treat as ambiguous unless instrumented
- Not a save: support manually reactivates days later outside the flow unless you tag that channel separately
Denominator choices
Pick one denominator per dashboard. Mixing “saw offer” with “started flow” will make week-over-week trends meaningless.
| Denominator | Use when |
|---|---|
| Sessions that reached “reason selected” | Comparing offer copy and reason branches |
| Sessions that saw any retention offer | Measuring offer acceptance only |
| Completed cancels + saves | End-to-end flow effectiveness |
Weight by MRR when ARPA varies
Ten saves on entry-tier plans can mask two enterprise losses. Report saved MRR and lost MRR alongside session counts. Analysis patterns: customer churn analysis.
Anti-patterns
- One company-wide save rate with no reason or plan split
- Counting involuntary recovery as cancel-flow success
- Publishing or targeting third-party benchmark save rates without your own evidence
- Optimizing save rate when skipping retention offers is the right UX for some segments
Save rate by reason and plan
ChurnIntel breaks out voluntary saves and cancels with session MRR.