Marketing Hub
Local Demo

Data Governance

Collapse / Expand

Data Governance is the operational workspace for data governance within integration and governance, where teams manage concrete records, dependencies, and execution decisions rather than static summaries. The business and compliance goal is to keep catalog, lineage, retention aligned with approved claims, consent controls, market rules, and audit evidence at every step. This page presents role-scoped actions, linked downstream impacts, and policy-aware guardrails so users can work quickly without violating promotional or safety obligations. Next, use this data governance workspace to execute governed tasks and route outcomes to connected teams.

RestrictedSection: Integration FabricSeed: 20260224

Access Boundaries

SSO + RBAC/ABAC controls are evaluated by brand, market, function, agency zone, and risk tier before actions are enabled.

Field Surfaces: Approved-only enforcedExternal Partner: Submit-onlyRisk Tier Scope: Low/Moderate/High/Critical
Data Governance: Catalog Coverage
54+5%
Data Governance: Lineage Completeness
61+1%
Data Governance: Retention Compliance
68-3%
Data Governance: Consent Mapping
75-7%
Data Governance: Env Separation
82+6%
Data Governance: Audit Confidence
89+2%

Operational Focus

  • Track data lineage across connectors.
  • Validate consent propagation.
  • Review dev/test/prod separation controls.

What To Do Next

  • Approve retention update.
  • Resolve catalog gap.
  • Export governance report.

Data Governance Studio

Manage catalog, lineage, retention, and consent overlays with environment separation signals.

IDTitleMarketOwnerStatusRiskRelated
GOV-0001Data Governance · Catalog entry 1ESData GovernanceDraftHighPolicy EngineConsent
GOV-0002Data Governance · Lineage chain 2JPPrivacyIn ReviewCriticalPolicy EngineConsent
GOV-0003Data Governance · Retention policy 3AUSecurityApprovedLowPolicy EngineConsent
GOV-0004Data Governance · Env separation 4BRData GovernanceActiveModeratePolicy EngineConsent
GOV-0005Data Governance · Catalog entry 5MXPrivacyBlockedHighPolicy EngineConsent
GOV-0006Data Governance · Lineage chain 6SGSecurityEscalatedCriticalPolicy EngineConsent
GOV-0007Data Governance · Retention policy 7USData GovernanceDraftLowPolicy EngineConsent
GOV-0008Data Governance · Env separation 8CAPrivacyIn ReviewModeratePolicy EngineConsent
GOV-0009Data Governance · Catalog entry 9UKSecurityApprovedHighPolicy EngineConsent
GOV-0010Data Governance · Lineage chain 10DEData GovernanceActiveCriticalPolicy EngineConsent
GOV-0011Data Governance · Retention policy 11FRPrivacyBlockedLowPolicy EngineConsent
GOV-0012Data Governance · Env separation 12ITSecurityEscalatedModeratePolicy EngineConsent

Page-Specific Data

Governance data tracks catalog lineage, retention controls, and environment separation. Current page path: /data-governance.

HomeHelpSettings

Relationship Graph

Linked entities are enabled so users can traverse parent-child dependencies and downstream impacts without manual lookup.

Command CenterSearch

Data Governance Tools

Lineage Tracer

Trace lineage from source to activation.

Event BusAudit
Retention Policy

Configure retention and legal hold.

SettingsHelp
Execution StepOwnerETA
Validate inputOps5m
Policy checksCompliance8m
Route next actionWorkflow3m

Integration Fabric + Governance

Connector catalog includes CRM, DAM or PromoMats, marketing automation, CMS, warehouse, consent management, and PV system endpoints.

ConnectorLatencyFailuresRetriesMappingDQ
CRM210ms22HealthyPass
DAM/PromoMats430ms43PartialWarn
Marketing Automation300ms11HealthyPass
CMS270ms22HealthyPass
Data Warehouse/Lakehouse520ms32PartialWarn
Consent Mgmt180ms00HealthyPass
PV Handoff190ms11HealthyPass

Event log filters: connector, market, severity, policy impact, retry state.

Data Governance

Catalog, lineage, retention, consent policy overlays, and simulated env separation (dev/test/prod).

Environment: devEnvironment: testEnvironment: prod

Consent rules are propagated to activation and audience publishing services before deployment artifacts are generated.

Governance Notes

  • Every approval, publication, policy block, and AI output writes an audit event.
  • Consent and frequency caps are evaluated before deployment packaging.
  • Expiry and withdrawal controls maintain cross-channel evidence status.
  • Safety routing is always flag-and-route with human adjudication.

Geo Coverage

US1,820 active
UK640 active
DE550 active
JP730 active
BR500 active
AU320 active

Seed Coverage Summary

brands: 8campaigns: 30briefs: 200assets: 6,000components: 20,000claims: 2,500references: 8,000markets: 12localizationJobs: 1,500mlrPackages: 15,000reviewSteps: 60,000annotations: 200,000interactionsRollup: 2,000,000socialSignals: 50,000aeSignals: 1,500experiments: 5,000reports: 3,000connectors: 250auditLog: 300,000