Win-back email campaign
Build winback around the repurchase cycle and customer context, not one fixed delay for the entire list.
Define what an inactive customer means for your store
No new order does not mean the same thing in every store. A consumable buyer may need replenishment; a furniture buyer may have no further purchase planned for a long time. A winback sequence starts with that difference. It aims to restart a relevant conversation with customers who have drifted away, rather than keep pushing until any response appears.
Before choosing a delay, define which behaviour you want to recover. Buying again, replying to a question and showing interest in emails are different signals. Mixing them can label someone inactive even though they buy through another channel, or recovered merely because they opened a message.
The table separates three working decisions. The labels do not replace reviewing your platform; they give marketing, customer service and the person configuring flows a shared meaning when discussing reactivation.
| Decision | Main question | Avoid confusing these points |
|---|---|---|
| Recover purchasing | Is there a new need we can help with? | No recent purchase does not prove rejection of the brand |
| Recover engagement | Is the communication still relevant to this person? | Engagement does not equal a new order |
| Reduce or stop marketing | Does continued sending make sense with these signals? | Saving a label does not prove that messages have stopped |
Build the audience around the buying cycle
Review the catalogue and history before defining the group. Compare product families with similar logic: replenishment, accessories, seasonal buying or durable goods. One window for the entire store may combine situations too different for the same message.
As an educational example, imagine a store selling coffee machines and coffee. A machine buyer may need guidance or accessories, while a regular coffee buyer may be ready to replenish. Do not use the second group’s rhythm to classify the first as inactive. Segmentation is useful when it changes the conversation, rather than merely dividing the database.
Define how you will handle returns, unresolved issues, address changes and recent purchases arriving through another source. Not every signal will always be available. Document what is known and what falls outside your view so the team does not mistake an automated selection for a complete description of the customer.
Segmentation by behaviour and purchases makes these conditions explicit. Save a readable description beside the rule: who it includes, why and which message they will receive. If someone cannot explain the selection without opening several screens, simplify it before expanding it.
Give the customer a specific reason to return
The first message should reconnect with something recognisable: a category, a need or a previous relationship. “We miss you” may suit a brand’s voice, but does not explain what the person will find. Pair the tone with a proposal you can substantiate.
In the coffee example, a message could help choose another origin based on preferences the customer has shared or known purchases. For a machine buyer, a guide or compatible accessory may help more. Do not turn an assumption about taste into a claim: explain the options and let the person choose.
If you include an incentive, make its conditions clear and verify the destination. The customer needs to understand eligible products, how to apply it and any restrictions. Include its cost in the commercial decision. An order achieved through an offer does not by itself prove that repeating the offer across the audience is worthwhile.
Each later message needs to add something different: answer a question, present a relevant option or enable preference changes. If only the subject changes while the offer repeats, you may increase persistence without increasing usefulness. A retention strategy helps determine when another communication has a purpose and when to allow space.
Decide when the journey starts and ends
Write down entry, delay, re-entry and exit conditions before designing the emails. For each, identify the supporting data and what would happen if it arrived late. A recent purchase may change the message’s relevance. A new subscription or preference change may also call for a different conversation.
Coordinate winback with the post-purchase sequence. Someone who has just returned should not keep receiving an invitation that assumes a long absence. Check scheduled campaigns too: leaving one flow does not necessarily remove someone from all marketing sends.
You do not need one sequence that handles every imaginable exception. Start with an understandable audience and a journey the team can test. Add distinctions when content genuinely differs or there is a real risk of inconsistency. Complexity should respond to observed situations, rather than a desire to fill a diagram.
Keep a journey record with an owner and review date. Changes to the catalogue, promotions or subscription model may make the definition of inactivity unsuitable. A technically active rule may need editorial review even when it produces no visible errors.
Decide what happens without a response
Winback needs an ending. Before activation, agree what happens if the person does not respond: narrow the scope, review preferences where appropriate or stop including them in certain sends. The criterion needs to be understandable and applied in the systems that actually send.
Klaviyo distinguishes a sunset flow from the effective suppression of profiles. A property or label can select contacts, but should not be assumed to stop marketing by itself. Verify the mechanism and actual result in your account.
Likewise, deleting a record is not the same decision as managing eligibility. Before changing contact status, understand the effect on your channels and integrations. A deliverability review should cover how exclusions are maintained and how the same audience is prevented from being reintroduced without a clear reason.
Treat opens cautiously when assessing interest. Klaviyo’s winback documentation explains that Apple Mail Privacy Protection can produce inflated open rates. Combine signals and context instead of treating an isolated open as sufficient proof of recovery.
Test the cases that would change the decision
Create test contacts representing different histories: an old purchase of a durable item, frequent consumable purchases, a recent order and someone who has not responded to recent sends. Test the business interpretation as well as the email’s appearance.
Record the expected result before running each case. Then compare entry, planned messages, destination and exit. A test confirming only that an email arrived does not prove that the right customer was selected or that the sequence will stop when their situation changes.
Acceptance scenarios
- Different cycles: the same time without purchasing does not necessarily produce the same message in every category.
- Recent purchase: check whether the contact should leave or change journeys.
- Offer applied: the destination’s product and conditions match the email.
- Changed preferences: subsequent sends respect the new situation.
- No response at the end: the agreed action takes place beyond simply saving a label.
- Re-entry: new activity does not create incompatible simultaneous sequences.
- Exclusion preserved: another system or import does not restart sends that were meant to stop.
Assess recovery with a stable definition
Define recovery before reading the report. Depending on the purpose, it may mean a new purchase, a specific reply or updated preferences. Keep those signals separate rather than adding them together as equivalent commercial value.
Compare purchasing over similar observation periods and review where the audience came from. A campaign for customers with a short replenishment cycle cannot simply be compared with one targeting occasional buyers. The email marketing KPI guide explains denominators and the difference between attributed orders and conclusions about causality.
Consider the cost of obtaining the response: discounts, production, support and channel pressure. Higher revenue can coexist with an unsustainable incentive. The decision should consider the outcome that matters to the store and the conditions under which it was achieved.
A review may show that a group needs a better proposal, a delay needs adjustment or further follow-up should stop. Effective winback does not try to prove that every contact will return. It identifies where there is a useful reason to restart the relationship and where silence should be respected.
Sources and further reading
AI-assisted translation
Article by Dídac Anton. The English, German, Dutch and French versions were translated from Spanish with the help of AI.
Read the Spanish originalRecommended articles
Post-purchase email sequence
Connect the post-purchase experience to useful information, reviews and future purchases while respecting the real order status.
Ecommerce email flows
A practical guide to selecting, connecting and prioritising email flows by customer stage and available data.
Ecommerce email segmentation
Turn segmentation into useful rules for deciding what to send, to whom, when and why.




