Email & SMS Advanced

Lineage: upgraded from IDS_Email_SMS_Advanced.md. Practitioner base: synthesis of 50 email/SMS strategists, Klaviyo partners, and DTC retention operators (IDS original) · Chase Dimond · Ezra Firestone (Smart Marketer) — carried forward from LUCE_05. Current as of July 2026.

---

#THE ONE-PAGE VERSION

1. Email and SMS are the only acquisition-adjacent channels where the marginal cost of a message is near zero and you own the relationship outright — no algorithm, no CPM, no auction. A brand that skips a serious retention stack is paying acquisition cost for customers it has already won.
2. Email is the highest-converting traffic source in e-commerce, full stop: email traffic converts at 4.0–5.3%, against a Shopify-store average of ~1.4% and paid-social cold traffic of 0.5–1.2%. Nothing else you run converts this well, at this cost.
3. At maturity, email + SMS should produce 25–35% of total revenue at 80%+ contribution margin (best-in-class operators push past 40%). If you're under 20% with a list of any size, something in this module is broken — the Decision Tree below diagnoses where.
4. Klaviyo is still the standard platform. Pricing as of mid-2026: free up to 250 profiles, then from $20/month, scaling by profile count. There's no reason to run a serious store on anything else once you have paying customers to segment.
5. Flows (automated, trigger-based) should generate 60–70% of email/SMS revenue; campaigns (broadcast sends) the remaining 30–40%. Build flows first — they run without you.
6. The 8-flow architecture — Welcome, Abandoned Checkout, Browse Abandonment, Post-Purchase, Win-Back, VIP, Sunset/List Cleaning, Replenishment — is not optional infrastructure. It's the difference between a list that monetizes itself and a list that's dead weight on your Klaviyo bill.
7. List growth isn't a separate project from your store's CRO work — it's the same capture points LUCE_08 already optimizes (exit-intent popup, checkout email field, post-purchase SMS upsell) pointed at Klaviyo instead of into the void.
8. SMS opens at 82–98% — the highest of any channel — but it is legally regulated (TCPA), burns out fast, and should never exceed 2–4 sends/month outside of genuinely high-intent moments. Treat it as a privileged channel, not a second inbox.
9. Deliverability is not a settings checkbox you do once. SPF/DKIM/DMARC authentication, list hygiene, and engagement-based sending determine whether your emails land in the inbox or the spam folder — and a large unhealthy list is worse than a small healthy one.
10. Zero-party data — information the customer volunteers, not information you infer — is the highest-leverage 2026 addition to this stack: a 3-question post-purchase survey or quiz funnel turns a flat welcome series into a segmented one, and it's free.
11. AI collapses the blank-page problem in campaign drafting — subject line variants, body drafts, segment-specific angles in minutes — but voice, claims accuracy, and the send decision stay human. This module gives you the guardrail workflow, not just the shortcut.
12. The lean solo-operator version of this module is five flows, one weekend, zero paid SMS tool. If you're at the $1k proof-of-concept stage, Section 9 is the only part of this module you need to execute before your first 100 customers — the rest is where you graduate to.
13. Every worked number in this module uses 2026 reality: Klaviyo's current pricing tiers, TCPA's actual quiet-hours rule, and realistic (not aspirational) recovery/conversion rates pulled from current benchmarks — not the inflated round numbers a lot of "guru" retention content still recycles.
14. This module closes the loop LUCE_05 opened: that module gave you the 7-flow foundation every store needs live before touching anything here. This module is what "graduating to depth" actually looks like — deeper segmentation, deliverability engineering, campaign calendars, and the SMS compliance detail LUCE_05 deliberately left out.
15. This is the final module in the course. Read the closing note at the bottom — it ties this channel back to the full LUCE arc: Launch → Unit Economics → Compound → Exit.

---

#SECTION 1: THE RETENTION REVENUE MODEL

#1.1 Why Retention Is the Real Business

Your ad spend buys a customer once. Your email and SMS program determines whether that customer is worth having bought at all.

The economics of a retention-optimized business vs. a retention-neglected one (2026 figures):

A business converting 35% of buyers into repeat customers can sustainably pay 2× the CAC of a competitor stuck at 15% — with blended e-commerce CAC already running $68–84 in 2026, that gap is the difference between a business that survives Meta's next CPM increase and one that doesn't. This is not a marketing nicety; it's a structural acquisition advantage that shows up directly in LUCE_09's unit-economics model.

#1.2 The Retention Revenue Split

A fully built email + SMS stack should generate:

• 25–35% of total revenue attributed to email/SMS at maturity (best-in-class brands push 40%+)
• Flows: 60–70% of that email/SMS revenue — automated, runs without a human touching it daily
• Campaigns: 30–40% of that email/SMS revenue — broadcast sends you actively schedule and write

Diagnostic reading of your own split: if email/SMS is under 20% of total revenue with a list of meaningful size, one of three things is true — flows aren't built, list health is poor, or you're not sending enough campaigns. Section on Decision Trees below turns this into a checkable branch instead of a vague feeling.

#1.3 Platform Selection

Klaviyo remains the default choice for any DTC brand serious about this channel. Pricing as of mid-2026: free up to 250 profiles, then from $20/month, scaling by profile count as your list grows. For a $1k proof-of-concept operator, this means the entire flow architecture in this module costs nothing until you cross 250 subscribers — there is no financial reason to delay building it.

Why Klaviyo still wins:

• Native Shopify integration with real-time event data sync (order placed, product viewed, checkout started — no manual pixel wiring)
• Flow triggers from any Shopify event, including refunds and subscription changes
• Built-in predictive analytics: predicted LTV, churn risk, expected next order date
• Real-time segment builder with event-based conditions (not just static list tags)
• Native A/B testing on flows and campaigns
• SMS built into the same platform — no context-switching between two dashboards

