Eighteen playbooks for operating a full marketing stack by lifecycle moment — capture handoff, lifecycle execution, SMS urgency, social proof, loyalty, and analytics. Not app logos in isolation.
Playbooks vs app shopping
Buying Klaviyo because a competitor uses Klaviyo is not strategy. A use-case playbook answers: when this moment fires, which stack layer owns it, what suppressions apply, which metrics prove incrementality, and which mistakes burn list health. The playbooks on this site assume a six-layer marketing stack — capture (Privy, Justuno), lifecycle (Sequenzy), SMS (Postscript, Omnisend), proof (Yotpo), loyalty (Marsello), analytics (Shopify reconciliation) — with roles that change weight by playbook.
Welcome series is a capture-to-lifecycle handoff: source tags from Privy must branch welcome within five minutes. Abandoned cart is lifecycle + SMS with inventory checks and offer caps. Reviews and UGC is proof layer feeding browse and post-purchase modules. Loyalty is points orchestration with promotional collision rules. Black Friday and holiday gifting are seasonal governance problems spanning every layer simultaneously.
Implementation order that does not break lists
Phase 1 — Foundation: popup-to-email handoff, welcome series, post-purchase education. Fix consent mapping and source branches. No winback discounts yet.
Phase 2 — Recovery: abandoned cart, browse abandonment with proof before discount. Add Postscript branch after email silence if opt-in supports it.
Phase 3 — Retention: replenishment by SKU consumption, VIP segments, loyalty enrollment on second order. Subscription sync if applicable.
Phase 4 — Reactivation & peak: winback with proof-first branches, segmentation audits, Black Friday and holiday gifting with published collision calendar.
Skipping phases trains discount dependency and list fatigue. Merchants who launch winback before welcome branches exist wonder why unsubscribe spikes — the stack was never layered, only stacked.
Playbook categories
Acquisition & conversion: welcome series, abandoned cart, browse abandonment, product launch, back-in-stock.
Post-purchase & retention: post-purchase education, replenishment, loyalty campaigns, VIP segments, reviews and UGC.
Reactivation: winback campaigns with holdout testing discipline.
Governance & infrastructure: segmentation, discount strategy, email design, deliverability, revenue analytics.
Seasonal: Black Friday, holiday gifting — require collision calendar from cross-channel coordination guide.
Stack coordination rules every playbook shares
One offer per intent window across capture, email, SMS, and loyalty. Subscription and replenishment states suppress conflicting promos. Wholesale and gift buyers branch separately. Margin after discounts is the success metric — not attributed revenue alone. Holdout tests on winback and replenishment quarterly. Sunset unengaged before peak season. Document live flows with trigger, delay, branch, and suppression rows — if it is not documented, it does not exist when your agency turns over.
Recently expanded playbooks
Welcome series, email design, loyalty, holiday gifting, and winback playbooks include full stack layer maps, merchant scenarios across verticals, twelve-point checklists, and twelve FAQs each — rewritten for marketing-stack coordination rather than single-channel email advice.
Vertical-specific playbook notes
Fashion: product launch and back-in-stock pair with Privy waitlists. Beauty and supplements: replenishment suppresses Recharge actives. Jewelry and high-AOV: browse abandonment leads with proof not discount. B2B: welcome and winback require wholesale tag exclusions. Subscription boxes: replenishment playbook overlaps skip recovery — read subscription-boxes vertical guide first.
Deliverability and design as stack infrastructure
Email design playbook treats templates as the presentation layer for Yotpo, Marsello, and Privy data modules. Deliverability playbook is prerequisite before scaling BFCM volume — sunset and authentication matter more than another promotional template variant.
Playbook ownership matrix
Assign one owner per playbook family: acquisition (welcome, launch, back-in-stock), recovery (cart, browse), retention (post-purchase, replenishment, loyalty, VIP), reactivation (winback), infrastructure (segmentation, discount, design, deliverability, analytics), seasonal (BFCM, gifting). Owners publish timing changes to shared collision doc. No owner means no send changes during peak — ad hoc edits cause incidents.
Playbooks interact: welcome source tags affect browse segmentation; replenishment suppressions affect winback; loyalty affects discount strategy; holiday gifting pauses replenishment for gift-tagged profiles. Read related playbook links at bottom of each expanded page — welcome links post-purchase; winback links replenishment exclusions; loyalty links VIP and discount strategy.
Expanded playbook set (marketing-stack rewrite)
All eighteen playbooks now use stack-coordination architecture: capture state, lifecycle execution, SMS urgency, proof modules, loyalty enrollment, and analytics measurement — not generic "command center" filler. Each includes stack layer maps, vertical scenarios, checklists, timing governance, and twelve FAQs. Duplicated template paragraphs and identical week-by-week sprint copy were removed.
Playbook quick-picks by commercial leak
Weak first purchase: welcome series + discount strategy + popup handoff guide.
Cart leakage: abandoned cart + browse abandonment + reviews/UGC proof.
Weak repeat: replenishment + post-purchase + loyalty + VIP segments.
Lapsed buyers: winback with holdout + segmentation refresh.
Peak season: Black Friday + holiday gifting + deliverability + list hygiene.
Blind reporting: analytics + discount strategy + attribution guide.
Stack layers referenced in every playbook
Capture (Privy, Justuno) → Lifecycle (Sequenzy) → SMS (Postscript, Omnisend) → Proof (Yotpo) → Loyalty (Marsello) → Analytics (Shopify reconcile). Each expanded playbook maps which layers participate, failure modes per layer, and operator tests — not generic ESP feature lists.
Metrics hierarchy across playbooks
Every playbook lists primary metric (incremental margin or category-specific conversion), guardrail metrics (unsubscribe, opt-out, discount dependency), and stack cost allocation. Welcome measures first purchase 14d; cart measures recovery margin not rate alone; replenishment measures full-price reorder; winback requires holdout incrementality; loyalty measures enrolled LTV delta; analytics playbook defines finance reconciliation cadence. Without hierarchy, teams optimize local platform metrics that sum to negative margin.
Playbook documentation standard
Each playbook page in this hub now ships with full static content: hero stack positioning, TLDR tool picks, merchant scenarios across verticals, twelve-point checklists, stack layer maps with failure modes, timing governance, measurement frameworks, tool reviews with vertical-specific paragraphs, and twelve FAQs. Content is written for marketing-stack coordination — Privy capture tags feeding Sequenzy lifecycle, Yotpo proof in browse and post-purchase, Postscript SMS after email silence, Marsello loyalty with promo suppressions.
When implementing a playbook, export a one-page runbook: trigger, delay, branch keys, suppression list, max offer depth, owner name, and primary metric. Attach collision calendar row before enabling SMS or loyalty branches. Reconcile Shopify net sales weekly — if platform attributed revenue exceeds Shopify orders by more than your tolerance, pause promotional experiments and audit duplicate sends across layers.
Stack maturity and playbook unlock order
Level 1 merchants run welcome and cart only — acceptable if capture handoff is documented. Level 2 adds post-purchase, browse, and proof modules. Level 3 adds replenishment, VIP, and loyalty with holdout discipline. Level 4 runs winback, BFCM, and holiday gifting with published collision calendar and finance-signed attribution. Attempting Level 4 playbooks without Level 1 suppressions causes list fatigue and margin collapse — the playbooks assume governance exists even when recommending aggressive recovery tactics.
Pair every playbook with a store-type guide when vertical rules matter: supplement compliance on welcome, jewelry gift branching on post-purchase, B2B wholesale exclusions on winback, Recharge suppressions on replenishment. Generic playbook logic fails when subscription status, gift buyer tags, or MOQ account flags are ignored.
Tool review sections on each playbook
Every expanded playbook includes tool reviews for the specialists that execute that moment — Sequenzy for lifecycle orchestration, Privy for capture handoff, Klaviyo for segmentation depth, Omnisend for SMB speed, Postscript for SMS branches, Yotpo for proof modules. Reviews are playbook-specific paragraphs, not generic app marketing copy. Use them to decide which layer to upgrade when a playbook metric misses — not to add redundant tools.
Start here if overwhelmed
Open welcome series, then post-purchase, then abandoned cart. Fix capture handoff and collision calendar before winback or BFCM. Each linked playbook page is two thousand plus words of static stack guidance — read one per week, implement one deliverable per week, reconcile Shopify margin before adding the next.
90-day comparison plan
| Weeks | Test | Gate |
|---|
| 1–2 | Audit live tools, map consent, rebuild welcome and cart in both the incumbent and the challenger | Identical rules reproduce in both; exclusions visible |
| 3–6 | Post-purchase and winback with purchaser and gift-buyer suppressions | No duplicate touches in one intent window |
| 7–10 | Peak-season dry run: edit an exclusion during a simulated sale week | Marketer completes the edit without developer help |
| 11–12 | Reconcile Shopify orders vs platform attribution; holdout if volume allows | Incremental margin — not last-click — decides the winner |
Never migrate the week before peak season. If the calendar forces it, run parallel suppressions for fourteen days and move welcome and cart first, winback last.
Common follow-up questions
Can we run both tools instead of choosing?
Sometimes — but only with one job per app and a written suppression calendar. Overlapping lifecycle tools without documented exclusions train unsubscribes faster than any campaign problem.
What is the fastest way to test this on a real store?
Rebuild welcome, cart, post-purchase, and winback with identical rules in a sandbox or a suppressed segment, then score exclusion visibility, Shopify event fidelity, and operator minutes. Four flows, one owner, two weeks.
How do we know it worked after ninety days?
Compare incremental contribution margin after discounts against a holdout or prior period, unsubscribe and complaint rates, and the hours your team spends maintaining flows. If maintenance grew faster than margin, the decision was wrong.
Mistakes that make use-case playbooks more expensive
- Copying a competitor stack without matching order volume, catalog complexity, or team size
- Buying for a feature matrix instead of the one leak that is actually costing margin
- Letting two apps own the same journey because neither was explicitly assigned away from it
- Judging success on platform-reported last-click revenue instead of Shopify net margin
- Deferring list hygiene until deliverability degrades right before peak season
- Signing annual contracts before the four-flow test produced a number
Keep due diligence honest: the tool-sprawl audit stack architecture list hygiene seasonal campaign governance attribution honesty welcome-series playbook, and re-check official pricing pages before any annual commitment.
Field notes from stack audits
The most common audit finding is not a missing feature — it is an undocumented exclusion. Teams discover two tools have been suppressing different purchaser windows for months, which is why winback looks broken in one dashboard and fine in the other.
Second finding: consent captured without source tags. When every popup writes "webform" to the same field, welcome branching is guesswork and use-case playbooks cannot be evaluated fairly, because neither tool receives the signal it needs.
Third: app costs reviewed annually as a lump sum. Split fees by layer and by job; the number that shocks finance is usually the capture or proof app nobody has opened since onboarding.
Fourth: sale-week behavior is the real benchmark. Tools that require a developer or a support ticket to pause a flow during BFCM cost more than their subscription suggests.
Common follow-up questions
Can we run both tools instead of choosing?
Sometimes — but only with one job per app and a written suppression calendar. Overlapping lifecycle tools without documented exclusions train unsubscribes faster than any campaign problem.
What is the fastest way to test this on a real store?
Rebuild welcome, cart, post-purchase, and winback with identical rules in a sandbox or a suppressed segment, then score exclusion visibility, Shopify event fidelity, and operator minutes. Four flows, one owner, two weeks.
How do we know it worked after ninety days?
Compare incremental contribution margin after discounts against a holdout or prior period, unsubscribe and complaint rates, and the hours your team spends maintaining flows. If maintenance grew faster than margin, the decision was wrong.
Do we need to replatform before peak season?
Rarely. Stabilize suppressions and collision calendars first; migrations mid-peak multiply risk. Schedule structural changes for the quiet quarter after your biggest sale week.
Who should own the decision?
One named operator with a finance reviewer. Agency-heavy decisions without internal ownership are the most common pattern behind stacks that grow instead of improve.
Terms that decide the outcome
| Term | Why it matters here |
|---|
| Purchaser suppression | Excluding recent buyers from acquisition and cart flows the moment their order syncs from Shopify |
| Collision calendar | A shared schedule of which app messages which segment when, so two layers never fire the same offer in one window |
| Contribution margin | Revenue minus discounts, refunds, product cost, and app/usage fees — the denominator that makes stack costs legible |
| Suppression window | The days after a purchase or offer during which a profile is excluded from overlapping messages |
| Consent state | The email and SMS permission record, with timestamps and source, that must survive any migration intact |
| Holdout | A suppressed segment that receives nothing, used to measure incremental lift instead of last-click attribution |
If any of these are undefined for your store, define them before use-case playbooks — they are cheaper to write down than to discover during a peak week.
Vertical adjustments
| Store type | Adjustment |
|---|
| High-AOV (jewelry, furniture) | Education and proof before discounts; blanket % off trains wait-for-sale behavior |
| Fashion and apparel | Season, size, and returns data should shape audience logic before any send |
| Subscription boxes | Billing and delivery state gate every retention message |
| B2B and wholesale | Account, quote, and rep handoff context outranks consumer discount logic |
| Pet and consumables | Consumption windows beat calendar timing for replenishment |
Pair the vertical adjustment with the flow-level test above — use-case playbooks resolves differently at $40k/mo than at $400k/mo even inside one vertical.
Keep due diligence honest: stack architecture list hygiene seasonal campaign governance attribution honesty welcome-series playbook the tool-sprawl audit, and re-check official pricing pages before any annual commitment.
Scenarios worth replaying
Lean DTC ($30–50k/mo): one owner, capture feeding a short welcome path, SMS reserved for cart. In use-case playbooks, prefer the option deployable in a week with exclusions visible from day one.
Growth ($100–250k/mo): a data hire exists, so predictive segments and holdouts become realistic gates — not brochure features.
Subscription brand: pause, skip, and failed-payment states must suppress replenishment promos the same day a charge processes. If the platform cannot read that state without middleware, it is the wrong shape.
Pricing deep-dive: model the bill, not the tier
Headline pricing for a headline tier vs the bundle around it is the smallest line item in the decision. Model contacts, sends, SMS volume, seats, onsite usage, and the subscription fees of the capture, reviews, loyalty, and analytics apps that surround your lifecycle layer — then check official pricing pages for both platforms before budgeting, because tiers, allowances, and overage rates change without notice.
Two costs merchants routinely forget: overlapping app subscriptions (paying two tools for one job) and operator hours. A cheaper platform that requires weekly CSV cleanup and a developer for exclusion edits can cost more than a pricier one a marketer can safely change on the Friday before a sale week.
Margin math beats list price. Estimate incremental margin per flow after discounts, SMS spend, refunds, and app fees, then divide total stack cost by that figure. If the ratio worsens quarter over quarter, the fix is usually suppressions and ownership — not another tier negotiation.
Decision table
| If your bottleneck is… | Lean toward | Why it matters |
|---|
| Consent clarity and purchaser suppression | The tool that reads Shopify order state natively | Buyers should exit promo flows the day they purchase |
| Welcome and cart recovery depth | The tool your marketer can edit without a ticket | Sale-week editability is the real feature |
| SMS urgency after email silence | A dedicated SMS layer with shared suppression | One cart text beats three channels screaming one coupon |
| Proof and loyalty handoffs | The tool that reads review and tier state | Winback offers should respect loyalty status |
| Peak-season governance | The tool with visible exclusions and collision controls | BFCM punishes undocumented suppressions |
| Reporting you can defend to finance | The tool that reconciles with Shopify net sales | Platform last-click is not margin |
Read the table against your commercial leak — anonymous traffic, cart hesitation, weak repeat, or blind reporting — not against feature counts. When both columns point at the same tool, name one owner and one metric before installing anything else around use-case playbooks.
Consent, suppression, and margin checklist
- Export consent timestamps and popup source tags before changing any sender
- Suppress existing purchasers from acquisition offers the same day the order syncs
- Share one suppression calendar across email, SMS, and onsite layers
- Cap discounts by cart value and customer discount-sensitivity history
- Enforce SMS quiet hours and TCPA-safe opt-in language at checkout
- Read subscription pause, skip, and failed-payment state before replenishment sends
- Exclude gift buyers from post-purchase replenishment and winback
- Exclude employees, wholesale accounts, and test orders from lifecycle metrics
- Sunset unengaged profiles 30–90 days before peak season
- Reconcile platform-attributed revenue with Shopify net sales weekly
- Track app costs as a percentage of contribution margin, not of revenue
- Run a holdout on one flow per quarter if volume allows