25 parts · 1 checkpoint · 3 free / 22 member parts →
Series start
Fix the Email series case spine first
This series uses one ordinary pet travel bottle store as its case: the 20oz blue and 32oz gray versions are different SKUs, and a customer can move through signup, browse, cart, started checkout, order, delivery and use, replenishment, or silence. Every lesson defines the trigger, customer state, and no-send line before reading revenue and list health. The case is teaching data, not public proof of a brand or platform result.
Note Do these three things today
- Draw five states: subscribed, viewed, added to cart, started checkout, purchased. 2. For each, write entry, exit, and suppression conditions. 3. Pick one path, tie it to order and profit evidence, then decide whether to turn it on.
How to build a Shopify email lifecycle map: map customer states before you prioritize flows
Put customer state, event, marketing consent, entry, exit, and suppression on one map, then bind each path to order, list, and profit evidence. The map is a decision boundary, not permission to send automatically.
There is no universal order. Read conflict risk, customer state, exit rules, and evidence availability together, then repair the path most likely to duplicate or misroute a send.
Write the event, eligibility and consent, exit, recent-touch, and duplicate-suppression checks for every rule, plus the support, refund, and inventory boundaries that pause a sales path.
No. Reconcile attributed revenue with Shopify orders, refunds, margin, repeat purchase, unsubscribes, and complaints; revenue inside an attribution window is not standalone proof of incrementality or profit.
This lesson answers
Lifecycle email map and metric review rules
This email lifecycle review splits lifecycle email into three layers: where the customer is, what they should receive, and when not to send. Do not start with which email earned more; define entry, exit, suppression, then read revenue, order quality, and list health together.
- Stage boundary: where the customer is now.
- Entry / exit / suppression: who may enter and who must stop.
- Revenue + list health: whether the stage keeps the money it appears to earn.
The stage jobs and boundaries are laid out in the state table below; do not let a flow name replace the decision.
Define the reviewable unit first
Do not treat a flow as the work unit. Treat one customer-state decision as the unit
A flow name cannot explain why a person should receive an email today. The reviewable unit is a customer-state record: one customer ID, one timezone, one SKU, one event, current marketing permission, most recent touch, and any purchase or support state. Put those fields on the map row so “send this” becomes a checkable decision.
Try it first
Lifecycle lead + merchandising lead
- Symptom
- A new subscriber views a pet travel bottle and receives brand intro, abandonment reminder, and campaign promo within 48 hours.
- Fix rule
- Set priority: keep the higher-intent path, but pause or reduce later welcome promo messages.
Lifecycle lead + support lead
- Symptom
- The buyer gets a second-purchase promo before delivery; any logistics or product issue can amplify refunds and negative reviews.
- Fix rule
- Shipment, delivery, support exception, and refund states must suppress repeat-purchase promos.
Lifecycle lead + data lead
- Symptom
- Long-silent users keep receiving heavy discounts; occasional orders come with worse unsubscribes, complaints, and inbox quality.
- Fix rule
- Turn win-back into a clear test: re-engage returns to lifecycle; no engagement enters suppression or cleanup.
Note Open case: a flow is a state rule
A flow is not a template name. It is who receives what, in which state: subscribed, viewed, added to cart, started checkout, ordered. Draw the states first, then pick the template.
Pro lesson · free with an account until 2027-04-26 · Parts 3-24 · 22 parts
Members: full exercises and records
This part includes
- Turn four lifecycle stages into a working map
- Write entry, exit, and suppression rules for every flow
- Review revenue with order quality and list health
1 self-check question
An account is free; sign in to read this part.
Checking your membership…
FAQ
- Which Shopify email flow should I build first: welcome, abandonment, or win-back?
Order by the customer journey: subscribers into welcome, viewers into browse abandonment, cart or checkout starters into recovery, buyers into post-purchase. The first map states who receives it, when, why not, and what result proves progress.
- Which customer states should the trigger table separate first?
Separate signup, browse, cart, checkout, purchase, review, repeat, and win-back first. This changes the question from "should we send an email" to "what state is this person in, which flow fits, and which flow must step aside." That is the beginner mistake this email lifecycle review is meant to prevent.
- Can welcome flow and abandoned cart flow conflict with each other?
Yes. If a new subscriber adds a 20oz pet travel bottle to cart within 24 hours, their shopping intent is stronger than a generic welcome story. Cart recovery should take priority. Welcome brand education or first-order discounts should pause or become supporting proof, otherwise the customer receives two messages fighting for attention.
Lifecycle map next steps
After the map is clear, connect the first-purchase path to the welcome flow.
The lifecycle map is a decision frame, not permission to send automatically; make stage, entry, exit, and suppression rules concrete in the flow next.
Return to the Email Lifecycle Hub
Sources
Klaviyo attribution explains how the platform credits orders inside a reporting window; it does not prove incremental profit on its own. Read it with Shopify refunds, discounts, margin, repeat behavior, and list health. Deliverability and list health are not only later reports; they are send-eligibility gates for every flow.
Sources: 7Last checked
Klaviyo Help Center: Getting started with flows (opens in a new tab)Checked
Supports
Use it to understand triggers, filters, step status, and automation analytics.
Klaviyo Help Center: Flow Triggers and Filters (opens in a new tab)Checked
Supports
Use it to separate entry rules, trigger filters, and send-time profile filters.
Klaviyo Help Center (opens in a new tab)Checked
Supports
Use it to separate recipient, message, link, and attributed-revenue readings instead of treating platform credit as incremental profit.
Shopify Help Center: Migrate abandoned checkout (opens in a new tab)Checked
Supports
Use it for sending conditions, undelivered states, and Shopify automation boundaries.
Shopify Help Center: Shopify email analytics (opens in a new tab)Checked
Supports
Use it to connect email readings back to Shopify orders, sales, and unsubscribe facts.
FTC: Can spam act compliance guide business (opens in a new tab)Checked
Supports
Use it for opt-out, sender identity, and subject-line promise boundaries.
arXiv: 1703.02596 (opens in a new tab)Checked
Supports
Method reminder from “Customer Lifetime Value Prediction Using Embeddings”: separate feature history from the target / label window, then use time-split historical backtesting and calibration. This bounds offline segmentation evaluation; it is not a randomized intervention or an Ecomwith result.