When to look elsewhere:

The Klaviyo-SMS-vs-dedicated-tool threshold: below $5M/year in revenue, Klaviyo's native SMS is sufficient — the simplicity of one platform outweighs the marginal sophistication a dedicated tool adds. At $5M+, evaluate Postscript or Attentive if SMS carries a meaningful share of retention revenue; coordinating two platforms only pays off once the volume justifies the coordination overhead. (Full decision logic in the Decision Trees section.)

---

#SECTION 2: LIST GROWTH — THE SAME CAPTURE POINTS LUCE_08 ALREADY BUILT

#2.1 List Growth Is a CRO Problem Wearing a Marketing Hat

LUCE_08 built your store's conversion-optimized capture points — exit-intent popups, checkout fields, post-purchase moments — to sell product. This section is the reminder that every one of those same touchpoints is also a list-growth mechanism, and treating them as two separate projects wastes the CRO work you've already done.

Email capture methods, ranked by conversion rate (2026 benchmarks):

List growth targets by stage:

#2.2 Zero-Party Data — The 2026 Addition to This Playbook

What changed since the IDS original: the original treated list growth purely as a volume game — capture the email, sort quality into the popup vs. checkout methods above. The 2026 addition is zero-party data: information a customer volunteers directly (a quiz answer, a stated preference, a survey response), as distinct from first-party data you infer from behavior (pages viewed, items purchased). Zero-party data is higher-trust, higher-signal, and lets you segment a welcome series before the customer has bought anything — which is exactly the moment your flows are otherwise guessing.

Three zero-party data plays that pay for themselves immediately:

1. The post-signup micro-quiz. After email capture, a 2–3 question quiz ("What's your biggest [category] challenge?" / "Which best describes you?") routes the subscriber into a segmented Welcome Series variant instead of the generic one. Klaviyo's segment builder reads quiz-answer properties directly — no separate tool required for a simple 2–3 question version.
2. The post-purchase "why did you buy" survey. One email in the Post-Purchase flow (Section 3.4) asks a single open or multiple-choice question: "What convinced you to buy?" The answers become both a copy-testing goldmine (Section 7.3) and a segmentation input for future campaigns.
3. Preference-center segmentation. A simple preference page (category interest, send-frequency preference) reduces unsubscribes from subscribers who'd rather get fewer, more relevant sends than none at all — a direct list-health lever (Section 2.3).

None of these require a dedicated quiz-funnel tool at the $1k-operator stage — a Klaviyo custom property captured via a simple on-site form or post-purchase email does the job. Graduate to a dedicated quiz platform (e.g., Octane AI) only once quiz-driven segments are demonstrably outperforming your generic flows in the KPI table below.

#2.3 List Health — The Silent Business Killer

A large, unhealthy list actively damages you. Inbox providers (Gmail, Yahoo, Outlook) track sending reputation based on engagement signals across your entire list — sending to unengaged subscribers tanks deliverability for everyone else on it, including your best customers.

The four health metrics to watch:

Note on open rate: iOS 15+ Mail Privacy Protection generates machine opens that inflate open-rate numbers across the entire industry. Track click rate as your primary engagement signal — it isn't distorted by Apple's proxy-opens the way open rate is.

The Suppression Pyramid — who not to email:

TIER 1 — Always suppress (never email again)
  - Hard bounces (address doesn't exist)
  - Spam complainers
  - Manual unsubscribes

TIER 2 — Suppress from marketing (transactional only)
  - Zero opens in 365+ days
  - Opens are exclusively Apple MPP machine opens — never a real click

TIER 3 — Win-back segment (attempt before suppressing)
  - 120–365 days since last click
  - Run one sunset campaign (Flow 7, Section 3.7) before permanent suppression

The 90-day list cleanse: every 90 days, review your Klaviyo deliverability dashboard — move zero-engagement subscribers (365+ days, zero clicks) to suppression, run a single "are you still interested?" send to the 180–365-day no-click segment, and suppress non-responders. This is not optional maintenance; skipping it is Failure Mode #10 below.

---

#SECTION 3: THE FLOW ARCHITECTURE

#3.1 Flow Priority Order

Build in this order. Each subsequent flow adds incrementally less revenue than the one before it — flows 1–4 are non-negotiable; flows 5–8 are where a mature retention stack differentiates itself.

#3.2 Flow 1 — Welcome Series (Most Important Flow)

Purpose: convert new subscribers who haven't bought yet into first-time buyers, and build brand affinity in the ones who aren't ready yet.

Email 1 — Immediate
Subject: Here's your [X]% off (+ what we're about)
- Coupon prominent, above the fold
- 2–3 sentences of brand story — not a wall of text
- Hero product, direct link to buy
Goal: capture the first-purchase-ready segment immediately

Email 2 — 24hr (if no purchase)
Subject: [Name], did you know this about [brand]?
- Brand story in depth, founder photo/video if authentic
- Social proof: "Over [X] customers" or press mentions
Goal: build trust for the browsers who didn't convert on email 1

Email 3 — 48hr (if no purchase)
Subject: The [specific benefit] most people don't know about
- Pure education, not a hard sell — mention product once in context
Goal: become a helpful brand, not just an advertiser

Email 4 — Day 4 (if no purchase)
Subject: Real people, real results
- 5–7 reviews/testimonials with photos or UGC screenshots
Goal: overcome objections with social proof

Email 5 — Day 7 (if no purchase)
Subject: Last chance: your [X]% off expires soon
- Genuine urgency — set the coupon to actually expire in Klaviyo
Goal: convert fence-sitters

Email 6 — Day 14 (if no purchase)
Subject: Still deciding? Start here.
- Address the top objection directly; simple product-fit guide
Goal: convert the undecided with clarity, not pressure

