OneTrust CMP Integration with Google Consent Mode v2
OneTrust CMP with Google Consent Mode v2
📌Introduction
A global enterprise with operations in 15 countries needed to implement a unified consent management solution using OneTrust that would correctly pass Consent Mode v2 signals to Google while respecting different regulatory requirements across jurisdictions.
❗The Problem
The company's existing OneTrust implementation was not correctly mapped to Google's Consent Mode v2 signal framework. The four required consent parameters (analytics_storage, ad_storage, ad_user_data, ad_personalization) were not being sent, causing Google to default all signals to denied for EU users.
🔍Identifying the Causes
OneTrust's GTM integration was configured for legacy Consent Mode v1 (only analytics_storage and ad_storage). The v2 upgrade requiring ad_user_data and ad_personalization signals had not been implemented. Additionally, the geo-targeting logic was not working correctly, applying EU-level consent restrictions to non-EU traffic and unnecessarily degrading data quality globally.
⚠️Consequences for the Business
EU traffic conversion modeling was completely absent — Google had no consent signal at all (defaulting to denied) rather than partial consent. Global traffic was being impacted by EU restrictions incorrectly applied. Google Ads remarketing audiences for all regions were being limited as a result.
✅Solution
Updated OneTrust GTM template to the v2 API version. Mapped OneTrust consent categories (Performance Cookies, Targeting Cookies) to all four Google Consent Mode v2 signals with correct category-to-signal mapping. Implemented geo-based default consent settings: EEA/UK defaulted to denied with user choice; non-EEA defaulted to granted. Validated across all 15 market domains.
📈Results
EU behavioral modeling activated correctly for the first time. Non-EU traffic data quality restored to 100% (previously restricted incorrectly). Remarketing audiences for all regions recovered. EU campaign performance improved by 18% as modeling filled conversion gaps previously invisible to the algorithm.
🏁Conclusion
Enterprise Consent Mode v2 implementation requires careful mapping between CMP categories and Google signal types, and precise geo-targeting logic to avoid over-restricting non-regulated traffic.
💡Key Takeaways
Consent Mode v2 requires all four signals mapped correctly. Geo-targeting defaults are critical — applying EU consent defaults globally is unnecessarily restrictive. Always validate with Google Tag diagnostic tools across multiple test geographies.