Compliance & Governance
Implement privacy controls and data governance policies with MetaRouter's Advanced Consent Enforcement. Ensure downstream vendors only receive data according to each user's consent preferences.
Advanced Consent Enforcement (ACE)
MetaRouter's Advanced Consent Enforcement helps your organization achieve compliance with GDPR, CCPA, and similar privacy regulations. ACE integrates seamlessly with your existing Consent Management Platform (CMP) to ensure that downstream vendors only receive data according to each user's consent selections—little or no extra code required on your end.
How It Works
Your website loads with a consent banner from your CMP (OneTrust, Cookiebot, etc.)
User makes their consent selections—Accept All, Decline All, or category-specific choices
A first-party consent cookie is set with their opt-in/opt-out preferences
MetaRouter's Sync Injector reads the consent cookie and imports the consent data
If a user opts out of a vendor, identifiers for that vendor are purged and no API calls fire
All Analytics.js events are enriched with consent preferences, and each integration enforces them individually
Key Features
Implicit & Explicit Tracking
Choose your tracking mode based on regulatory requirements. Implicit tracking begins collection before consent interaction (CCPA-style opt-out), while explicit tracking requires user opt-in before any collection (GDPR-style opt-in).
Native OneTrust Support
Out-of-the-box integration with OneTrust. Simply enter your OneTrust cookie name in the File Builder and MetaRouter automatically reads and enforces consent preferences across all your integrations.
Google Consent Mode v2
ACE meets Google's Consent Mode v2 requirements. Simply create the required category structure within ACE's interface—no additional implementation needed.
Universal CMP Support
MetaRouter can read from any consent cookie matching the required format, ensuring compliance is always enforced regardless of which CMP you use—OneTrust, Cookiebot, TrustArc, or your own custom solution.
Quick Setup
In your MetaRouter dashboard, navigate to Settings → Consent Settings and create categories that match your CMP's consent cookie identifiers (e.g., C0001 for Necessary, C0004 for Marketing).
In the Analytics.js File Builder section of the UI, assign whether a data pipeline should follow Implicit or Explicit tracking based on your compliance requirements.
If you are using OneTrust, ensure the name of your OneTrust cookie is entered in the Analytics.js File Builder (commonly OptanonConsent). If you are not using OneTrust, ensure your existing cookie or a new cookie set by you matches the required cookie formatting.
When adding integrations to your data pipelines, assign the appropriate consent categories from those you created in step 1. Events will only flow to integrations that match the user's consent preferences.
In your File Builder settings, assign consent categories to each ID Sync. Syncs will only fire for vendors the user has approved.
Related Topics
What's Next?
You've completed the Quickstart guide. Explore more resources: