Pushlane: Dormant User Re-Engagement Push Playbook
Build a 30, 60 or 90-day dormant-user push playbook from each product's real usage rhythm, current subscription state and a credible reason to return.
A dormant user re-engagement push notification should begin with the product's normal rhythm. Thirty days can be a severe lapse for a daily language app and completely normal for a quarterly planning tool.
The 30, 60 and 90-day labels are useful analysis windows, not universal send dates. Pushlane can evaluate recent product events, current lifecycle state and delivery eligibility before deciding whether a return message still makes sense.
This playbook separates dormancy from churn and gives each message one credible reason to return.
Define dormancy with a meaningful event
Choose the action that represents real use, not any app launch.
Examples include:
- a workout completed;
- a lesson finished;
- a report reviewed;
- a budget updated;
- a project exported;
- a planned meditation session completed.
Then define a lapse relative to the expected interval. A weekly product might consider someone dormant after missing two expected cycles. A monthly report product needs a longer window.
Avoid psychological labels such as "lost interest" or "low intent." The observable fact is that a meaningful action has not occurred within a defined period.
Separate dormancy from subscription state
A dormant user can be free, trialing, actively paid, canceled with access remaining or expired. Those states require different messages and exits.
| State | Possible message job |
|---|---|
| Free and activated | Return to a useful unfinished task |
| Trialing | Reach premium value before actual expiration |
| Active paid | Use a benefit already included in the plan |
| Auto-renew off, access active | Use remaining access without pretending it already expired |
| Expired | Consider a current reason to resubscribe |
Do not send a generic "We miss you" to all five groups. Use a reconciled state attribute or an event-driven lifecycle flow with explicit exits.
The segmentation guide explains how to combine current state, behavior and reachability.
Turn 30, 60 and 90 days into review stages
Use staged windows only when each stage offers new value.
First missed rhythm
Remind the person about the unfinished or newly available job.
Your weekly review is ready
See the changes since the last report you opened.
Longer lapse
Lead with a product change, saved progress or specific benefit the user has not seen. Do not repeat the first message with stronger urgency.
Your saved plan has a new starting point
Review the schedule before deciding whether to continue.
Extended dormancy
Use only when there is a credible new reason to return. Otherwise stop. A final preference check can be more respectful than another promotion.
The exact dates should match the product. Record why each window exists before launch.
Build the flow from current evidence
scheduled dormancy evaluation
-> audience: no meaningful action in the defined window
-> branch: current subscription state
-> branch: reachable, consent-eligible iOS device
-> branch: no recent contact conflict
-> send one state-appropriate return path
-> exit on meaningful action, opt-out or state change
Scheduled audience entry can re-enter current members. Apply explicit limits so the same dormant user is not messaged forever.
An event-triggered alternative is useful when a server knows the moment a report, lesson or plan becomes relevant. Event timing is stronger than a calendar when fresh value exists.
Give the tap somewhere useful to land
Open the saved project, next lesson, new report or preference screen named in the message. Do not land every dormant user on the home screen.
Test whether the destination still exists after a long absence. Handle logged-out sessions and changed accounts. If saved data was deleted under a retention policy, do not imply it remains available.
For an expired subscriber, refresh authoritative entitlement state before deciding whether to show access or a current purchase option.
Avoid manufactured familiarity
Dormant-user copy often becomes overly personal. Use only facts the product can safely expose.
Avoid:
- "We know you've been struggling";
- streak loss threats after the streak already ended;
- private health or financial details on the lock screen;
- invented scarcity;
- discounts that are not available at the destination;
- guilt about the time away.
Apple's notification guidance recommends concise, high-value information and avoiding sensitive content. That standard matters more as the lapse grows and context fades.
Stop on return and lifecycle change
The first meaningful product action should end the sequence. An app open alone may not be enough if the user immediately leaves, but it can suppress another push during the active session.
Also stop or reevaluate on:
- trial conversion;
- verified purchase or renewal;
- billing issue;
- cancellation or expiration;
- logout or identity transfer;
- explicit opt-out;
- no active supported device.
RevenueCat's common webhook flows show why current subscription state cannot be inferred from one old event.
Measure reactivation without claiming retention
Choose the meaningful action as the primary outcome. Report restored paid access separately for expired users.
reactivation rate = eligible dormant users completing the target action in window / eligible dormant users
Track sends, suppressions, attributed opens, destination failures and opt-outs. Keep 30, 60 and 90-day cohorts separate because the baseline likelihood of return differs.
When volume supports it, use a stable holdout within each eligible state and dormancy window. Do not compare a highly engaged 30-day cohort with a 90-day group and call the difference a campaign effect.
Earn the return
Dormancy is a time gap, not a diagnosis. Define it from the product's real rhythm, branch on current subscription state and send only when a useful destination still exists.
If the team cannot name what is newly helpful, silence is a better re-engagement strategy.