Skip to content
Learn · Growth for small teams

Retention and win-back flows

Retention keeps already-active users engaged; a win-back flow re-engages those who have lapsed. The flow triggers on a dormancy window matched to your product's natural cadence, sends a short sequence of two to four messages, and then suppresses non-responders to protect deliverability.

Updated 10 Jun 20266 min readBy fromHello
Key takeaways
  • Retention and win-back are different jobs: keep the active engaged, bring the lapsed back.
  • Trigger win-back on a dormancy window matched to how often your product is normally used.
  • Keep it short — two to four messages — and suppress non-responders to protect deliverability.
  • Measure 7-, 30-, and 90-day post-return retention, not just the reactivation click.

Two jobs, not one

Retention and win-back sit at different points in the lifecycle. Retention keeps users who are still active engaged and getting value. Win-back — sometimes called resurrection — targets users who have already lapsed. Amplitude defines a resurrected user as a previously inactive user who returns. Conflating the two leads to nagging active users and ignoring the ones actually slipping away.

A short win-back flow: a dormancy window triggers a two-to-four message sequence, ending in a last-chance message and suppression of non-responders.

Set the trigger to your cadence

The dormancy threshold that should trigger a win-back depends on how often your product is naturally used. A daily app might consider a user dormant after one to two weeks; a monthly tool, not for several weeks longer. Picking a window that matches the cadence is the whole game — too short and you pester active users, too long and they're gone before you reach out.

Keep it short, then suppress

A typical win-back is two to four messages: a soft we-miss-you check-in, a reminder of the value or an incentive, and a last-chance confirm-you-want-to-stay. Short is deliberate. Repeatedly emailing people who don't engage hurts your sender reputation, so non-responders should be suppressed — removed from the active list — which also keeps your data and consent posture clean.

Measure real returns, not one-time clicks

Don't judge win-back by the reactivation click alone. A user who opens once and leaves again isn't won back. Track retention at 7, 30, and 90 days after they return, so you can tell a genuine resurrection from a one-time bounce. Segmentation helps here — grouping users by how recently and often they engaged tells you who's worth a win-back at all.

FAQ

Common questions

  • What is a win-back flow?

    An automated re-engagement journey for users who have lapsed. It triggers on a dormancy window, sends a short sequence of two to four messages, and suppresses anyone who doesn't respond to protect sender reputation.

  • When should a win-back email trigger?

    After a dormancy window matched to your product's normal usage cadence. A daily app might trigger after one to two weeks of inactivity; a monthly product much later. Match the window to how often people normally use you.

  • How many win-back emails should I send?

    Usually two to four: a soft check-in, a value or incentive reminder, and a last-chance message. Keep it short — emailing non-responders repeatedly damages deliverability, so suppress people who don't re-engage.

  • How do I measure win-back success?

    Not by the reactivation click alone. Track retention at 7, 30, and 90 days after a user returns to separate a genuine resurrection from a one-time open. A real win-back stays; a bounce doesn't.

See the platform the team runs.

Related guides
Early access

Put your growth teamon autopilot.

Early access opens Q3 2026, gradually, so the team tunes to real use cases. Small teams with big ambitions go first.

Not ready to share an email? It's open source. Run it yourself today. View on GitHub

No spam. One email when your spot opens. Unsubscribe at any time.