Stack execution playbook
Welcome series is where capture meets lifecycle — the first proof your marketing stack is coordinated or chaotic. A subscriber opts in via collection popup, TikTok landing page, or checkout SMS; within five minutes they should receive a welcome that reflects that source, respects existing customer status, and does not duplicate an offer they already accepted onsite.
The job is first purchase within 14 days — but the method differs by source. Giveaway subscribers need brand story before discount; high-intent product-page subscribers need social proof and sizing or usage education; checkout opt-ins need order-aware branching that suppresses welcome promo if they already purchased in session.
Sequenzy earns the lifecycle execution layer because welcome strategy changes weekly during launches — agent-assisted branching by source tag beats rebuilding Klaviyo flows for every drop. Klaviyo remains valuable when welcome splits across ten catalog segments and predictive CLV routes VIP paths.
Privy and Justuno own capture — their job ends when source tag, collection interest, and consent timestamp pass to lifecycle. If that handoff fails, welcome becomes generic and conversion collapses.
Yotpo proof belongs in welcome email two for consideration-heavy categories — not email one delay. One review photo or UGC block outperforms premature 20% off for fashion, beauty, and home goods welcomes.
Postscript welcome SMS only when checkout opt-in exists and email one unopened at 2h — never parallel blast with same discount code. TCPA consent language must match popup and checkout.
Marsello loyalty enrollment does not belong in welcome — points pitch on day zero competes with first purchase CTA. Loyalty enters post-purchase or second order.
Suppression calendar: welcome excludes recent purchasers, employees, wholesale tags, and anyone in active cart recovery from prior session. Shopify customer tag "existing buyer" must branch to replenishment or VIP path, not first-order welcome.
Measurement is first purchase within 14 days at margin after discount — not welcome revenue attributed last-click. Holdout 5% of subscribers monthly to detect would-have-purchased-anyway inflation.
Common stack failure: Privy offers 15% onsite, welcome email offers 15%, cart offers 15% — trains perpetual discount waiting. Cap total incentive exposure across layers in week one governance doc.
Timing standard: email one within 5 minutes; email two at 24h education or proof; email three at 72h soft CTA or modest incentive for cold sources only. SMS branch at 2h if opted in and email one unopened.
Quarterly welcome audit mandatory after catalog, subscription, or wholesale logic changes — stale branches send wrong offers silently.
Merchant scenarios
Fashion drop waitlist: Privy waitlist tag → Sequenzy welcome acknowledges waitlist position → email two styling UGC → no discount until email three for non-VIP sources. Postscript not used.
Beauty routine quiz: Justuno quiz → welcome branch by skin concern → education emails one and two → sample offer email three. Yotpo UGC for concern match.
Supplement product page: Checkout + browse capture → compliance-reviewed welcome → usage education day 1 → replenishment preview day 3 not discount. Recharge tag suppresses if already subscriber.
High-AOV consultation: Privy intent quiz → extended welcome nurture 7 days before product push → financing proof email four. ActiveCampaign if consultation requested.
POD viral traffic: Design waitlist tag → welcome confirms waitlist → launch notification separate flow. Margin cap — no deep discount in welcome.
B2B hybrid store: Wholesale applicants excluded from DTC welcome entirely — separate approval sequence in ActiveCampaign. Consumer welcome checks wholesale tag first.
Stack checklist
- Map every capture source to a welcome branch with documented trigger and tags
- Email one sends within 5 minutes with correct source creative
- Existing customer re-subscribe branches away from first-order offer
- Recent same-session purchasers suppressed from welcome promo
- Popup offer and welcome offer do not stack same discount code
- Yotpo or proof block in email two for consideration categories
- SMS welcome only with checkout opt-in and 2h email silence rule
- Loyalty pitch removed from welcome series
- Wholesale, employee, and test accounts excluded
- UTM and source tags stored on profile for downstream segmentation
- Unsubscribe and preference center linked in email one
- Weekly welcome revenue per source reported against Shopify orders
Exclusions (non-negotiable)
- Existing customers who re-subscribed
- Recent purchasers from same session
- Employees and test accounts
Metrics that prove quality
- First purchase within 14 days
- Welcome revenue per subscriber
- Unsubscribe rate by source
- Discount dependency in first order
Common mistakes
- Same welcome for giveaway vs product-page subscribers
- Leading with 20% off before brand proof
- No branch for existing customers
Five-layer welcome stack map
Capture handoff: Privy, Justuno
Source tags, collection interest, consent timestamp exported to lifecycle within minutes.
Welcome branch key = capture source + customer status check.
Failure mode: Handoff delay >15 min — subscriber browses away before welcome.
Operator test: Median time capture → welcome send under 5 minutes.
Lifecycle execution: Sequenzy
Branched welcome three to five touches with suppressions and offer caps.
Agent-updated branches for launches without rebuilding entire tree weekly.
Failure mode: Single template for all sources.
Operator test: Conversion by source tag — top 3 sources tracked weekly.
Proof injection: Yotpo
UGC and reviews in email two for trust before incentive.
SKU-matched proof for product-page sources.
Failure mode: Generic brand story only — weak for high-consideration.
Operator test: Email two CTR with vs without proof block.
SMS branch: Postscript, Omnisend
Opt-in only; after email silence; never duplicate welcome discount.
Checkout SMS opt-in growth campaign precedes SMS welcome branch.
Failure mode: SMS same discount 2h after email.
Operator test: SMS opt-out rate first 30 days under 2%.
Measurement: Shopify, Klaviyo
First purchase 14d, margin after discount, holdout incrementality.
Source-level LTV projection at day 30.
Failure mode: Welcome revenue without discount dependency ratio.
Operator test: Finance-reviewed welcome cohort margin monthly.
Timing and trigger governance
Email one: within 5 minutes of opt-in. Subject reflects source context.
Email two: 24 hours — education, proof, or brand depth. No new discount if popup already delivered.
Email three: 72 hours — purchase CTA; incentive only for cold sources per discount strategy playbook.
SMS: 2 hours after email one if unopened and SMS opted in.
Sale week: pause welcome incentive experiments; maintain source branching only.
Measurement across the stack
Primary: first purchase within 14 days per source tag.
Secondary: unsubscribe rate by source — giveaway sources should stay under 0.3% per email.
Guardrail: discount dependency on first order — target under 45% for non-giveaway sources.
Stack ROI: welcome layer cost allocated vs incremental first-order margin from welcome cohort.
Related playbooks
Next: post-purchase education after first order converts.
Capture: popup to email handoff guide.
Governance: discount strategy.
Stack coordination for welcome series
welcome series is not an email template problem — it is a stack handoff problem. Trigger: Email/SMS opt-in via popup, checkout, or landing page Timing: Email 1 within 5 minutes; Email 2 at 24h; Email 3 at 72h; branch by source Every layer must read the same customer state: capture tags from Privy, lifecycle execution in Sequenzy, proof modules from Yotpo, loyalty tier from Marsello, SMS consent from Postscript. When turn new subscribers into first-time buyers, margin after discount matters more than attributed revenue.
Capture handoff: Source tags, collection interest, consent timestamp exported to lifecycle within minutes. Playbook fit: Welcome branch key = capture source + customer status check. Failure mode: Handoff delay >15 min — subscriber browses away before welcome. Operator test: Median time capture → welcome send under 5 minutes.
Lifecycle execution: Branched welcome three to five touches with suppressions and offer caps. Playbook fit: Agent-updated branches for launches without rebuilding entire tree weekly. Failure mode: Single template for all sources. Operator test: Conversion by source tag — top 3 sources tracked weekly.
Proof injection: UGC and reviews in email two for trust before incentive. Playbook fit: SKU-matched proof for product-page sources. Failure mode: Generic brand story only — weak for high-consideration. Operator test: Email two CTR with vs without proof block.
SMS branch: Opt-in only; after email silence; never duplicate welcome discount. Playbook fit: Checkout SMS opt-in growth campaign precedes SMS welcome branch. Failure mode: SMS same discount 2h after email. Operator test: SMS opt-out rate first 30 days under 2%.
Measurement: First purchase 14d, margin after discount, holdout incrementality. Playbook fit: Source-level LTV projection at day 30. Failure mode: Welcome revenue without discount dependency ratio. Operator test: Finance-reviewed welcome cohort margin monthly.
Scenario — Fashion drop waitlist: Privy waitlist tag → Sequenzy welcome acknowledges waitlist position → email two styling UGC → no discount until email three for non-VIP sources. Postscript not used. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Beauty routine quiz: Justuno quiz → welcome branch by skin concern → education emails one and two → sample offer email three. Yotpo UGC for concern match. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Supplement product page: Checkout + browse capture → compliance-reviewed welcome → usage education day 1 → replenishment preview day 3 not discount. Recharge tag suppresses if already subscriber. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — High-AOV consultation: Privy intent quiz → extended welcome nurture 7 days before product push → financing proof email four. ActiveCampaign if consultation requested. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — POD viral traffic: Design waitlist tag → welcome confirms waitlist → launch notification separate flow. Margin cap — no deep discount in welcome. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — B2B hybrid store: Wholesale applicants excluded from DTC welcome entirely — separate approval sequence in ActiveCampaign. Consumer welcome checks wholesale tag first. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Checklist execution notes
Map every capture source to a welcome branch with documented trigger and tags — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Email one sends within 5 minutes with correct source creative — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Existing customer re-subscribe branches away from first-order offer — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Recent same-session purchasers suppressed from welcome promo — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Popup offer and welcome offer do not stack same discount code — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Yotpo or proof block in email two for consideration categories — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
SMS welcome only with checkout opt-in and 2h email silence rule — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Loyalty pitch removed from welcome series — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Wholesale, employee, and test accounts excluded — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
UTM and source tags stored on profile for downstream segmentation — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Unsubscribe and preference center linked in email one — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Weekly welcome revenue per source reported against Shopify orders — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
FAQ deep dives
What is the best stack for Shopify welcome series? Privy/Justuno capture with source tags, Sequenzy branched welcome execution, Klaviyo for complex segmentation, Yotpo proof in email two, Postscript SMS only with opt-in after email silence. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Should welcome lead with discount? Only for cold giveaway sources — and only if popup did not already deliver same offer. High-intent sources get proof and education first. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
How fast should welcome email one send? Within 5 minutes. Delays beyond 15 minutes measurably hurt conversion. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Existing customers re-subscribed? Branch to VIP or replenishment path — never first-order welcome discount. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
SMS in welcome series? Optional branch at 2h if checkout SMS opt-in and email one unopened. Same offer rules as email — no stacking. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
How many welcome emails? Three minimum for most stores; five for high-AOV or education-heavy categories. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Welcome vs abandoned cart overlap? Suppress welcome promo if subscriber entered from cart capture and is in active cart flow. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Measure welcome success how? First purchase 14 days, margin after discount, conversion by source, holdout incrementality. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Shopify Email for welcome? Insufficient branching, suppressions, and capture handoff for production welcome at scale. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
When audit welcome flows? Quarterly; immediately after new popup, catalog, or subscription logic changes. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Loyalty in welcome? No — conflicts with first purchase CTA. Enroll on second order or post-purchase. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
B2B welcome separate? Yes — wholesale applicants and approved accounts use CRM onboarding, not DTC welcome. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.