Email Marketing (Global) skill

Use when the user needs email or lifecycle automation — welcome series, nurture, abandoned cart, re-engagement, broadcast, and transactional flows with subject lines, segmentation, cadence, and deliverability, plus legal variants: CAN-SPAM for US, GDPR opt-in for EU, PDPA for SEA, LGPD for LATAM.

by minhnv0807·MIT license·★ 592 Stars on the repo·GitHub ↗

Use now

Files of Email Marketing (Global)

minhnv0807/master1 file shown
SKILL.md
Show the full text207 lines

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?"

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)

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 your region.

Universal requirements (all regions)
  • Working unsubscribe link in every email
  • Sender identification (brand name, physical address)
  • Subject line accurately describes content (no deceptive headers)
  • Honor unsubscribe within reasonable time (10 days US, 24h EU/SEA/LATAM)
Region-specific requirements (see variants)
  • US: Physical postal address, opt-out within 10 days
  • EU: Explicit opt-in (timestamp + IP logged), DPO if processing large data, DPA with ESP, right to erasure
  • SEA: Per-country (Singapore PDPA strictest), opt-in for marketing
  • LATAM: Brazil LGPD requires opt-in + DPO; Mexico LFPDPPP requires privacy notice

Step 4-7: Segmentation, sequences, automation, tracking

These are largely region-agnostic in CONTENT, but legal-bound in EXECUTION. The variant file documents:

  • What data fields you can/cannot collect (e.g., EU requires "minimum necessary")
  • Retention period (e.g., LGPD Brazil = 5 years max default)
  • Cross-border transfer rules (e.g., EU -> US requires SCCs or DPF)

For sequence templates and KPI structure, the patterns are the same as the VN skill (welcome 3-email, nurture 5-email, re-engage 3-email) but with region-tuned subject lines, send times, and footer.


How other skills use this file

When 00-marketing-plan-global includes email as a channel, it references this skill for the operational layer. When 18-referral-program-global builds a referral flow with email triggers, it inherits the consent model from this skill.


Quality checklist

  • Region variant chosen (US / EU / SEA / LATAM)
  • ESP selected with region-appropriate data residency
  • Consent model documented (opt-in vs opt-out)
  • Footer compliant (physical address + unsubscribe)
  • DPA signed with ESP if processing EU/UK/Brazil data
  • Sequences tested in dev environment before launch
  • Suppression list / hard-bounce auto-removal active
  • A/B test plan documented (one variable at a time)

  • product-marketing-context-global — foundation context (run first)
  • 11-channel-setup-global — channel infrastructure (when available)
  • 18-referral-program-global — referral via email
  • references/global-legal-compliance — deep legal reference

Global Skill 14 (Email Marketing) | Over Powers Agency | v1.0.0

