Activation & Usage
Usage Habit Recovery
Regular use stops → return to the relevant point → recovered or exit
Bring back a user whose regular use stopped by opening the last meaningful context or the next small action.
- Relationship Recovery & Intervention
- Push
9 steps · 2 decisions · 2 exits
Open the canvasFlow structure
- 9 steps
- 2 decisions
- 2 exits
Core rule
A recovery message opens the next useful action instead of only asking the user to come back.
Journey plan
When to set it up
Usage analytics showing previously regular users going quiet for seven days, in numbers that matter to your weekly active base, are the signal to build this. Usage events have to be tracked per user identity and regular use defined around the product's rhythm; the last used content must be stored for the deep link, and push permission and email subscription must be known. If usage stopped because of a bug, an outage or content that disappeared, fix that first, and keep users who never reached first value out of this flow; a recovery message cannot deep-link to value that is not there.
How to measure success
Incremental habit recovery rate vs control
What matters is how many more users in the messaged group rebuild regular use than in the control group; a single app open or a push tap is not that outcome.
How it is counted: Count every user assigned to the two groups at entry; of those, the share who again show the repeated meaningful action you defined around the product's rhythm within the same follow-up window after assignment is the metric, and the difference between the two groups is the journey's contribution. Delivery or taps on a message do not change the denominator.
Also track
- Return rate within 7 daysAssigned users who come back to the product at least once, as a share; an intermediate step that does not mean the habit returned, and never merged into the same report line.
- Returns per touchRead returns in the three days after the push and the seven days after the email separately; if the email adds no returns, try a one-touch version.
- Push opt-outs and unsubscribesWatch push permission turned off and email unsubscribes after the messages; a rise means the text went no further than asking people back, or pushed too hard.
How to set it up
- Trigger and entryA previously regular user showing no usage for 7 days triggers entry, and the first push goes out without a wait. At entry, randomly split eligible users into the journey group and a control group this flow never messages.
- Who must not enterUsers who never reached first value or never built a regular pattern stay out. So does anyone in another active churn journey, to avoid overlapping recovery messages. One broken usage pattern is the scope; no second attempt opens for the same person at the same time.
- Timing and channelsAs soon as the trigger fires, a push deep-links to the last used content or action. If usage has not resumed after 3 days, an email shows one low-effort restart step; the final check comes 7 days after that. Each message opens the next useful action rather than only asking the user back.
- Exit and handoffUsage seen at the three-day check ends the journey and the email is not sent; usage at the seven-day check ends it too. With no return at the final check, recovery communication stops. The user is handed to no other journey and is not messaged again once the window has closed.
- Frequency and consentEach recovery attempt is capped at two touches: one push and one email. Push goes only with permission and email only with a subscription; neither text uses guilt-based language, and no second email or extra channel is added.
What to watch when reading the result
- 1If the share rebuilding the habit in the journey group does not rise above the control group, the message only brought forward users who would have returned anyway; more single opens or taps do not close that gap. Such a result calls for questioning where the deep link lands, not for adding touches.
- 2These findings hold for the seven-day gap definition, the immediate push, the email after three days and the final check seven days later. Users in an active churn journey never entered, so do not credit their return here; activation of users who never reached first value is read separately.
- 3With a small gap or small groups, enter the control group's habit recovery rate and the smallest gap you want to catch into the sample size calculator; divide the users needed per arm by daily entries to see how many days the test needs, and do not decide before then.
- 4Even with a good return rate, if usage breaks again a few days later the habit has not returned; extend the follow-up to the product's rhythm, and send no new message to the same person once the recovery window has closed.
Frequently Asked Questions
Who should enter a usage habit recovery journey?
Use it for previously regular users whose usage has stopped. This example checks a seven-day gap. Keep users who never reached first value separate and avoid overlapping with an active churn intervention.
What should a habit recovery message link to?
Lead to recently used content or a small relevant action. This example sends an email after three days if usage has not resumed. Make the reason to return clear in both the message and destination.
Does one app open prove the habit has returned?
It can count as a return, but assess restored regular use separately. Define repeated meaningful actions around the product's rhythm. End the bounded sequence if it fails. Keep reopening and sustained usage distinct.
Explore other journeys
Tiered Churn Intervention
When churn risk crosses a threshold, choose a response based on the strength of the signals and check whether usage recovers.
Predicted Replenishment
Remind users before a repeat-use product is likely to run out, while clearly treating the timing as a prediction.
Lapsed Customer Win-Back
Bring back a former paying customer after enough time has passed for a meaningful reason to return.