Customer retention: measure return behavior and choose what to improve
Customer retention measures whether people continue getting value from a product. Before setting a target, decide what returning means for your users and how often they reasonably need to do it.
Define the return you want to measure
For a meal diary, a useful return might be logging another day's meals. For a collaborative planning tool, it could be updating a shared plan the following week. Opening the app is easier to count, but may not mean the user completed anything useful.
Choose the starting event, return event, unit of analysis and time window. Specify whether you count a return in a particular interval or any return after it. These definitions answer different questions, so comparisons need the same rule.
Compare cohorts at the same age
Group users by a meaningful start, such as first use or first payment, and compare them after the same amount of elapsed time. A recent cohort that has not yet reached week four cannot tell you its four-week retention.
In a hypothetical example, 1,000 users complete an initial action and 240 of those same users repeat the chosen action during week four. Week-four retention is 24% under that definition. Investigate differences by acquisition source, user need or onboarding path, while checking that the groups are large enough to interpret.
| Question | Metric | Keep consistent |
|---|---|---|
| Do people return to the task? | Behavioral retention | Start event, return event and observation window |
| Do subscribers stay? | Subscriber retention | Existing subscriber base and period |
| Does the existing base generate more revenue? | Net revenue retention | Revenue definition and treatment of expansion and churn |
| Do buyers purchase again? | Repeat purchase rate | Purchase cohort and time allowed for another order |
Keep product retention and revenue retention separate
A subscriber can keep paying while barely using the product, and an active free user can get value without paying. Track the behavior relevant to the product alongside subscription or purchase outcomes.
For an existing subscriber base, net revenue retention compares its recurring revenue at the end of the period with its starting revenue, including expansion, contraction and churn but excluding new customers. For example, $40,000 minus $3,000 in churn, minus $2,000 in downgrades, plus $6,000 in upgrades gives $41,000, or 102.5% NRR. That increase does not mean every customer stayed.
Investigate the reason for the drop-off
A curve tells you when people stop returning, not why. Combine it with support conversations, research and observed product behavior. Someone blocked by an import error needs a different change from someone who finished a one-off task or no longer needs the product.
Check whether users reached their first useful result, whether the task recurs and whether price or access rules interrupt it. Also inspect failed payments separately from deliberate cancellations. A lifecycle message will not repair a broken workflow.
Test a change that matches the cause
If new users cannot complete setup, test help or a simpler path at that point. If established users forget a recurring task, test a relevant reminder. If the product does not solve the problem well enough, revisit the workflow before adding an incentive.
Define the eligible users and expected behavior before the test. Where practical, use a randomized comparison and allow both groups to complete the observation window. Watch for unwanted effects such as more opt-outs, refunds or support requests. An association between a feature and retention is a reason to investigate, not proof that the feature caused the return.
Judge the improvement against its cost
Include the cost of development, support, messages and incentives when comparing a retention change with other priorities. More retained revenue is not automatically more profit, and a discount can preserve renewals while reducing the margin they contribute.
Longer customer tenure can improve lifetime economics, but it does not automatically shorten acquisition payback. Payback depends on when contribution margin recovers the acquisition cost. Compare alternatives over the same time horizon and keep assumptions about future retention visible.
FAQ
What is a good customer retention rate?
There is no useful universal target without a product, audience, return action and time window. Start with comparable cohorts in your own product and investigate meaningful differences.
Should retention always take priority over acquisition?
No. The choice depends on the user problem, expected effect, cost and confidence in the evidence. A product still needs people with a relevant need to discover it.
How quickly can a retention test be evaluated?
The cohort must have time to complete the return window you chose. For a monthly task, a few days of activity cannot establish monthly retention.
Should onboarding be the first thing to change?
Only if the evidence points there. Early drop-off can suggest an activation issue, but the curve alone does not establish its cause.
Sources
Discuss your product's next step
I help define product priorities, plan launches and investigate where users drop out.
