Consent Mode Overview
Google Consent Mode enables privacy-compliant tracking by adjusting Google tag behavior based on user consent choices. When users decline cookies, tags respect those choices while providing modeled conversions.
Consent Mode v2 adds required consent signals for EEA users using Google advertising services. Implementation is mandatory for personalized advertising to European users.
v2 Requirements
New Consent Signals
Consent Mode v2 introduces ad_user_data and ad_personalization signals alongside existing analytics_storage and ad_storage signals.
All four signals must be implemented for compliant EEA advertising.
EEA Compliance
European Economic Area users require explicit consent collection. Consent Mode communicates consent status to Google services.
Implementation Deadline
Google requires v2 implementation for continued EEA personalized advertising. Check current deadlines for specific requirements.
Basic vs Advanced Mode
Basic mode blocks all tags until consent. Advanced mode sends cookieless pings enabling conversion modeling.
Our [analytics services](/services/digital-marketing) include Consent Mode implementation.
Implementation Guide
Tag Manager Setup
Configure Consent Mode in Google Tag Manager. Set default consent states and update consent triggers.
Default States
Set default consent states appropriately. EEA users should default to denied; other regions may default to granted based on requirements.
Region-Specific Defaults
Configure region-specific defaults. Different jurisdictions have different consent requirements.
Consent Updates
Implement consent update mechanisms. When users grant or revoke consent, communicate changes to Google tags.
Implementation Methods
Implement through Tag Manager, gtag.js, or CMP integrations. Choose based on existing infrastructure.
Consent Platform Integration
CMP Compatibility
Ensure your Consent Management Platform supports Consent Mode v2. Major CMPs offer native integration.
Signal Mapping
Map CMP consent categories to Consent Mode signals. Advertising consent should trigger ad_storage and ad_user_data updates.
Implementation Testing
Test CMP and Consent Mode integration thoroughly. Verify signals update correctly for different consent choices.
IAB TCF Integration
Integrate with IAB Transparency and Consent Framework where applicable. TCF compliance may be required for certain advertising.
Conversion Modeling
Modeling Eligibility
Qualify for conversion modeling by implementing Advanced Consent Mode. Basic mode does not enable modeling.
Data Requirements
Modeling requires sufficient consented data. Minimum thresholds vary by conversion volume and time period.
Modeled Conversions
Google estimates conversions from non-consenting users based on consenting user patterns. Modeled conversions fill measurement gaps.
Reporting Impact
Understand modeling impact on reporting. Total conversions include both observed and modeled conversions.
Bidding Integration
Smart bidding incorporates modeled conversions. Modeling maintains optimization despite consent gaps.
Validation and Testing
Tag Assistant
Use Google Tag Assistant to validate Consent Mode implementation. Check consent signal transmission and tag behavior.
Consent Flow Testing
Test complete consent flows. Verify behavior for consent granted, denied, and updated scenarios.
Reporting Validation
Validate reporting post-implementation. Compare conversion volumes and ensure modeling activates appropriately.
Compliance Verification
Verify legal compliance with privacy counsel. Technical implementation must align with compliance requirements.
Ongoing Monitoring
Monitor Consent Mode ongoing. Consent rates and modeling quality metrics indicate implementation health.
Ready to implement Consent Mode v2? Our [marketing solutions](/solutions/marketing-services) ensure privacy-compliant advertising.