Study first
Review the ideas behind the questions
Retention growth accounting separates who is newly active, still active, returning after dormancy, or newly dormant. Read the movement with the right usage interval and critical event before recommending more lifecycle spend.
Define The Movement Before The Readout
A retention readout needs a time frame and a value event before it can explain movement. Otherwise, teams can confuse visits, logins, or one-off returns with durable customer activity.
- Retention should be measured against a critical event that reflects the product's core value, not just any visit.
- The product usage interval matters because it defines the time frames for new, current, resurrected, and dormant users.
- Pulse ratio compares incoming active users with outgoing dormant users, but it does not explain why the movement happened.
In Practice
Match The Interval To The Product
A weekly-use product and a monthly-use product need different retention windows. The readout should not punish customers for a return pattern that is normal for the product.
Do Not Let Logins Replace Value
If the retained-user action is too shallow, lifecycle growth can look stronger than the customer's real progress.
Common mistakes
Calling all returning logins retained customers when the product value comes from completing a meaningful action.
Count retention on the critical event that represents value, then read lifecycle movement from that event.
Q&A
Why does the usage interval matter?
It sets the time frame for deciding whether a customer is current, dormant, new, or resurrected.
What does pulse ratio not prove?
It shows active-user inflow versus dormancy in the selected interval, but it does not prove which campaign or product change caused the movement.
Check Reactivation Quality
A reactivation campaign can bring people back without rebuilding durable usage. Compare resurrected users with current and new users, and look at the value action after they return.
- A resurrected-user opportunity pool should be scoped to people active in a previous lookback period but inactive in the current period.
- Resurrected users should be compared with current and new users, not only counted as returned.
- Critical-event performance after return is a stronger quality check than a simple active-user count.
In Practice
Separate Opportunity Size From Quality
A large dormant pool tells you who could be reached. It does not say whether returning users will behave like healthy current users.
Use Behavior And Qualitative Clues
Current-user diagnosis can compare retained and dormant groups, then use user conversations or activity sequences to explain the pattern.
Common mistakes
Funding more win-back just because many dormant users exist.
Check whether resurrected users perform the critical event and retain well enough compared with current and new users.
Q&A
What should a reactivation report check after people return?
Check whether resurrected users complete the value action and whether their retention pattern is healthy compared with current and new users.
When is a dormant pool not enough to justify a win-back budget?
It is not enough when the team has not checked whether resurrected users return to valuable, durable behavior.
Keep Cohort Comparisons Honest
Growth accounting gets more useful when each lifecycle group is compared against the right neighbor. A reactivation result should not be read like new-user acquisition, and current-user health should not disappear from the story.
- Current-user diagnosis can compare retained current users with dormant current users to find behavior differences.
- Resurrected-user performance should be compared with current and new users so return volume does not hide weak retention.
- Behavior clues and customer conversations can help explain why retained and dormant users differ.
In Practice
Compare Like With Like
Use the same interval and critical event when comparing lifecycle groups, then explain which group moved and why it matters.
Look Past First Return
A win-back result is stronger when resurrected users continue returning and perform the critical event, not just when they make one visit.
Common mistakes
Calling reactivation healthy because many people returned once, without comparing later retention or value behavior.
Compare resurrected users with current and new users, and check critical-event behavior after return.
Q&A
What is the wrong comparison for resurrected users?
Counting only first-return volume is too thin. Compare their retention and value behavior with current and new users.
How can a team explain why current users become dormant?
Compare retained and dormant current-user behavior, then add customer conversations or activity-sequence review to explain the pattern.