1---2name: qa-gates3description: Use before launching sequences to validate content, data, compliance, and monitoring.4---5
6# Email QA Gates Skill
7
8## When to Use
9- Prior to activating new nurture or lifecycle programs.
10- After major changes to segmentation, personalization tokens, or deliverability settings.
11- During post-incident reviews to ensure fixes remain in place.
12
13## Framework
141. **Content & Personalization** – placeholders resolved, links tracked, dynamic content fallback tested.
152. **Data & Routing** – trigger logic, smart lists, suppression rules, CRM fields synced.
163. **Compliance** – footer language, preference center links, consent status, regional routing.
174. **Tracking & Analytics** – UTM/tagging consistency, BI/warehouse pipes, alert webhooks.
185. **Monitoring Hooks** – dashboards referenced, alert thresholds set, rollback plan documented.
19
20## Templates
21- QA runbook with owner, status, evidence links for each checklist item.
22- Proofing matrix (persona × email × device × ISP) for screenshot validation.
23- Launch readiness form requiring sign-off from marketing, ops, legal, and RevOps.
24
25## Tips
26- Pair with `deliverability-ops` to confirm authentication and inbox monitoring.
27- Automate regression tests via API where possible (token validation, link health).
28- Store QA evidence (screenshots, logs) alongside sequence assets for audits.
29
30---