data-governance
Use when defining data contracts, consent policies, and monitoring for automation programs.
When & Why to Use This Skill
The Automation Data Governance skill is a comprehensive framework designed to ensure data integrity, regulatory compliance, and operational reliability within automated systems. It provides structured methodologies for defining data contracts, managing consent policies (GDPR/CCPA), and implementing proactive monitoring to prevent data-driven failures in cross-system workflows.
Use Cases
- 1. Cross-System Data Integration: Establishing formal data contracts and identity resolution protocols when syncing customer data between CRMs, CDPs, and marketing automation platforms.
- 2. Compliance & Consent Management: Auditing and enforcing regional consent rules and suppression logic across multiple communication channels like Email, SMS, and In-App messaging.
- 3. Proactive Data Monitoring: Implementing automated 'kill switches' and alert systems to detect schema changes, data latency, or null value spikes before they impact live automation journeys.
- 4. Incident Root Cause Analysis: Utilizing structured templates and incident logs to investigate data quality issues and maintain a clear audit trail for change management.
| name | data-governance |
|---|---|
| description | Use when defining data contracts, consent policies, and monitoring for |
Automation Data Governance Skill
When to Use
- Launching new journeys requiring cross-system data sharing.
- Auditing consent/suppression logic across email/SMS/in-app.
- Investigating data quality incidents impacting automation.
Framework
- Data Contracts – document required fields/events, owners, freshness SLAs, fallback behavior.
- Consent & Compliance – track opt-in types, regional consent, TTL, audit trails.
- Identity Resolution – ensure consistent IDs across product, CRM, MAP, CDP.
- Monitoring – dashboards/alerts for data latency, schema changes, null spikes.
- Change Management – versioning, rollback, and communication paths.
Templates
- Data requirements matrix (journey → fields/events → source → owner → SLA).
- Consent policy doc (channel, region, legal basis, suppression rules).
- Incident log + RCA template.
Tips
- Set automated kill switches when critical fields are stale or missing.
- Collaborate with security/legal on retention + privacy impact assessments.
- Align governance cadences with quarterly automation retros.