Library · Subscriptions · How to run this
Frequency change is not a save
A frequency change can precede cancel. Churn % = cancels ÷ freq changes × 100. Type both.
Pair: Frequency-change churn on Subscriptions. Skips: skip stack depth. Fork: pause vs skip vs cancel.
What you type
Freq changes — subscription cadence / frequency changes in the cohort window.
Cancels — cancels that followed those frequency changes in the same window.
Churn % = cancels ÷ freq changes × 100. Offer a real save when churn % is fat — do not invent a churn chip.
What not to do
Do not invent churn %. Do not mix skips into frequency changes. Do not treat SKU swaps as cadence changes. Do not average every plan when one owns the hole.
Related: Subscriptions, skip stack depth, pause vs skip vs cancel, SKU swap margin.
Procedure
- Type frequency changes and cancels.
- Read churn %.
- Offer a real save when churn % is material.
Failure modes
- Inventing churn %.
- Mixing skips into frequency changes.
- Treating SKU swaps as cadence changes.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Frequency-change churn %
- Cancels after frequency changes ÷ frequency changes × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this skip stack depth?
- Sibling cancel path. [Skip stack depth](/manuals/ordergroove-skip-stack-depth) is avg skips per cancel. This page is cancels ÷ frequency changes.
- Is this pause vs skip vs cancel?
- Related MIT fork. [Pause vs skip vs cancel](/manuals/pause-vs-skip-vs-cancel) names the outcome. This page is churn after a cadence change.
- What churn % should I invent?
- None. Type frequency changes and cancels that followed from the same cohort window.