Email 7 — Day 30 (if no purchase)
Subject: We made this for you.
- Final attempt — refreshed offer format (free gift vs. % off)
Goal: capture remaining value before moving to the general list

Conversion target: 20–35% of welcome-series recipients purchase within 10 days (per LUCE_05); the 7-email extended version above pushes total-series conversion higher across the full 30-day window for subscribers who don't buy in the first 10 days.

Settings that matter: Smart Sending OFF (this series should reach subscribers even if other campaigns are firing); flow filter "not placed order in last 180 days" on every email after email 1 so a purchase exits the flow immediately; A/B test subject lines on emails 1, 2, and 5 first — highest volume, highest impact.

Zero-party upgrade (Section 2.2): if you've captured a quiz answer at signup, branch email 2 by quiz segment instead of sending the generic version — this alone is the single highest-leverage upgrade available to an existing welcome series.

#3.3 Flow 2 — Abandoned Checkout (Highest Immediate ROI)

Context: someone reached checkout, Klaviyo captured their email, and they didn't complete the purchase. This is the hottest segment on your list — a payment method was already out.

Email 1 — 1hr after abandonment
Subject: You left something behind
- Product image, direct restore-cart link, no discount yet
Expected recovery: 8–15% of receivers

Email 2 — 24hr (if no purchase)
Subject: [Name], still thinking it over?
- Objection handling: guarantee, free returns, shipping policy; one testimonial
- Still no discount — preserve margin
Expected recovery: 3–6% of receivers

Email 3 — 48hr (if no purchase)
Subject: Last chance — cart expires + special offer inside
- Introduce 5–10% discount or free shipping; real expiration timestamp
Expected recovery: 2–4% of receivers

Combined recovery rate across the sequence: 15–25% of abandoned checkouts — consistent with LUCE_05's foundation-level target; this is the fully built-out version.

SMS complement (if opted in): SMS 1 at 30 minutes if email 1 goes unopened ("[Brand]: Hey [Name]! You left [Product] in your cart. Grab it here: [link]. Reply STOP to opt out"); SMS 2 at 2 hours with the discount code if still no purchase. SMS consistently outperforms email in checkout abandonment by 2–3× on open rate — this is the single highest-ROI SMS automation in the entire stack.

#3.4 Flow 3 — Browse Abandonment

Trigger: product page view, no add-to-cart — lower intent than checkout abandonment, softer touch.

Email 1 (4hr): "Still thinking about [product]?"
Email 2 (Day 2): Social proof on the specific product viewed

Keep this flow short. Browse abandonment is a warmer nudge, not a hard sell — over-building it produces the same "corporate megaphone" feel that kills SMS performance (Section 5.4).

#3.5 Flow 4 — Post-Purchase (The LTV Engine)

Purpose: thank, onboard, cross-sell, and build loyalty in the 0–90 day window after a first purchase. This flow determines whether a customer buys a second time — and second-purchase rate is the single number that moves your sustainable CAC ceiling (Section 1.1).