1---
2name: 14-email-marketing-global
3description: "Use when the user needs email or lifecycle automation — welcome series, nurture, abandoned cart, re-engagement, broadcast, and transactional flows with subject lines, segmentation, cadence, and deliverability, plus legal variants: CAN-SPAM for US, GDPR opt-in for EU, PDPA for SEA, LGPD for LATAM. Covers Klaviyo, Mailchimp, and ActiveCampaign. Trigger on 'email marketing', 'welcome sequence', 'drip campaign', 'newsletter', 'abandoned cart emails', 'nobody opens our emails'. Not for — coding HTML that renders correctly in Outlook, see `49-html-email-template-global`; cold outbound to B2B prospects, see `33-b2b-lead-gen-global`; refer-a-friend loops, see `18-referral-program-global`."
4metadata:
5 version: 1.0.1
6 category: operations
7license: MIT
8triggers:
9 - "email marketing"
10 - "email automation"
11 - "newsletter"
12 - "drip campaign"
13 - "GDPR email"
14 - "CAN-SPAM"
15related:
16 - product-marketing-context-global
17 - 11-channel-setup-global
18 - 18-referral-program-global
19 - references/global-legal-compliance
20---
21 
22# Email Marketing (Global)
23 
24> 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).
25 
26---
27 
28## For newbies
29 
30### Who is this skill for?
31 
32| Audience | Concrete example |
33|----------|------------------|
34| Founder / DTC brand running newsletter | Shopify store, SaaS company, B2B service |
35| Agency setting up email automation for client | Welcome series, nurture, re-engage |
36| Marketer migrating from one ESP to another | Klaviyo to Mailchimp, ActiveCampaign to Brevo |
37| Multi-region brand needing legal-safe email | Selling US + EU + LATAM, must comply per region |
38 
39### Who is this NOT for?
40 
41- **Vietnam-only email marketing** -> Use `14-email-marketing` (VN skill) — covers PDPA Vietnam (Decree 13/2023)
42- **Transactional-only (order confirms, password reset)** -> Use ESP defaults; transactional emails have softer consent rules in most regions
43- **SMS / WhatsApp / push** -> Different channels with different laws (TCPA US, GDPR EU)
44 
45### 30-second pre-read
46 
47This 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.
48 
49### 3 common errors
50 
511. **Reusing US opt-out logic in EU** -> GDPR violation; fines up to EUR 20M or 4% global revenue
522. **Skipping double opt-in for EU/Brazil/SEA** -> Cannot prove consent if challenged; subscribers can demand deletion
533. **Missing physical address in footer** -> CAN-SPAM violation US; EUR 51,744 per email
54 
55---
56 
57## Why do you need this skill?
58 
59Email is the highest-ROI channel (USD 36-42 per USD 1 spent globally), but legal compliance is non-negotiable. Without the right region variant:
60- US brand using EU opt-in flow -> losing 30-50% of subscribers unnecessarily
61- EU brand using US opt-out flow -> direct GDPR violation
62- LATAM brand ignoring LGPD -> BRL 50M penalty risk in Brazil
63- SEA brand mixing rules -> PDPA Singapore + per-country differences
64 
65Pick the right variant once -> all downstream emails compliant by default.
66 
67---
68 
69## Workflow
70 
71```
72Step 0: Check global context file
73 |-- exists -> read product / region / customer info
74 |-- missing -> suggest user run product-marketing-context-global first
75Step 1: Pick region variant (US / EU / SEA / LATAM)
76Step 2: Choose ESP based on region (Klaviyo / Mailchimp / ActiveCampaign / Brevo)
77Step 3: Set up legal foundation (consent flow, footer, unsubscribe, DPA)
78Step 4: Design segmentation (behavioral + lifecycle)
79Step 5: Build sequences (welcome / nurture / re-engage / promo)
80Step 6: Configure automation flow
81Step 7: Set up tracking + A/B test plan
82```
83 
84---
85 
86## Step 0: Check global context file
87 
88Check whether `.agents/product-marketing-context-global.md` exists:
89- **Yes** -> Read product, customer, region, language, regulation context. Do NOT re-ask.
90- **No** -> Suggest running `product-marketing-context-global` first. If user wants to continue, ask 2-3 minimum questions about product + region.
91 
92---
93 
94## Step 1: Pick region variant
95 
96Ask the user one question: **"Which is your PRIMARY region: US, EU, SEA, or LATAM?"**
97 
98### Decision tree (LEGAL FRAMING)
99 
100```
101Where do MOST of your subscribers live?
102 |-- US / Canada
103 | --> 01-us.md (CAN-SPAM Act 2003, opt-out OK, CCPA/state laws)
104 |-- EU / EEA / UK
105 | --> 02-eu.md (GDPR + ePrivacy, opt-in MANDATORY, EUR 20M penalty)
106 |-- Southeast Asia (SG, MY, ID, TH, PH)
107 | --> 03-sea.md (PDPA Singapore + per-country, mostly opt-in)
108 |-- Latin America (BR, MX, AR, CO, CL)
109 | --> 04-latam.md (LGPD Brazil + LFPDPPP Mexico, opt-in mandatory)
110 |-- Vietnam only
111 | --> Use `14-email-marketing` (VN skill) — Decree 13/2023
112 |-- Multi-region
113 --> Default to STRICTEST applicable region (usually EU GDPR)
114```
115 
116### Why "default to strictest" matters
117 
118If you sell in US + EU + LATAM, you can either:
1191. **Run separate sequences per region** (best — but operationally heavy)
1202. **Apply EU GDPR rules globally** (safe — but loses 20-30% US subscribers due to double opt-in friction)
121 
122For most early-stage brands, option 2 is the safer default. Document the decision in your DPA.
123 
124---
125 
126## Step 2: Choose ESP (Email Service Provider)
127 
128| ESP | Strength | Region fit | Legal features |
129|-----|----------|------------|---------------|
130| **Klaviyo** | E-commerce / DTC | US (default), EU (with EU data center) | GDPR-ready, opt-in flows, suppression lists |
131| **Mailchimp** | General-purpose, easy UI | US (HQ), EU (Intuit-owned, GDPR DPA available) | Built-in GDPR forms, double opt-in toggle |
132| **ActiveCampaign** | CRM + automation | US default, global | Behavioral + GDPR consent tracking |
133| **Brevo (Sendinblue)** | EU-native, transactional | EU (data residency in FR/DE), Global | GDPR by default, EU servers |
134| **Customer.io** | API-first, developer-friendly | Global | GDPR + CCPA + LGPD ready |
135| **HubSpot Marketing Hub** | All-in-one CRM | US default, EU (with EU hosting) | GDPR consent + cookie management |
136 
137### ESP picker per region
138 
139- **US (DTC/e-commerce):** Klaviyo (default) or Mailchimp
140- **US (B2B SaaS):** ActiveCampaign or HubSpot
141- **EU:** Brevo (EU servers), Klaviyo EU, Mailchimp + EU DPA
142- **SEA:** Mailchimp, ActiveCampaign (no native local ESP dominant)
143- **LATAM:** Brevo (BR datacenter via partner), ActiveCampaign, RD Station (BR-native)
144 
145---
146 
147## Step 3: Legal foundation (varies by variant)
148 
149This is the CRITICAL step. Read the variant file carefully — it spells out the consent model, footer requirements, unsubscribe rules, and data retention specific to your region.
150 
151### Universal requirements (all regions)
152 
153- Working unsubscribe link in every email
154- Sender identification (brand name, physical address)
155- Subject line accurately describes content (no deceptive headers)
156- Honor unsubscribe within reasonable time (10 days US, 24h EU/SEA/LATAM)
157 
158### Region-specific requirements (see variants)
159 
160- **US:** Physical postal address, opt-out within 10 days
161- **EU:** Explicit opt-in (timestamp + IP logged), DPO if processing large data, DPA with ESP, right to erasure
162- **SEA:** Per-country (Singapore PDPA strictest), opt-in for marketing
163- **LATAM:** Brazil LGPD requires opt-in + DPO; Mexico LFPDPPP requires privacy notice
164 
165---
166 
167## Step 4-7: Segmentation, sequences, automation, tracking
168 
169These are largely region-agnostic in CONTENT, but legal-bound in EXECUTION. The variant file documents:
170- What data fields you can/cannot collect (e.g., EU requires "minimum necessary")
171- Retention period (e.g., LGPD Brazil = 5 years max default)
172- Cross-border transfer rules (e.g., EU -> US requires SCCs or DPF)
173 
174For sequence templates and KPI structure, the patterns are the same as the VN skill (welcome 3-email, nurture 5-email, re-engage 3-email) but with region-tuned subject lines, send times, and footer.
175 
176---
177 
178## How other skills use this file
179 
180When `00-marketing-plan-global` includes email as a channel, it references this skill for the operational layer. When `18-referral-program-global` builds a referral flow with email triggers, it inherits the consent model from this skill.
181 
182---
183 
184## Quality checklist
185 
186- [ ] Region variant chosen (US / EU / SEA / LATAM)
187- [ ] ESP selected with region-appropriate data residency
188- [ ] Consent model documented (opt-in vs opt-out)
189- [ ] Footer compliant (physical address + unsubscribe)
190- [ ] DPA signed with ESP if processing EU/UK/Brazil data
191- [ ] Sequences tested in dev environment before launch
192- [ ] Suppression list / hard-bounce auto-removal active
193- [ ] A/B test plan documented (one variable at a time)
194 
195---
196 
197## Related skills
198 
199- `product-marketing-context-global` — foundation context (run first)
200- `11-channel-setup-global` — channel infrastructure (when available)
201- `18-referral-program-global` — referral via email
202- `references/global-legal-compliance` — deep legal reference
203 
204---
205 
206*Global Skill 14 (Email Marketing) | Over Powers Agency | v1.0.0*
207 

Discussion

Alternatives