MAILCRAFT
Home Features Pricing About Blog Contact Log in Get Started →
Email automation

Lifecycle Email Marketing: Mapping Automations to Each Customer Stage

Hands typing on a laptop showing a task board, planning email automations for each customer stage

Lifecycle email marketing comes down to one rule: every contact sits in exactly one stage, and that stage’s automation decides what they get. Do that and your welcome series and post-purchase flow stop tripping over each other. Running both separately right now? Black Friday is about to dump a pile of new signups and one-time buyers on your list, so connect them before it hits. Below you’ll find a stage map (entry trigger, exit condition, stage tag for each stage) and the rules that stop automations from colliding.

Why do separate automations end up mailing the same person twice?

Each automation picks its own entrants. None of them knows what the others are already sending. The textbook collision is someone who subscribes and buys on the same day. They land in the welcome series and the post-purchase sequence at once, and then a promo broadcast shows up on top. Three emails, one confused person.

You can shuffle send times all you like, but it won’t help, because this is a structural problem. The fix is one shared stage field that every automation reads and writes. Skipping it costs you, too: Gmail’s email sender guidelines ask you to send only mail people want, make unsubscribing easy and keep the spam rate reported in Postmaster Tools below 0.3%. Want to push complaints up fast? Run three overlapping sequences at the same person.

The lifecycle email marketing map: five stages, one tag each

It’s one table with five stages. Each row has an entry trigger, what to send, an exit condition and a stage tag. That’s it.

StageEntry triggerWhat to sendExit conditionStage tag
New subscriberSignupOnboarding email sequenceFirst purchase or end of sequencestage-new
First purchaseFirst order eventPost-purchase sequenceSecond order or the time window passesstage-first-buyer
Repeat customerSecond orderLoyalty and replenishment contentNo order or engagement within a set windowstage-repeat
LapsedInactivity thresholdShort re-engagement or permission passRe-confirmation moves them back; otherwise suppression or deletionstage-lapsed
UnsubscribedUnsubscribeNothingNone, final statestage-unsubscribed

For the first row, don’t stop at a single hello. Build welcome sequences that keep working after the opening message.

The second row behaves best as a post-purchase email sequence with its own end date. Open-ended post-purchase flows tend to drift into everything else (and that’s exactly the overlap we’re trying to kill).

Rules that keep customer lifecycle emails from colliding

Three rules carry most of the load. One stage per contact. The tag change is the exit. Promotions live on a separate layer.

  1. One stage tag at a time. A contact never holds two stage tags.
  2. The tag swap is the exit. Moving on means you remove the old tag and add the new one, and that removal fires the exit conditions for automations of the previous stage.
  3. Re-entry control. Decide per stage whether someone can go through it again. Otherwise a returning buyer gets dropped back into onboarding, which looks a bit silly.

Make the move to the next stage each automation’s goal. Opens don’t tell you much. A new subscriber reaching stage-first-buyer, though? That’s the sequence doing its job.

How to run one promotional calendar on top of the stages

Promo broadcasts come from one shared calendar that sits above the stages and filters by stage tag before every send. Hold back contacts in their first days of onboarding. Let the welcome series set the tone before Black Friday offers take over their inbox.

Offers can vary by tag. First buyers get a reason to place a second order. Repeat customers get loyalty perks. Lapsed and unsubscribed contacts get no campaigns at all. In practice, I’d build that exclusion as a saved segment, so nobody has to remember it before each send (because someone will forget).

Sorting the post-Black Friday wave into the right stage

When the holiday peak dies down, tag every new contact by what they actually did. Not by “send everyone everything”.

  • Signups without an order go to new subscriber.
  • Single holiday orders go to first purchase.
  • Existing customers who ordered again go to repeat.

Purchase events can come from the shop as a custom event or a tag set through the API, and bulk tag apply and remove clears the backlog after a CSV import. Then check one thing: does any contact carry two stage tags? If yes, fix it before the next send.

When the lapsed stage should end in deletion

The lapsed stage needs an end point. Either they re-confirm, or they get suppressed and deleted. Endless mailing isn’t an option. The Spamhaus guidelines for ESPs and large senders recommend a strong sunset policy and a permission pass for addresses that haven’t engaged in more than 12 months, suppressing anyone who doesn’t re-confirm.

And there’s a legal side. GDPR rules on data minimisation in Article 5(1)(c) and storage limitation in Article 5(1)(e) make it hard to justify keeping addresses you no longer use. So, honestly, deleting a contact instead of trying yet another reactivation is often the cleaner move.

Building the map in MailCraft

The map translates straight into tags, custom fields and automations triggered on signup, tag, link click, date or custom event. Each stage automation starts on its own stage tag. Goal tracking and re-entry control handle exits and repeats. Dynamic segmentation drives the broadcast exclusions. One note: automations are not part of the Starter plan.

A lifecycle marketing strategy holds up when stages, tags and the promo calendar share one source of truth. Build that first. Then lifecycle email marketing stops being a bunch of flows fighting over the same inbox and turns into a single path each contact walks once.

FAQ

Can a contact be in two lifecycle stages at once?

No. Each contact holds exactly one stage tag. Change the tag and the previous automation ends while the next one starts, and that’s what stops duplicate sends.

Should new Black Friday subscribers get holiday promotions right away?

Keep them out for the first days of onboarding so the welcome series gets a chance to introduce your shop. After that, the shared calendar picks them up by tag like everyone else.

How long should a contact stay in the lapsed stage?

Just long enough for one re-engagement email or permission pass. If they don’t confirm, suppress or delete them. Don’t keep mailing them forever.