CacheMagpie logoCacheMagpie· Community Library

Winback email tests and learnings

Winback works when it is honest about why someone left and narrow about what it asks next. Asking a question, surfacing what changed, and setting a clear stop point beat escalating discounts on lapsed contacts. The biggest gains usually come from tighter targeting of who is worth contacting at all.

  • What the winback stage is for and the metric you own
  • Test ideas grouped by lever, from targeting to offer
  • The winback tests most teams skip, and how to run one properly
  • Guard metrics, and graded evidence from real programs

What the winback stage is actually for

Winback exists to recover value from people who already know you and stopped. Because they know you, novelty does nothing and pressure carries real cost: this is the population most likely to unsubscribe, complain, or mark you as spam.

The metric you own is the reactivation rate inside a defined window, paired with the value of what reactivated contacts do next. A campaign that produces one cheap order from a dormant contact who then lapses again has not won anything.

The definition of lapsed is itself a design decision. Most programs use a single global window when purchase cycles differ wildly by category, which quietly puts active customers in the winback bucket and truly dormant ones nowhere.

In CacheMagpie, every test in this cell records its own primary metric, and the metric you own here is reactivation rate. Check that a test's metric lines up with yours before you copy the learning.

Where winback sits in the lifecycle

Winback sits at the end of the lifecycle and feeds back to the start. Contacts who return re-enter retention, and contacts you decide to stop messaging should leave the sendable list rather than sit there depressing every rate you report.

What you can test at the winback stage

Each group below is one variable. A clean test changes one of them and holds the rest still, which is the difference between a learning and a story.

Targeting and eligibility

  • Test a category specific lapse window against a single global one.
  • Test excluding contacts with no engagement since sign-up, who are a different problem entirely.
  • Test prioritising the contacts with the highest previous value rather than treating all lapsed contacts alike.

Ask and framing

  • Test asking what went wrong against offering a reason to return.
  • Test surfacing what has changed since they left against restating the original pitch.
  • Test a single specific next action against a general invitation to come back.

Offer and non-price levers

  • Test no incentive against your standard winback offer, read on repeat behaviour rather than the first order.
  • Test a service lever, such as restored settings, saved data or a faster route back, against a discount.
  • Test escalating the offer across touches against holding it constant.

Cadence and stop conditions

  • Test two touches against four, with complaints and unsubscribes read as primary results.
  • Test a permanent stop point after which the contact is suppressed rather than recycled.
  • Test a preference step, offering less frequent contact instead of nothing.

Channel

  • Test whether an SMS or push touch adds recovered contacts or only pulls the same people forward.
  • Test sending the last touch on a different channel from the first.
  • Test suppressing the channel where the contact went quiet first.

What the graded tests say about aggressive defaults

Across the graded tests in this stage, targeting and segmentation, timing and delay carry more of the winning reads.

The highest-value winback tests most teams skip

Winback is usually run as a campaign and rarely as a program, which leaves these tests untouched.

The definition of lapsed

Changing the window that defines the audience often moves reactivation more than anything inside the message, and it costs nothing to test.

The permanent stop

Deciding when to stop messaging a dormant contact is a test with an unusual profile: it improves deliverability, complaint rate and reporting accuracy at the same time, and it is almost never run.

The sunset preference step

Offering a lower frequency instead of a final offer keeps contacts who would otherwise unsubscribe, and very few programs have measured how many.

How to run a winback test

Randomise inside a single lapse cohort so both arms have the same recency profile. Read reactivation over a window that matches your purchase cycle, and always keep a no contact holdout so you can see how many would have come back on their own.

Set the sample size and the read date before the test ships, not after you have seen the first day of data. If the audience cannot reach the sample you need inside a sensible window, change the test rather than the standard: pick a lever with a bigger expected effect, or widen the trigger.

A test card template for Winback

Hypothesis
Because contacts lapsed for [window] respond to [reason], sending [variant] instead of [control] will increase the share who complete [return action].
Success criteria
Reactivation rate against a no contact holdout inside a fixed window, with value of the return action as a secondary read.
Guard metric
Complaint rate, unsubscribe rate and spam placement on the sending domain.

Free to copy and use in your own program. Fill the brackets from a test you have read in the library.

Guard metrics: what a win must not cost

This audience is the most fragile part of your list. These reads decide whether a win is real.

  • Complaint rate, which matters more here than anywhere else in the lifecycle.
  • Unsubscribe rate, read against the no contact holdout.
  • Deliverability and inbox placement during and after the campaign.
  • Second action rate of reactivated contacts, so a single discounted order does not count as recovery.

Evidence from real Winback programs

The library holds 21 graded tests run by Winback teams: 18 report a win for the variant, 1 a loss, and 2 no clear difference.

Winning tests in this cell read above the rest of the library, across 13 comparable tests.

Direction, grade and source are free. Exact figures open up once you sign in.

Winback tests by channel

The same stage behaves differently depending on the channel carrying it. These counts are published tests in this cell.

What a winning winback test looks like

A winning winback test beats a no contact holdout, not a previous campaign, and it does so without a rise in complaints.

The durable winners are targeting and stop conditions. Offer led wins in this stage decay fastest, because a lapsed audience learns the pattern quickly and waits for it.

Frequently asked questions

Does winback messages still work in 2026?

The library holds 21 graded tests here, and 18 of them report a win for the variant against 1 losses and 2 with no clear difference. That is enough to say the direction still holds, and not enough to promise a number for your own program.

What is the most credible winback test in the library?

Plain-text style subject line beat the branded promo subject in win-back. In win-back, a plain, human subject line outperformed the branded promo phrasing on opens without hurting unsubscribes.

What tends to fail in winback messages?

A discount can win the conversion and lose the P&L, so judging win-back by reactivations rather than margin flatters the wrong variant. Losing tests are kept in the library on purpose, because knowing what did not move is as useful as knowing what did.

How fresh are these winback learnings?

The newest record in this cell is from 2026 and the oldest from 2020. 1 record has been reviewed and vouched for by the CacheMagpie editor.

Which metric should I judge winback tests on?

The metric you own for this stage is reactivation rate. Every test in this cell records its own primary metric, so check that it matches yours before you copy the learning.