A dormant user is someone who created an account or used your product in the past but has not shown meaningful activity for a defined period. The exact threshold depends on your product and your goals. A banking app may flag dormancy after thirty to forty five days without a sign in. A shopping app may flag dormancy after fourteen days without a visit or a cart action. Knowing who is drifting lets you act early, revive value, and protect retention and revenue.
Plain language explanation
Think of dormancy as quiet mode. The person still exists in your database and often still has the app installed. They just have not done the key thing you care about for a while. Your job is to notice the silence quickly and offer the right nudge back.
How to define dormancy for your product
- Choose the anchor activity
Pick the action that proves intent. Examples include sign in, session start, add to cart, stream start, order, or bill pay.
- Set the time window
Match the window to expected cadence. Daily trackers may choose seven days. Weekend services may choose fifteen days. Financial services may choose thirty to sixty days.
- Segment by lifecycle
Trial users, new subscribers, and longtime customers behave differently. Use separate dormancy rules for each segment.
- Document the rule
Example
A user is dormant if there has been no app open or web session for fourteen days and no conversion events in that same period.
Why users go dormant
- Onboarding was unclear and the first value moment never happened
- Content or inventory felt thin or stale
- Price or paywall friction created drop off
- Notifications were irrelevant or too frequent
- Technical issues or slow performance degraded trust
- They achieved their goal and forgot to come back
Use data to validate the cause. Read session replays, support tickets, store reviews, and survey responses. Correlate drop offs with releases and pricing changes.
Early warning signals
- Drop in session count over seven day moving average
- Declining depth of session such as fewer screens or short play time
- Fewer high intent actions such as search or add to cart
- Notification mute or email unsubscribe
- App uninstall or reduced open rate of owned messages
Set alerts on these signals and reach out before the user crosses your dormancy threshold.
Measurement and reporting
- Dormancy rate by cohort and by acquisition source
- Time to dormancy from signup or last conversion
- Save rate after a re engagement touch
- Revenue recovered from revived users
- Share of active base at risk based on early warning signals
Report these alongside new user metrics so the team sees both sides of growth.
Re engage playbook
Principles
- Make the return path short with deep links to the exact task
- Lead with value that matches past behavior
- Remove friction on sign in and payment
- Limit contacts and cap frequency
- Stop when a user clearly says no
Tactics that work
- Contextual email or SMS with a direct path to a product, playlist, or bill
- Push notification with a clear action and a deep link to the screen that completes it
- Time bound offer or credit that unlocks with one tap
- New feature announcement that maps to the last feature they used
- Social proof such as ratings or friend activity that is relevant and tasteful
- Win back ads to opted audiences using privacy safe targeting
- On open checklist that showcases quick wins and hides advanced options until later
For uninstalled users
- Email or SMS with a smart app banner and a deferred deep link that restores context after install
- QR codes in physical places that lead to the same deferred deep link
Prevention playbook
- Deliver a crisp first session that proves value within minutes
- Personalize the home screen based on the first three interactions
- Use gentle education inside the product rather than long tutorials
- Rotate content or inventory that drives repeat visits
- Set frequency caps for notifications and test send times
- Create habit loops such as streaks or saved items that wait for the user’s return
- Ask for feedback after friction moments and fix the top issues quickly
Common mistakes
- One size fits all dormancy rule that ignores lifecycle and product cadence
- Sending users back to the home screen rather than the task they wanted
- Over discounting which trains people to wait for offers
- Measuring only open or click and not the downstream action
- Blending opt in and opt out audiences in the same analysis
- Treating dormancy as a media problem rather than a product value problem
How grovs.io helps
Grovs detects at risk users with behavior signals, routes email and push links straight to the right in app screen, and measures the outcome clearly. For users who removed the app, Grovs uses privacy aware deferred deep links so the first open resumes exactly where the click intended. Your team gets segment level insights, clean experiments, and automated win back journeys that respect consent.
Frequently asked questions
What is a dormant user
Someone who has not performed your defined key action for a set period even though they still exist in your system.
How long before a user is considered dormant
It depends on your product cadence. Many consumer apps use seven to fourteen days. Finance and utilities often use thirty to sixty days. Choose based on real usage patterns.
Is a dormant user the same as a churned user
No. Churn usually implies a formal end such as cancellation or uninstall. Dormant means inactive but still reachable.
What is the fastest way to re engage someone
Send a deep link to the exact next best action. Reduce sign in friction and show immediate value on return.
How often should I contact dormant users
Start light. One to two touches in the first week after the threshold, then pause or switch channels if there is no response. Respect opt outs.
Which metric shows success
Save rate, which is the share of dormant users who return and complete a key action within a set window, plus revenue recovered and subsequent retention.
How do I avoid discount dependency
Lead with product value and relevance. Reserve monetary offers for high value cohorts and cap their use.
What about privacy
Honor consent, provide clear choices, and avoid sensitive data in messages or links. Use aggregate reporting when individual tracking is not allowed.
Related Terms