Back to Details

qa-gates

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email QA Gates Skill

Email QA Gates 技能

When to Use

适用场景

  • Prior to activating new nurture or lifecycle programs.
  • After major changes to segmentation, personalization tokens, or deliverability settings.
  • During post-incident reviews to ensure fixes remain in place.
  • 激活新的培育或生命周期营销项目之前。
  • 对细分规则、个性化令牌或送达率设置进行重大修改之后。
  • 事件复盘期间，确保修复措施持续生效。

Framework

验证框架

  1. Content & Personalization – placeholders resolved, links tracked, dynamic content fallback tested.
  2. Data & Routing – trigger logic, smart lists, suppression rules, CRM fields synced.
  3. Compliance – footer language, preference center links, consent status, regional routing.
  4. Tracking & Analytics – UTM/tagging consistency, BI/warehouse pipes, alert webhooks.
  5. Monitoring Hooks – dashboards referenced, alert thresholds set, rollback plan documented.
  1. 内容与个性化 – 占位符解析正常、链接可追踪、动态内容回退机制已测试。
  2. 数据与路由 – 触发逻辑、智能列表、排除规则、CRM字段同步正常。
  3. 合规性 – 页脚声明、偏好中心链接、同意状态、区域路由设置合规。
  4. 追踪与分析 – UTM/标签设置一致、BI/数据仓库管道正常、告警Webhook配置正确。
  5. 监控钩子 – 关联仪表盘已配置、告警阈值已设置、回滚计划已记录。

Templates

模板

  • QA runbook with owner, status, evidence links for each checklist item.
  • Proofing matrix (persona × email × device × ISP) for screenshot validation.
  • Launch readiness form requiring sign-off from marketing, ops, legal, and RevOps.
  • QA运行手册：包含每个检查项的负责人、状态及证据链接。
  • 校对矩阵（角色 × 邮件 × 设备 × 运营商）：用于截图验证。
  • 启动就绪表单：需要营销、运营、法务及RevOps团队签字确认。

Tips

小贴士

  • Pair with 
    deliverability-ops
    to confirm authentication and inbox monitoring.
  • Automate regression tests via API where possible (token validation, link health).
  • Store QA evidence (screenshots, logs) alongside sequence assets for audits.
  • 与
    deliverability-ops
    配合使用，确认认证设置及收件箱监控状态。
  • 尽可能通过API自动化回归测试（如令牌验证、链接健康检查）。
  • 将QA证据（截图、日志）与序列资产一同存储，以备审计。