Consent Mode v2: Technical Guide and Requirements

Consent Mode v2 is a Google-developed API that communicates user consent choices from a website or app to Google tags. It adjusts the behavior of Analytics and Ads services based on whether a visitor accepts or denies specific cookies. This tool allows marketers to maintain measurement accuracy through data modeling even when users opt out of tracking.

Entity Tracking

• Consent Mode v2: A communication protocol that sends user consent signals to Google tags to adjust data collection behavior.
• ad_user_data: A parameter introduced in v2 that sets consent for sending user data related to advertising to Google.
• ad_personalization: A parameter introduced in v2 that sets consent for personalized advertising and remarketing.
• Basic Consent Mode: An implementation where Google tags remain blocked and send no data until a user grants consent.
• Advanced Consent Mode: An implementation where tags load immediately and send cookieless pings if consent is denied, allowing for data modeling.
• Cookieless Pings: Metadata signals sent to Google without accessing browser storage to help fill data gaps through modeling.
• Digital Markets Act (DMA): European legislation that identifies digital gatekeepers and requires stricter user consent for data processing.
• Consent Management Platform (CMP): A tool or "banner" used to obtain and manage user consent preferences on a digital property.

What is Consent Mode v2?

Consent Mode v2 is an update to Google’s original consent framework. It adds new requirements for how advertisers handle data in response to [strengthening enforcement of EU user consent policy] (Google Developers).

Unlike a cookie banner, it does not collect consent itself. Instead, it acts as a translator between your Consent Management Platform (CMP) and Google services like Ads and Analytics. The update introduces two mandatory parameters for those using advertising features: ad_user_data and ad_personalization.

Why Consent Mode v2 matters

Implementing this protocol is no longer optional for many practitioners. Failure to activate it results in significant measurement limitations.

• Compliance requirements: Implementation is [required by March 2024] (Simo Ahava) for websites collecting data for audience building or remarketing in the European Economic Area (EEA).
• Legal alignment: It helps businesses comply with the [Digital Markets Act (DMA)] (Vaimo).
• Data Modeling: It enables Google to estimate the behavior of non-consenting users. This fills gaps in reports that would otherwise show as missing traffic or conversions.
• Ad Performance: Without it, no data is sent to advertising platforms, which decreases audience creation and remarketing capabilities.
• Measurement Uplift: Google measurement products provide more accurate reporting once they have [at least 7 full days of data to report uplift] (Google Ads Help).

How Consent Mode v2 works

The system operates through a specific sequence of "default" and "update" commands.

1. Set Defaults: Before any tags fire, the site sets a default state (usually denied) for all consent parameters based on regional requirements.
2. User Interaction: The visitor interacts with a consent banner.
3. Update State: The CMP sends an update command to the Google tag API with the user's actual choices.
4. Tag Adjustment: Google tags change their behavior. If consent is granted, they use cookies; if denied, they send cookieless pings or remain silent depending on the implementation mode.

Implementation Modes

You can choose between two primary methods of setup.

Best practices

• Use a Google-certified CMP: Certified platforms often include automated integrations for v2 parameters, which reduces manual coding errors.
• Set region-specific defaults: Use the region parameter to apply strict denied defaults for EEA users while maintaining standard measurement for other regions.
• Fire commands in order: The default command must execute before the Google tag (gtag.js) or Tag Manager snippet loads to avoid "race conditions."
• Enable URL passthrough: For users who deny ad_storage, enable URL passthrough to send ad click information across pages via URL parameters instead of cookies.
• Verify with Tag Assistant: Use the Google Tag Assistant "Consent" tab to check if signals are correctly transitioning from default to update.

Common mistakes

Mistake: Calling the update command as the page unloads. Fix: Ensure consent updates logged during user interaction are sent immediately to allow the browser to complete the network request before the user leaves the page.

Mistake: Forgetting the two new v2 parameters. Fix: Update implementations to include ad_user_data and ad_personalization alongside the original ad_storage and analytics_storage.

Mistake: Broken code order in manual setups. Fix: The dataLayer and gtag function must be defined before the consent, default command, and these must all appear before the main GTM/Gtag script.

Mistake: Assuming Consent Mode replaces a cookie banner. Fix: Always use a CMP or custom banner to ask for permission; Consent Mode only communicates those choices to Google.

FAQ

What happens if I don't implement Consent Mode v2 by the deadline?

Measurement and remarketing features for EEA traffic will likely become non-functional. Google Ads will not be able to build audiences or perform personalized targeting for those users. Conversion tracking may also become less accurate as modeling benefits are lost.

What is the difference between the GCS and GCD parameters?

When debugging network requests, gcs (Google Consent Status) tracks ad_storage and analytics_storage (e.g., G111). The gcd parameter is newer and encodes all four v2 signals plus the source of the signal (default vs. update) into a string of letters like p, q, r, or v.

Do I need to resend hits when a user grants consent?

For Google Analytics 4, any hits collected on the same page while consent was denied are automatically reprocessed once consent is granted. You do not need to manually resend these hits, provided you are using Advanced Consent Mode.

Does basic mode provide any data for non-consenting users?

No. In Basic Consent Mode, tags are hard-blocked. Google receives no signals from those users, and conversion modeling must rely on a general, less detailed model rather than data specific to your site's traffic.

Is Consent Mode v2 mandatory for US traffic?

It is not currently required for US-based traffic or ads. However, practitioners often use it for US traffic to stay ahead of evolving state privacy laws and to improve reporting accuracy between consented and non-consented sessions.