Claim and evidence
Target users inactive for 30, 60 or 90 days with a short multi-channel sequence offering a reason to return, then stop with a breakup message.
No dated example yet. Treat this tactic as a hypothesis.
Vendor claim
A tool vendor reports numbers about its own customers or product. Useful, but not independent.
Working · 2026-07 Braze guide published July 2025, edited July 2026.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Timing, relevance and a clear reason to return reactivate a fraction of dormant users; a defined end protects deliverability and goodwill.
How to run it
- Define inactivity for your cadence
- Segment by recency and value
- Offer a reason (feature, offer, reminder)
- Use one journey across channels
- Ask why they left
- End with a breakup message
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option AFeature reason
Lead with what has changed in the product since the user last came back.
- Option BOffer for high-value lapsers
Reserve discounts or credits for the most valuable segments and use reminders for the rest.
- Option CBehaviour-triggered message
Tie the message to a recent real-world action, like Ibotta's email after a shopping trip.
- Option DBreakup message
Close the sequence with a note that you will stop writing, plus one easy way to stay.
Timeline
- 12025 Ibotta — Automated re-engagement via Braze incl. a 'Switch and Save' email 24 hours after a shop trip.
- 22026-07 status checked: Working
Dated examples
- 2025
Ibotta
Automated re-engagement via Braze incl. a 'Switch and Save' email 24 hours after a shop trip.
15% open, 1% CTR, 8% conversion (as published by Braze).
braze.com · 2025-07-17
Does it still work?
Braze guide published July 2025, edited July 2026. source
Risks
- Vendor-reported results
- Discount reliance
Sources
Change log
- 2026-11-20 — harvest v0.1 (retention)