Email 1 — Immediate (transactional)
Subject: Order confirmed: [Order #]
- Order summary, fulfillment timeline, "we're packing your order now"

Email 2 — On ship (transactional)
Subject: Your order is on its way!
- Tracking link prominent, build anticipation

Email 3 — 2 days post-delivery
Subject: How are you liking [Product] so far?
- Check-in, soft review-request ask, link to review platform (Loox/Yotpo/Okendo)

Email 4 — Day 5 post-delivery
Subject: Getting the most from [Product]
- How-to/usage content — position as expert, not seller

Email 5 — Day 10 post-delivery
Subject: Customers who bought [Product] also love this
- Cross-sell 2–3 complementary products, not overwhelming

Email 6 — Day 20 post-delivery
Subject: Your results so far?
- Social proof at the 3-week mark; soft repurchase nudge if consumable

Email 7 — Day 30 post-delivery
Subject: [Name], one month in — we have a gift for you
- Loyalty-framed 10% repeat-purchase offer

Email 8 — Day 45 post-delivery (if no second purchase)
Subject: [Product] results take time — here's what to expect
- Re-educate on timeline (especially supplements/skincare); prevent silent churn

Zero-party insertion point: Email 3 or 4 is the natural home for the "what convinced you to buy" micro-survey (Section 2.2) — it's the moment engagement is highest and the answer feeds both copy testing and future segmentation.

#3.6 Flow 5 — Win-Back

Trigger: purchased once (or more), 90–180 days since last order, no engagement in 60+ days.

Email 1 (Day 90): "We miss you, [Name]" — reference their last purchase, no hard sell
Email 2 (Day 120): New product/collection + 15–20% win-back offer (stronger than standard — they need a reason)
Email 3 (Day 150–180): Genuinely final — sunset language ("stay subscribed or we'll stop emailing you") or the most aggressive offer you'll make

What this flow is really doing: either recovering revenue or cleaning your list of contacts who were never coming back — both outcomes protect deliverability (Section 6).

#3.7 Flow 6 — VIP

Trigger: 3+ purchases or $500+ lifetime spend.

Email 1: VIP recognition — early access, dedicated support line
Email 2: 48-hour early access on new launches
Email 3: Referral ask — 25–30% commission or store credit

Your VIP segment is also your cheapest UGC and referral source — cross-reference with LUCE_17's affiliate mechanics if you're running TikTok Shop, since your best repeat customers are often your best unpaid creators.

#3.8 Flow 7 — Sunset / List Cleaning

Trigger: no opens in 90–180 days. This flow protects the deliverability of every other flow and campaign in this module — a list full of dead subscribers drags inbox placement down for your entire sending domain, not just for the unengaged contacts themselves. Two-email re-engagement attempt, then unsubscribe non-openers per the Suppression Pyramid (Section 2.3).

#3.9 Flow 8 — Replenishment / Subscription Nudge

Consumables only. Trigger: estimated product-depletion date based on typical usage cycle (e.g., a 30-day supplement triggers a nudge at day 25). Content: "running low? reorder in one tap" + subscribe-and-save offer if you run a subscription SKU. This is a medium-high-revenue flow for the right category and effectively zero-revenue noise for a durable-goods store — skip it if your product isn't consumed on a cycle.

---

#SECTION 4: CAMPAIGNS — THE PROACTIVE REVENUE ENGINE

#4.1 The Campaign Calendar Framework

Flows are reactive; campaigns are proactive sends you schedule to segments. Monthly volume targets:

Core campaign types (the 3-type rotation, Chase Dimond's framework, unchanged from LUCE_05 but expanded here with a 4th type for calendar planning):

#4.2 The 5-Tier Campaign Segmentation Hierarchy

Never send every campaign to your entire list — segmentation improves deliverability and relevance at the same time.

TIER 1 — Engaged (opened OR clicked in last 30 days)
  Highest deliverability. Every campaign goes here first.

TIER 2 — Engaged (last 90 days)
  60–70% of campaigns reach this segment. Warm, not hot.

TIER 3 — Purchasers (any history, any recency)
  Always included regardless of engagement recency — buyers earned it.

TIER 4 — Cold (90–365 days no engagement, no purchase)
  Promotional/win-back sends only, max 2–3×/month — each send here
  risks further deliverability damage.

TIER 5 — Suppressed (365+ days no engagement, no purchase)
  No marketing sends. Transactional only if they somehow reactivate.

For most campaigns: send to Tier 1 + Tier 2 + Tier 3 — that's your working list. Tier 4 and 5 exist to keep your sunset flow (Section 3.8) and suppression pyramid (Section 2.3) honest, not to pad reach numbers.

#4.3 BFCM Campaign Strategy

Black Friday/Cyber Monday is the single highest-revenue email event of the year — executed correctly, BFCM email can represent 15–25% of annual email revenue in one week.

Pre-BFCM (2 weeks out): tease campaign ("something big is coming"), VIP early-access opt-in to build a high-intent segment before competitors' inboxes get loud.

BFCM SMS: max 1 SMS/day during BFCM (vs. 2 emails/day max) — unsubscribe rates spike hardest during BFCM, so the frequency cap tightens, not loosens, exactly when the temptation to over-send is highest. Best SMS moments: Black Friday AM announcement, Cyber Monday midnight countdown.

---

#SECTION 5: SMS ADVANCED STRATEGY

#5.1 SMS Fundamentals

#5.2 TCPA Compliance — Non-Negotiable

The Telephone Consumer Protection Act (TCPA) governs commercial SMS in the US, and violations carry real financial exposure: $500–1,500 per unsolicited text, and class-action exposure scales with list size. This is the section of the module where "move fast" is the wrong instinct.

The four compliance pillars:

1. Consent — separate and explicit. SMS opt-in is not implied by email opt-in; it requires its own affirmative action. At checkout or on a dedicated opt-in form, use plain language: "Sign up for text alerts — [Brand] SMS. Msg & data rates may apply. Msg frequency varies. Reply STOP to cancel, HELP for help." Do not pre-check an SMS box. Do not bundle SMS consent inside a broader terms-of-service checkbox.
2. Quiet hours. TCPA restricts marketing SMS to 8am–9pm in the recipient's local time zone. Klaviyo/Postscript/Attentive enforce this automatically by matching phone-number area code to time zone, but confirm your platform's quiet-hours setting is actually turned on — it is not always the default.
3. Frequency disclosure. Every opt-in flow must disclose that message frequency varies (or state an expected cadence) and that standard message/data rates may apply. This is a legal requirement, not marketing copy — don't soften it out of the flow.
4. Opt-out handling. Every marketing SMS must include clear opt-out instructions (typically "Reply STOP to unsubscribe"), and the opt-out must process automatically and immediately. Never manually intercept or delay a STOP request.

What the platforms handle vs. what you must configure: Klaviyo, Postscript, and Attentive all enforce TCPA mechanics (quiet hours, STOP processing, opt-in double-confirmation) at the platform level — but the responsibility to configure consent language correctly, avoid pre-checked boxes, and disclose frequency sits with you. A compliant platform running a non-compliant opt-in flow is still a violation.

Never add a phone number to your SMS list from an order form's shipping field alone — that's a shipping-notification consent, not marketing consent, and treating it as the latter is the single most common TCPA mistake new operators make.

#5.3 SMS Flow Architecture — The 5 Essential Automations

1. SMS Welcome (at opt-in)
   Send within 5 minutes. Deliver any promised offer. State expectations
   and opt-out instructions per Section 5.2. Klaviyo handles natively.

2. Checkout Abandonment SMS (Section 3.3)
   Complementary to email — fires if email 1 goes unopened in 30 min.

3. Order Shipped SMS
   Transactional, high open rate, trust-building. Tracking link included.

4. Back-in-Stock SMS
   Extremely high conversion — the subscriber opted in specifically
   because they wanted this item. Fire immediately on restock.

5. Win-Back SMS
   At 90 days since last SMS engagement (distinct from the email
   win-back trigger). Stronger offer is affordable here — the SMS
   list is smaller and the channel converts better per send.

#5.4 SMS Campaign Best Practices

What converts: SMS-exclusive offers ("20% off — text only"), genuine flash sales with real time windows, new-product-launch pings, back-in-stock alerts, live-event invitations.

What kills performance: sending more than 4×/month (unsubscribe spike, near-guaranteed); educational content that belongs in email, not SMS; long messages that truncate and lose meaning; anything that reads like a mass blast instead of a heads-up from a brand that respects the recipient's attention; sending outside the 8am–9pm window.

The cadence rule: if you're unsure whether to send, don't. SMS is a privileged channel — the recipient handed you access to a device that interrupts their day. Treat every send like a text from a person they'd actually want to hear from, not a megaphone with 160 characters of room.

---

#SECTION 6: DELIVERABILITY MASTERY

#6.1 Technical Deliverability Setup

Before anything else: authenticate your sending domain. Without it, emails land in spam at a meaningfully higher rate regardless of how good your copy is.

1. SPF record — authorizes Klaviyo to send on your domain's behalf
2. DKIM record — cryptographic signature proving the email wasn't
   tampered with in transit
3. DMARC record — tells inbox providers what to do with
   unauthenticated mail claiming to be from you
   Start: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com (monitor)
   After 30 days of clean monitoring: move to p=quarantine, then p=reject
4. Custom sending domain — send from mail.yourbrand.com instead of
   Klaviyo's shared domain; meaningfully higher deliverability

Klaviyo setup checklist:

• SPF: include:klaviyomail.com added to your domain's SPF record
• DKIM: Klaviyo-provided CNAME records added to DNS
• DMARC: TXT record added and monitored for 30 days before tightening
• Custom sending domain configured in Klaviyo → Sending Domains
• Dedicated IP: not needed below 100K emails/month — don't pay for this prematurely

#6.2 Inbox Placement Factors, in Order of Importance

1. Domain reputation (~40% of placement). Accumulates over time. Never buy an email list — this is the single fastest way to destroy a domain's reputation permanently.
2. Engagement signals (~30%). Gmail and Yahoo watch whether recipients open, click, and move mail from spam to inbox — or mark it spam and delete. High engagement compounds into a good reputation; low engagement compounds into the spam folder.
3. Spam complaint rate (~20%). >0.08% triggers warnings from Gmail Postmaster Tools; >0.1% actively damages deliverability.
4. Content signals (~10%). Spam-filter keywords matter less than they did a decade ago, but "FREE!!!", all-caps subjects, and excessive punctuation still cost you at the margin.

#6.3 The Warmup Protocol for New Sending Domains

A new or freshly-switched sending domain has zero reputation data with inbox providers, who default to skepticism.

Sending only to your most engaged subscribers during warmup signals to Gmail/Yahoo that your mail is wanted — that's what builds the positive reputation the rest of this module depends on.

---

#SECTION 7: ADVANCED ANALYTICS, ATTRIBUTION, AND COPY TESTING

#7.1 The Weekly Performance Dashboard

#7.2 Revenue Attribution Setup

Klaviyo's default: 5-day click attribution, 1-day open attribution.

Recommended windows:

• First-purchase flows: 5-day click / 1-day open (standard)
• Win-back flows: 14-day click / 5-day open (longer — the customer was dormant, decisions take longer)
• Campaigns: 5-day click / 0-day open (don't credit machine opens as conversions)

The attribution problem: iOS Mail Privacy Protection generates machine opens that inflate attributed email revenue if your platform counts opens as conversion signals. Configure Klaviyo to exclude Apple Mail machine opens from attribution — the resulting revenue number will be lower and it will be accurate, which is the only number worth reporting into LUCE_09's P&L.

#7.3 Subject Line and Copy Testing Science

Subject lines decide roughly 80% of whether an email gets read at all — everything else in the email is secondary until that decision is made.

Variables that lift open rate:

Variables that reduce open rate: fake "Re:" reply-thread tricks (one-time lift, destroys long-term trust); ALL CAPS; excessive punctuation; generic phrasing ("Summer sale," "New arrivals"); over-frequency (recipient fatigue suppresses opens even on genuinely good subject lines).

Testing protocol: test one variable at a time; minimum sample 1,000/variant for campaigns, 500/variant for flows; 4-hour test window before selecting a winner on time-sensitive sends; track open rate and click rate and revenue per email — open rate alone, given the MPP distortion in 7.2, is not a safe optimization target on its own.

---

#SECTION 8: THE AI-ASSISTED CAMPAIGN DRAFTING WORKFLOW

#8.1 Where AI Actually Helps in This Channel

The bottleneck in a mature email/SMS program isn't ideas — it's the time cost of turning 8–16 monthly campaigns into finished, on-brand copy. AI collapses that bottleneck at the draft stage; it does not replace the judgment calls this module has spent seven sections building.

1. Feed the model: your product/offer brief, your brand voice document
   (→ LUCE_07), 3–5 examples of your best-performing past campaigns
   (subject line + body), and the segment you're writing for (Section 4.2).
2. Generate 5–10 subject-line variants spanning the categories in
   Section 7.3 (curiosity, benefit, urgency, question, personalization).
3. Generate one full body draft against the 3-type rotation (Section 4.1)
   you've assigned this send — value, social proof, or promotional.
4. Human filters subject lines down to 2–3 worth A/B testing. This step
   stays manual — models over-generate lines that are generic or make
   claims you can't substantiate (Hopkins's specificity rule, LUCE_05
   Section 6.1, applies identically here).
5. Human edits the body draft for voice, verifies every factual/product
   claim, and confirms the CTA matches the actual offer terms
   (expiration date, discount code, inventory reality).
6. Schedule the send. AI never gets send authority — see 8.3.

This mirrors the organic-content AI workflow LUCE_05 Section 7.1 already teaches you; the difference is you're applying it to owned-channel copy instead of short-form video scripts.

#8.2 Voice Guardrails

AI-generated copy defaults toward the statistical average of its training data — bland, over-polished, and drifting away from the "talk like a friend" principle that makes retention copy convert. Three rules hold the line:

1. Feed it your actual voice every time. Paste 3–5 of your best-performing sends before asking for anything new. A model with no voice reference writes in nobody's voice.
2. Ban corporate reflexes explicitly in the prompt. Instruct against "elevate your routine," "game-changing," "unlock your best self," and any phrase you wouldn't say out loud to a customer standing in front of you.
3. Read every draft aloud before it ships. If it doesn't sound like something you'd actually text or say to a friend, it's not ready — no exceptions for how polished it reads silently on the page.

#8.3 What NOT to Automate

• Claims and specificity. Every discount, expiration date, and product claim in a draft gets checked against what's actually true before it sends — an AI-hallucinated "20% off" on a 15%-off campaign is a real customer-trust and margin problem, not a hypothetical one.
• Segment and offer strategy. Which segment gets which offer, and when, is a business judgment call informed by the KPI table (Section 7.1) and the 5-tier hierarchy (Section 4.2) — not something to hand to a model.
• TCPA-governed SMS copy. Consent language, opt-out instructions, and frequency disclosure (Section 5.2) are legal text, not marketing copy — draft them once correctly with counsel or a compliant platform template, and don't let an AI "improve" them into non-compliance.
• The send decision. AI drafts; a human does the final read and hits send. Every time, no exceptions, regardless of how many campaigns are queued.

---

#SECTION 9: THE LEAN SOLO-OPERATOR VERSION — FIVE FLOWS, ONE WEEKEND

If you're the $1k proof-of-concept operator this course is built for, you do not need Sections 3–8 in full on day one. You need five flows, built in a single weekend, using the free tier of one platform.

Why five, not eight: Section 3.1's priority ordering already tells you that flows 1–4 are non-negotiable and each subsequent flow adds incrementally less. The fifth flow here — Sunset/List Cleaning — isn't a revenue flow at all; it's the cheapest possible insurance against the deliverability collapse described in Failure Mode #10, and it takes under an hour to build.

The five:

What's deliberately deferred: Win-Back, VIP, Replenishment, and full campaign calendaring (Section 4) — none of these matter until you have a repeat-purchase base large enough to segment. Building them at 50 subscribers is premature optimization; the $1k operator's job is proving the offer, not building retention infrastructure for a list that doesn't exist yet.

The weekend build:

SATURDAY MORNING (2–3 hrs)
- Sign up for Klaviyo (free, ≤250 profiles)
- Connect Shopify integration
- Configure SPF/DKIM per Section 6.1 (do this first — deliverability
  compounds from day one, don't retrofit it later)
- Build Flow 2 (Abandoned Checkout) — highest ROI, fastest to build

SATURDAY AFTERNOON (2–3 hrs)
- Build Flow 1 (Welcome Series, 3-email version: offer, brand story,
  final urgency)
- Set up your exit-intent popup and confirm checkout email capture
  is live (Section 2.1) — reuse LUCE_08's existing capture points,
  don't rebuild them

SUNDAY MORNING (1–2 hrs)
- Build Flow 3 (Post-Purchase, 3-email version)
- Build Flow 4 (Browse Abandonment, 2-email version)

SUNDAY AFTERNOON (1 hr)
- Build Flow 5 (Sunset/List Cleaning)
- Add SMS opt-in at checkout with TCPA-compliant consent language
  (Section 5.2) — even if you're not running SMS campaigns yet,
  capturing compliant consent now costs nothing and saves you from
  re-collecting it later
- Test every flow end-to-end with a real order

What graduates you out of the lean version: once you're consistently hitting 100+ subscribers/month of organic growth (Section 2.1) and your Post-Purchase flow is showing a measurable second-purchase rate in the KPI table, it's time to build Win-Back, VIP, and a real campaign calendar (Sections 3.6–3.7 and Section 4). Don't rush there — a five-flow stack running cleanly beats an eight-flow stack half-built.

---

#DECISION TREES

DECISION TREE 1: Your Email/SMS Revenue Is Below Target — Where's the Leak?

START: Is email/SMS revenue under 20% of total store revenue,
        with a list of 500+ subscribers?
├─ NO  → You're at or near the 25–35% maturity target. Focus on
│         Section 4 campaign calendar optimization and Section 7
│         copy testing, not new infrastructure.
└─ YES → Are all 4 non-negotiable flows (Welcome, Abandoned Checkout,
          Browse Abandonment, Post-Purchase) live and firing
          (verify in Klaviyo flow status, not memory)?
          ├─ NO  → Build the missing flow(s) first — Section 3. This
          │         is Failure Mode #3, the single most common leak.
          │         Nothing else in this tree matters until flows 1–4
          │         are live.
          └─ YES → Check list health (Section 2.3): is click rate
                    below 0.5%, or spam complaints above 0.08%?
                    ├─ YES → Deliverability problem, not a flow
                    │         problem. Run the 90-day cleanse
                    │         immediately (Section 2.3) and verify
                    │         SPF/DKIM/DMARC (Section 6.1) before
                    │         touching flow copy.
                    └─ NO  → List is healthy and flows are live —
                              this is a campaign-volume or
                              segmentation problem. Check: are you
                              sending fewer than 4 campaigns/month
                              (Section 4.1)? Are you segmenting per
                              Section 4.2, or blasting the full list?
                              Fix volume and segmentation before
                              assuming the channel itself is
                              underperforming.

DECISION TREE 2: Klaviyo Native SMS or a Dedicated SMS Platform?

START: Is annual revenue under $5M?
├─ YES → Use Klaviyo's native SMS module. The simplicity of one
│         platform outweighs any sophistication gap versus a
│         dedicated tool at this scale (Section 1.3).
└─ NO  → Does SMS already represent a meaningful share (>20%) of
          retention revenue, or do you need SMS-specific automation
          Klaviyo's module doesn't offer (e.g., advanced conversational
          flows, complex branching keyword triggers)?
          ├─ NO  → Stay on Klaviyo native SMS — revenue alone doesn't
          │         justify the coordination overhead of two platforms.
          └─ YES → Evaluate Postscript (SMS-first automation depth) or
                    Attentive (enterprise scale, 1M+ lists). Budget for
                    the operational cost of syncing two platforms'
                    segment data before switching.

---

#KPI TABLE — TARGETS, WARNINGS, KILL SWITCHES

---

#THE 2026 REALITY LAYER

Klaviyo's pricing structure is the actual 2026 fact worth anchoring on: free to 250 profiles, then from $20/month. This removes the cost objection entirely for any operator building the lean five-flow stack in Section 9 — the barrier to a serious retention channel in 2026 is time and discipline, not budget.

Email's conversion advantage over every other channel has only widened. At 4.0–5.3% against a Shopify-store average of ~1.4% and paid-social cold traffic of 0.5–1.2%, email is not just "a good channel" — it's the highest-converting traffic source available to a DTC operator, full stop, and that gap is why this module exists as the course's closing deep-dive rather than an afterthought.

Zero-party data is the structural addition the IDS original didn't have a name for. The original's list-growth section was purely a volume-and-quality-tier framework; the 2026 evidence adds a third axis — data the customer volunteers, which segments a welcome series before a single purchase happens. This didn't exist as a distinct practice when the source material was written; it's now a standard play.

TCPA enforcement and consent expectations have not loosened. The $500–1,500-per-violation exposure and the 8am–9pm quiet-hours rule are unchanged mechanics, but Meta's July 2026 removal of the off-platform activity opt-out (LUCE_05's Reality Layer) makes every owned, consent-based channel — email and SMS both — more valuable by comparison: it's the one place your customer relationship isn't subject to a platform's targeting-policy shift.

AI collapsed the drafting bottleneck for campaigns, exactly as it did for organic scripts in LUCE_05. The workflow in Section 8 is deliberately parallel to that module's — this is not a coincidence; it's the same discipline (draft fast, verify claims, keep the human at send) applied to a different surface.

Nothing in the trade-policy or ad-platform disruption this course tracks elsewhere touches this channel directly — email and SMS run on customer relationships you already own, not on tariff schedules or auction dynamics. That structural insulation from 2026's most volatile forces is, itself, the strongest argument for building this stack early rather than treating it as a later-stage nice-to-have.

---

#FAILURE MODES

1. Treating list growth as separate from CRO. Symptom: popup exists but converts poorly, checkout email capture isn't configured, no coordination with LUCE_08's work. Root cause: marketing and CRO run as separate projects with separate owners. Fix: audit every capture point in Section 2.1 against what LUCE_08 already built — they're the same touchpoints.

2. Building flows in the wrong order, or not at all. Symptom: growing list, flat email revenue. Root cause: skipping Section 3.1's priority order — building a VIP flow before Welcome and Abandoned Checkout exist. Fix: flows 1–4 first, always, before anything else in this module.

3. Zero flows behind a growing pop-up list. Symptom: subscriber count climbing, email revenue near zero. Root cause: pop-up captures emails but no automated flow ever fires. Fix: this is Decision Tree 1's first branch — verify flows are actually live, not just built and never turned on.

4. SMS overload. Symptom: unsubscribe rate spikes after a promotional push. Root cause: exceeding the 2–4×/month frequency cap because "SMS converts so well, let's send more." Fix: cap frequency hard; reserve SMS for genuinely high-intent moments (Section 5.4).

5. TCPA non-compliance from a shipping-field phone number. Symptom: SMS list includes numbers that never gave marketing consent. Root cause: treating a shipping-notification phone number as marketing consent. Fix: audit every phone number's consent source; purge anything not collected through an explicit SMS opt-in (Section 5.2).

6. No list hygiene — deliverability quietly collapsing. Symptom: open and click rates declining across every campaign, not just one send. Root cause: Flow 7/Sunset (Section 3.8) was never built; dead subscribers drag every send toward spam. Fix: build and run the sunset flow; run the 90-day cleanse (Section 2.3) without fail.

7. Skipping domain authentication. Symptom: good copy, healthy list, still landing in spam or promotions tabs at a high rate. Root cause: SPF/DKIM/DMARC never configured, or configured but never verified. Fix: run the Klaviyo setup checklist (Section 6.1) before troubleshooting anything else.

8. Corporate-voiced AI drafts shipping unedited. Symptom: low CTR on emails/SMS despite solid production quality and offers. Root cause: skipping the voice guardrails in Section 8.2 — AI's default output drifts generic. Fix: the read-aloud test, every send, no exceptions.

9. Over-building the lean operator's flow stack too early. Symptom: a solo operator spends week one building all 8 flows and a full campaign calendar instead of getting a product live. Root cause: treating this module's full depth as day-one required reading instead of using Section 9's lean five. Fix: build the lean five in a weekend; graduate to the full architecture once the graduation triggers in Section 9 are met.

10. Buying an email list, or treating a purchased list as a shortcut. Symptom: a sudden domain-reputation collapse with no obvious cause. Root cause: any purchased or scraped list — even "verified" ones sold as opt-in — destroys sender reputation almost immediately and is often a direct TCPA/CAN-SPAM violation. Fix: never do this. Every subscriber on the list must have opted in through one of Section 2.1's mechanisms. There is no shortcut here that doesn't cost more than it saves.

---

#SOPs & CADENCES

---

#WEEK-1 ACTION PLAN

1. Day 1: Sign up for Klaviyo (free, ≤250 profiles) if you haven't; connect the Shopify integration; configure SPF/DKIM per Section 6.1 before building anything else.
2. Day 2: Build Flow 2 (Abandoned Checkout) — highest ROI, fastest build. Confirm your Shopify checkout has email capture enabled at step 1.
3. Day 3: Build Flow 1 (Welcome Series, 3-email lean version); verify your exit-intent popup and checkout capture are live per Section 2.1.
4. Day 4: Build Flow 3 (Post-Purchase, 3-email lean version); add the SMS opt-in at checkout with compliant consent language (Section 5.2), even if you're not sending SMS campaigns yet.
5. Day 5: Build Flow 4 (Browse Abandonment) and Flow 5 (Sunset/List Cleaning) — both under an hour combined using the lean templates in Section 9.
6. Day 6: Test every flow end-to-end with a real test order; verify DMARC is in monitor mode and confirm no SPF/DKIM errors in Klaviyo's domain settings.
7. Day 7: Schedule your first broadcast campaign using the AI-assisted drafting workflow (Section 8.1); review Day 1–7 against the KPI table and decide whether you're staying in the lean five or ready to add flows 6–8.

---

#SELF-TEST

1. Per Section 1.2, what three things are true if a store's email/SMS revenue sits below 20% of total revenue with a list of meaningful size — and which decision tree resolves the ambiguity?
2. A store's Welcome Series is converting at 6% within 10 days. Per Section 7.1's dashboard, is that healthy, warning, or action-required — and what's the first thing to check per Decision Tree 1?
3. What's the TCPA quiet-hours window for marketing SMS, and what's the dollar exposure per violation if you ignore it?
4. Per Section 9, why does the lean solo-operator version include Sunset/List Cleaning as one of only five flows, even though it's not a revenue-generating flow?
5. Name two things Section 8.3 says should never be handed to AI in the campaign-drafting workflow, and why each one carries real financial or legal risk if it is.

<details> <summary>Answers</summary>

1. One of three things: flows aren't built, list health is poor, or campaign volume/segmentation is insufficient (Section 1.2). Decision Tree 1 resolves which one by checking, in order: are flows 1–4 live, is list health within range, and is campaign volume/segmentation meeting Section 4 targets.
2. Warning-range (5–8% is "warning" per the dashboard; 6% falls just above the <5% action-required threshold but below the >8% healthy target). Per Decision Tree 1, the first check once flows are confirmed live is list health (click rate, spam complaints) before assuming the flow copy itself is the problem.
3. 8am–9pm in the recipient's local time zone (Section 5.2). Violations carry $500–1,500 per unsolicited text, with class-action exposure scaling with list size.
4. Because it protects the deliverability of the other four flows — a list with no sunset mechanism drags inbox placement down for every other send, including the revenue-generating ones. It's cheap insurance (under an hour to build) against a much more expensive deliverability collapse.
5. Any two of: claims/specificity in offer copy (financial/trust risk if an AI-hallucinated discount or claim ships), segment and offer strategy (a business judgment call, not a drafting task), TCPA-governed SMS consent/opt-out language (legal risk if "improved" out of compliance), or the final send decision (accountability must stay human).

</details>

---

#CROSS-REFERENCES

• → LUCE_05_Marketing.md — the 7-flow foundation this module deepens into 8 (plus the lean-five variant); LUCE_05 also owns the organic-content AI workflow this module's Section 8 mirrors, and the SMS compliance floor this module expands into full TCPA detail.
• → LUCE_08_Store_CRO.md — owns the on-site capture-point mechanics (exit-intent popup design, checkout-field placement, post-purchase upsell moments) this module's Section 2 points at list growth; also the source of the 4–5.3% email-traffic CVR benchmark this module opens with.
• → LUCE_07_Brand_Building.md — the voice document and positioning statement Section 8.1's AI workflow depends on directly.
• → LUCE_09_Finance_Scaling.md — where the second-purchase-rate and CAC-ceiling math from Section 1.1 rolls into the full P&L; also where BFCM revenue concentration (Section 4.3) gets stress-tested against cash-flow timing.
• → LUCE_17_Influencer_UGC_System.md — VIP-segment customers (Section 3.7) are often a store's best unpaid UGC source; this module doesn't repeat that mechanic, LUCE_17 owns it.
• → LUCE_10_Exit_Strategy.md — a documented, high-performing retention stack (25–35%+ of revenue at 80%+ margin, clean flows, healthy list) is a direct valuation lever in an acquisition conversation; buyers price recurring, owned-channel revenue differently than ad-dependent revenue.
• → LUCE_04_Advertising.md / LUCE_14_Advertising_Mastery.md — retargeting-pool health (Meta's July 2026 opt-out removal) makes the owned-list insulation this module builds more valuable every time the paid landscape shifts.

---

#COURSE COMPLETION

This is the twentieth and final module of LUCE. If you've worked through the course in order, you've now covered the full arc: Launch (finding a product, standing up a store, choosing a fulfillment model that survives 2026 trade policy), Unit Economics (landed-cost math, CAC discipline, the contribution-margin thinking that separates a real business from a spreadsheet fantasy), Compound (organic content, paid scaling, brand-building, and — in this module — the owned-channel retention engine that turns one-time buyers into a business with revenue that doesn't reset to zero every time a platform changes its algorithm), and Exit (the valuation and sale mechanics that turn years of operating discipline into a number on a wire transfer).

Email and SMS were deliberately placed last for a reason beyond alphabetical or numerical convenience: every other channel in this course rents attention from a platform that can change its rules, its pricing, or its policies without warning — trade policy shifts every few months, ad platforms adjust CPMs every quarter, and even organic algorithms retrain without notice. The list you build following this module is the one asset in the entire course that answers to no one's roadmap but your own. Build it early, protect its health, and it will still be producing revenue on the day you sell the business — which is exactly the note this course wants to leave you on.

LUCE — Launch. Unit Economics. Compound. Exit.