Guides for operators, not tool tourists
App reviews answer "what does this tool do?" Use-case playbooks answer "how do I run welcome or winback?" Guides answer "how do I keep six tools from emailing the same person three offers on Tuesday?" That is stack governance — the unglamorous work that separates incremental margin from dashboard theater.
Merchants at $80k–$500k/mo often have Privy, Klaviyo or Sequenzy, Postscript, Yotpo, and maybe Marsello installed simultaneously. None failed on features. They failed on ownership: no collision calendar, no weekly Shopify reconciliation, no documented suppression between replenishment and winback. Guides fix the coordination layer assumptions the rest of the site builds on.
Reading order for new stack owners
1. Stack architecture — assign capture, lifecycle, SMS, proof, loyalty, analytics layers with named owners.
2. Popup to email handoff — source tags and consent timestamps into lifecycle within five minutes.
3. Cross-channel coordination — collision calendar template, one offer per intent window.
4. Attribution — incremental margin method finance will sign.
5. List hygiene — sunset rules before peak season volume.
Before BFCM: seasonal campaign governance. Before hiring agency: agency vs in-house ownership. When invoice list grows: tool sprawl remediation. When launching loyalty: loyalty integration with promotional suppressions.
Guide summaries
Stack architecture: six-layer model, owner matrix, week-one audit checklist.
Popup to email handoff: Privy/Justuno → Sequenzy/Klaviyo tag schema, consent mapping, failure modes.
Loyalty integration: Marsello/Yotpo with lifecycle — enrollment timing, expiry, promo collisions.
Reviews and UGC in the stack: Yotpo modules in browse, cart, post-purchase templates — not widgets only.
Marketing attribution: holdout tests, margin lines, Shopify as source of truth.
Tool sprawl remediation: overlap audit, retire vs integrate decisions.
Agency vs in-house: what must stay internal when outsourcing creative or strategy.
Seasonal campaign governance: BFCM collision rows, VIP early access sequencing, post-peak deliverability.
Cross-channel coordination: email + SMS + push + onsite without duplicate offers.
List hygiene: sunset, re-engagement vs winback discount, Gmail/Yahoo requirements.
Pair guides with vertical and playbook pages
After reading stack architecture, open your store-type guide for category-specific layer weights. Execute with use-case playbooks. Resolve tool choices on battlecards. Migration paths live in alternatives hub.
Operator checklist before peak season
Six weeks before BFCM: complete list hygiene sunset for unengaged 120+ day profiles. Four weeks before: publish collision calendar with rows for popup, welcome, cart, SMS, loyalty, winback, and promotional campaigns — each row names owner and max offer depth. Two weeks before: freeze segment logic changes; test shipping deadline dynamic content if Q4 gifting matters. One week before: deliverability spot-check domain authentication; pause non-essential A/B tests.
Post-peak: deliverability audit, Shopify margin reconciliation, document failed collision rows, schedule winback only after holdout design.
Finance-readable attribution
Attribution guide defines incremental margin with holdout cohorts. Email, SMS, popup, loyalty report separately — summing platform dashboards over-counts. Weekly Shopify net sales vs platform claims within agreed tolerance or trigger stack audit.
Guide maintenance cadence
Quarterly: tool sprawl audit, list hygiene review, attribution reconciliation with finance. Before peak: seasonal governance and cross-channel coordination refresh. After platform migration: popup handoff and loyalty integration re-read. After hiring agency: agency vs in-house guide — define retained internal ownership of segments and collision calendar regardless of vendor.
Guides are living references — when Shopify changes checkout extensibility, SMS regulations shift, or Gmail requirements update, list hygiene and cross-channel guides take precedence over new feature adoption.
Who on your team reads which guide
Growth lead: stack architecture, seasonal governance, cross-channel coordination, attribution. Email/lifecycle operator: popup handoff, loyalty integration, review-ugc, list hygiene. Founder at small team: all ten in order. Agency partner: agency vs in-house plus stack architecture — retained internal ownership non-negotiable. Finance: attribution guide monthly review with growth lead.
Common guide mistakes
Reading seasonal governance after BFCM starts. Implementing loyalty before collision calendar exists. Trusting agency attribution without Shopify reconcile. Adding SMS before checkout opt-in baseline measured. Skipping popup handoff while rebuilding welcome in new ESP.
Documentation deliverables each guide enables
Stack architecture → layer owner matrix. Popup handoff → tag schema doc. Cross-channel coordination → collision calendar template. Attribution → finance metric definitions. List hygiene → sunset policy. Seasonal governance → peak week row template. Tool sprawl → overlap audit checklist.
Stack maturity model
Level 0: single ESP, no capture tags, no reconciliation. Level 1: capture + lifecycle with documented welcome branches. Level 2: collision calendar, SMS layer, proof in templates. Level 3: loyalty with promo suppressions, holdout testing, finance-signed attribution. Level 4: vertical-optimized stack per store-type guide with quarterly audits. Most merchants overestimate level — audit honestly before peak season spend increases.
Operator roles for guide implementation
Growth lead owns collision calendar and attribution definitions. Lifecycle operator owns flow documentation and suppression rules. Capture owner owns Privy/Justuno tag schema. SMS owner owns Postscript quiet hours and frequency caps. Finance co-owns weekly Shopify reconciliation. Agency partners execute creative but retained internal ownership of segment logic is non-negotiable per agency vs in-house guide.
When to read which guide
Pre-launch stack: stack architecture → popup handoff → list hygiene. Pre-BFCM: seasonal governance → cross-channel coordination → list hygiene again. Post-migration ESP: popup handoff → attribution re-baseline. Adding loyalty: loyalty integration before Marsello install. Tool invoice growing: tool sprawl remediation. Hiring agency: agency vs in-house before contract signature.
Guides vs use-cases vs vertical pages
Guides are category-agnostic governance. Use-case playbooks execute one lifecycle moment (cart, welcome, winback) with stack layer maps. Store-type pages at /for apply six-layer architecture to fashion, beauty, B2B, etc. Read guides first for rules, vertical page for weights, use-case for execution.
Peak season guide reading order
Six weeks before BFCM: list hygiene guide for sunset sprint. Four weeks: seasonal campaign governance to draft collision calendar rows. Three weeks: cross-channel coordination to assign SMS and loyalty caps. Two weeks: attribution guide review with finance for margin thresholds. One week: popup handoff check — pause capture experiments that conflict with VIP early access. Post-peak: deliverability section of list hygiene guide within 14 days.
Guide + stack tool pairing
Stack architecture pairs with /apps roster for tool selection. Popup handoff pairs with Privy/Justuno battlecards. Loyalty integration pairs with Marsello/Yotpo reviews before points launch. Review-UGC pairs with email design playbook module specs. Attribution pairs with analytics use-case playbook holdout methods. Tool sprawl pairs with alternatives hub when retiring vendors.
Guide deliverables checklist
After reading the ten guides, your team should have: a layer owner matrix (stack architecture), capture tag schema with five-minute handoff SLA (popup handoff), collision calendar template with sale-week rows (cross-channel coordination), finance metric definitions with holdout design (attribution), sunset policy at 90–180 days (list hygiene), loyalty enrollment timing rules (loyalty integration), Yotpo module map in templates (review-ugc), peak-week governance doc (seasonal campaigns), overlap audit with retire decisions (tool sprawl), and retained internal ownership list (agency vs in-house).
Guides are prerequisites for playbooks — running winback or BFCM playbooks without collision calendar and list hygiene guides completed first is how merchants burn placement in January. Read guides for rules, /for for vertical weights, /use-cases for moment execution, /compare for tool finalists.
Stack governance rituals
Weekly: fifteen-minute collision check — any subscriber receive popup + cart + SMS same day? Monthly: Shopify net sales vs platform attribution reconcile. Quarterly: tool sprawl audit and segment logic review. Pre-peak: list hygiene sprint and seasonal governance refresh. Post-peak: deliverability audit within fourteen days. These rituals are boring and profitable — skip them and every guide becomes shelfware while invoice total climbs.
Guide-to-playbook mapping
Popup handoff guide before welcome playbook. Cross-channel coordination before cart + SMS playbooks. Discount strategy before winback and loyalty playbooks. List hygiene before deliverability and BFCM playbooks. Attribution before analytics playbook. Loyalty integration before loyalty playbook. Review-UGC before browse abandonment and reviews playbooks. Stack architecture before any of the above — it assigns owners so guides do not contradict each other in production.
Founders at under $50k/mo: read stack architecture, popup handoff, and list hygiene — execute welcome and cart playbooks only until collision incidents stay under one per sale week. Then add remaining guides as revenue band and team capacity grow.
Why ten guides instead of one mega-post
Stack problems arrive at different moments — peak season, migration, agency hire, loyalty launch, invoice sprawl. Splitting governance into focused guides lets operators update one document when Gmail requirements change without rereading sixty pages. Each guide cross-links to playbooks and vertical pages so implementation stays concrete. Marketing stack angle throughout: capture, lifecycle, SMS, proof, loyalty, analytics — not email-only advice divorced from popup and SMS collision reality.
Documentation output template
After each guide, save one page internally: owner name, last updated date, linked live flows, open risks, next review date. Guides without internal documentation become advice nobody executes — the hub exists to force stack governance into artifacts your team owns, not PDFs an agency keeps.