14-email-marketing-global
# ClaudeWave Definition This Claude Code skill generates region-compliant email marketing automation strategies for four global markets: US (CAN-SPAM opt-out framework), EU (GDPR mandatory opt-in), Southeast Asia (PDPA per-country requirements), and Latin America (LGPD Brazil). Use it when launching newsletters, nurture sequences, re-engagement campaigns, or transactional automations across multiple regions where legal compliance varies significantly by jurisdiction.
git clone --depth 1 https://github.com/minhnv0807/ai-business-skills /tmp/14-email-marketing-global && cp -r /tmp/14-email-marketing-global/skills/en/14-email-marketing-global ~/.claude/skills/14-email-marketing-globalSKILL.md
# Email Marketing (Global)
> Email is the only owned channel — algorithm-proof, free to re-reach. **But legal differs HUGELY by region: US allows opt-out, EU mandates opt-in, SEA/LATAM mostly require opt-in.** Pick the right variant — getting this wrong can cost up to EUR 20M (GDPR) or USD 51,744 per email (CAN-SPAM).
---
## For newbies
### Who is this skill for?
| Audience | Concrete example |
|----------|------------------|
| Founder / DTC brand running newsletter | Shopify store, SaaS company, B2B service |
| Agency setting up email automation for client | Welcome series, nurture, re-engage |
| Marketer migrating from one ESP to another | Klaviyo to Mailchimp, ActiveCampaign to Brevo |
| Multi-region brand needing legal-safe email | Selling US + EU + LATAM, must comply per region |
### Who is this NOT for?
- **Vietnam-only email marketing** -> Use `14-email-marketing` (VN skill) — covers PDPA Vietnam (Decree 13/2023)
- **Transactional-only (order confirms, password reset)** -> Use ESP defaults; transactional emails have softer consent rules in most regions
- **SMS / WhatsApp / push** -> Different channels with different laws (TCPA US, GDPR EU)
### 30-second pre-read
This skill produces ONE email marketing strategy file with 4 components: subscriber segmentation, sequence templates (welcome / nurture / re-engage / promo), automation flow, and KPI tracking. Pick 1 of 4 region variants — the variant tunes the LEGAL framework (consent model, unsubscribe rules, data retention, cross-border transfer). Every email automation built without this risks legal exposure.
### 3 common errors
1. **Reusing US opt-out logic in EU** -> GDPR violation; fines up to EUR 20M or 4% global revenue
2. **Skipping double opt-in for EU/Brazil/SEA** -> Cannot prove consent if challenged; subscribers can demand deletion
3. **Missing physical address in footer** -> CAN-SPAM violation US; EUR 51,744 per email
---
## Why do you need this skill?
Email is the highest-ROI channel (USD 36-42 per USD 1 spent globally), but legal compliance is non-negotiable. Without the right region variant:
- US brand using EU opt-in flow -> losing 30-50% of subscribers unnecessarily
- EU brand using US opt-out flow -> direct GDPR violation
- LATAM brand ignoring LGPD -> BRL 50M penalty risk in Brazil
- SEA brand mixing rules -> PDPA Singapore + per-country differences
Pick the right variant once -> all downstream emails compliant by default.
---
## Workflow
```
Step 0: Check global context file
|-- exists -> read product / region / customer info
|-- missing -> suggest user run product-marketing-context-global first
Step 1: Pick region variant (US / EU / SEA / LATAM)
Step 2: Choose ESP based on region (Klaviyo / Mailchimp / ActiveCampaign / Brevo)
Step 3: Set up legal foundation (consent flow, footer, unsubscribe, DPA)
Step 4: Design segmentation (behavioral + lifecycle)
Step 5: Build sequences (welcome / nurture / re-engage / promo)
Step 6: Configure automation flow
Step 7: Set up tracking + A/B test plan
```
---
## Step 0: Check global context file
Check whether `.agents/product-marketing-context-global.md` exists:
- **Yes** -> Read product, customer, region, language, regulation context. Do NOT re-ask.
- **No** -> Suggest running `product-marketing-context-global` first. If user wants to continue, ask 2-3 minimum questions about product + region.
---
## Step 1: Pick region variant
Ask the user one question: **"Which is your PRIMARY region: US, EU, SEA, or LATAM?"**
### Decision tree (LEGAL FRAMING)
```
Where do MOST of your subscribers live?
|-- US / Canada
| --> 01-us.md (CAN-SPAM Act 2003, opt-out OK, CCPA/state laws)
|-- EU / EEA / UK
| --> 02-eu.md (GDPR + ePrivacy, opt-in MANDATORY, EUR 20M penalty)
|-- Southeast Asia (SG, MY, ID, TH, PH)
| --> 03-sea.md (PDPA Singapore + per-country, mostly opt-in)
|-- Latin America (BR, MX, AR, CO, CL)
| --> 04-latam.md (LGPD Brazil + LFPDPPP Mexico, opt-in mandatory)
|-- Vietnam only
| --> Use `14-email-marketing` (VN skill) — Decree 13/2023
|-- Multi-region
--> Default to STRICTEST applicable region (usually EU GDPR)
```
### Why "default to strictest" matters
If you sell in US + EU + LATAM, you can either:
1. **Run separate sequences per region** (best — but operationally heavy)
2. **Apply EU GDPR rules globally** (safe — but loses 20-30% US subscribers due to double opt-in friction)
For most early-stage brands, option 2 is the safer default. Document the decision in your DPA.
---
## Step 2: Choose ESP (Email Service Provider)
| ESP | Strength | Region fit | Legal features |
|-----|----------|------------|---------------|
| **Klaviyo** | E-commerce / DTC | US (default), EU (with EU data center) | GDPR-ready, opt-in flows, suppression lists |
| **Mailchimp** | General-purpose, easy UI | US (HQ), EU (Intuit-owned, GDPR DPA available) | Built-in GDPR forms, double opt-in toggle |
| **ActiveCampaign** | CRM + automation | US default, global | Behavioral + GDPR consent tracking |
| **Brevo (Sendinblue)** | EU-native, transactional | EU (data residency in FR/DE), Global | GDPR by default, EU servers |
| **Customer.io** | API-first, developer-friendly | Global | GDPR + CCPA + LGPD ready |
| **HubSpot Marketing Hub** | All-in-one CRM | US default, EU (with EU hosting) | GDPR consent + cookie management |
### ESP picker per region
- **US (DTC/e-commerce):** Klaviyo (default) or Mailchimp
- **US (B2B SaaS):** ActiveCampaign or HubSpot
- **EU:** Brevo (EU servers), Klaviyo EU, Mailchimp + EU DPA
- **SEA:** Mailchimp, ActiveCampaign (no native local ESP dominant)
- **LATAM:** Brevo (BR datacenter via partner), ActiveCampaign, RD Station (BR-native)
---
## Step 3: Legal foundation (varies by variant)
This is the CRITICAL step. Read the variant file carefully — it spells out the consent model, footer requirements, unsubscribe rules, and data retention specific to yourKe hoach Fullstack Marketing — master skill tong hop chien luoc, noi dung, trien khai, hieu suat, va timeline. Goi cac skill con de hoan thien output.
Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.
Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.
Lich noi dung thang — len lich dang bai da kenh voi ti le pheu, content pillar, repurposing matrix, va scoring tieu chi.
Brief chien dich marketing — 9 phan day du tu Context den Risk, bao gom creative direction, RACI, budget allocation theo phase, va auto-trigger cac skill lien quan.
Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.
Danh gia hieu suat marketing — audit performance ads va organic, chan doan root cause, de xuat toi uu voi action plan 48h va checklist hang tuan.
Use when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality, 5-Whys, regional benchmarks for US, EU, SEA, and LATAM, and a 48-hour action plan. Covers dropshipping ROAS and BE-ROAS. Trigger on 'why is CPA so high', 'my ads are not converting', 'ROAS dropped', 'we are burning budget', 'performance is bad this month', 'diagnose the funnel'. Also use when the user pastes a screenshot of numbers with no question attached. Not for — auditing account configuration and scoring health, see `21-ads-audit-global`; writing a report someone else reads, see `07-marketing-report-global`; turning a raw export into insight, see `13-data-analysis-global`.