Skip to main content

Consent

16 min read

Google Consent Mode V2 Explained (+ Setup Checklist)

By Shreya July 10, 2025

Google Consent Mode V2 Explained (+ Setup Checklist)

Google Consent Mode V2 is a powerful mechanism designed to manage how Google’s advertising and analytics services operate based on user consent. This updated version aligns with the requirements of various privacy frameworks and regulations.

This article will explain how Google Consent Mode V2 works, highlight its key features, and compare it to the original version. We will also discuss the implications of not enabling it, provide implementation tips, and share best practices for ensuring compliance and optimizing data collection. Learn how Consent Mode V2 can help you balance user privacy with essential data insights.

What is Google Consent Mode v2?

Google Consent Mode is a tool developed by Google to manage how its advertising and analytics services operate based on user’s consent. It ensures that basic user interaction can still be tracked without compromising privacy using its prediction modelling even if users don’t give full consent.

It was first introduced in 2020 to comply with GDPR for Google Analytics and Google Ads data collection. The updated version, Google Consent Mode V2, aligns with the new Digital Markets Act (DMA), which came into effect in March 2024.

Consent Mode does not replace the need for a Consent Management Platform (CMP) or a cookie consent banner. Instead, it works alongside these tools to ensure Google tags and scripts operate according to user consent preferences. This allows websites to comply with privacy regulations like EU GDPR while maintaining essential analytical data.

How does Google Consent Mode v2 work?

Google Consent Mode v2 works by adjusting how Google tags behave based on user consent choices. The mode has four key parameters:

  • ad_storage: Controls the storage of user’s personal data for advertising.
  • analytics_storage: Manages the storage of data for analytics.
  • ad_user_data: Pertains to the collection and usage of user data for advertising.
  • ad_personalization: Allows the use of user data to personalize ads.

Here’s how the process works:

  1. User sees a consent banner:
    When a visitor lands on your website, the Consent Management Platform (CMP) prompts them to accept or reject different types of data use.
  2. Consent preferences are sent to Google<br Based on the user’s selection, the CMP sends consent signals to Google tags (e.g., Analytics, Ads).
  3. Google tags adapt accordingly
    Tags like Google Analytics 4 or Google Ads change their behaviour:
    • If ad_storage is denied, ad cookies are not set
    • If analytics_storage is denied, analytics tracking is disabled
  4. Data is handled based on consent
    Only the data permitted by the user is collected, processed, or stored—ensuring GDPR and DMA compliance.
How google consent mode v2 works - infographic

Download this infographic

Basic Consent Mode

In this mode, Google tags remain inactive until the user interacts with the consent banner. Once users consent, Google tags send consent information to Google and begin collecting data. Without consent, no data is sent to Google, and Google Ads relies on a general conversion model.

Advanced Consent Mode

In this mode, Google tags load immediately but remain inactive until consent is given. While waiting for user input, they send minimal data (cookieless pings). Once consent is granted, full measurement data is sent to Google, allowing for more accurate conversion modelling.

What is the difference between Google Consent Mode v1 and v2?

Consent Mode V1 introduced basic controls over cookies using two parameters:

  • ad_storage: manages cookies for advertising
  • analytics_storage: controls cookies for analytics

These settings allowed websites to adjust tracking based on whether users consented.

Consent Mode V2 builds on this with:

  • More granular control over data usage
  • Two new parameters:
    • ad_user_data: governs sending user data to Google for ads
    • ad_personalization: controls ad personalization features
  • Support for both Basic (limited data) and Advanced (consent-adjusted data) modes

This upgrade improves GDPR & DMA compliance, especially for sites using Google Ads or Analytics.

Is Consent Mode V2 mandatory?

Yes, Google Consent Mode v2 is essential for websites to comply with strict data privacy regulations like GDPR and the Digital Markets Act. If not enabled, you risk several negative consequences:

  • Non-compliance: Your website could be in violation of data privacy laws, leading to hefty fines and legal issues.
  • Data loss: Without Consent Mode, you might collect and process user data without proper consent, resulting in data loss.
  • Inaccurate analytics: Your analytics, such as audience or conversion data will be unreliable as it won’t accurately reflect user behavior due to missing consent-based data. This will affect the conversion tracking.
  • Reduced ad revenue: Ad performance may decline as targeted advertising relies on user data, which is restricted without proper user consent.
  • Damaged reputation: Failure to prioritize user privacy can harm your website’s reputation and trust among visitors.

How to implement Google Consent Mode v2

1. Manual Implementation

While technically feasible, manual implementation is generally not recommended due to its complexity and potential for errors. It involves modifying your website’s code to include Consent Mode logic for each Google tag.

Steps involved:

  • List all Google tags on your website (Google Analytics 4, Google Ads, Google Tag Manager, etc.).
  • Define different consent states (granted, denied, unknown).
  • Write code to check consent status and modify tag behaviour accordingly.
  • Ensure correct behaviour in all consent scenarios.

2. Google Tag Manager (GTM)

GTM offers a more manageable approach to implementing Consent Mode v2. It provides a user-friendly interface for managing and deploying tags.

Steps involved:

  • Define variables to store consent status (e.g., ‘consent_granted’).
  • Add Consent Mode parameters to your Google tag configurations.
  • Use triggers to control when tags fire based on consent status.

More details here.

3. Using CookieYes CMP

CMPs like CookieYes simplify the process by handling consent management and integrating with Google Consent Mode. As a Google-certified CMP, CookieYes supports IAB TCF v2.2 integration, enabling automatic compliance with Google Consent Mode v2. 

Here’s how you can implement Consent Mode v2 using CookieYes:

  • Install a cookie banner using CookieYes and enable Google Consent Mode in settings.
  • Choose either Google Tag Manager (GTM) or a custom script for integration.
  • For GTM, create a new tag, add the CookieYes template, and configure the settings. For custom script, add the provided script along with the GTM and CookieYes scripts on your site.
  • Set up consent categories and regions as needed.
  • Verify the functionality to ensure proper implementation.

Every time website users make a consent choice, CookieYes signals Google to adjust tag behaviour accordingly.

Here is how to implement Google Consent Mode v2 using CookieYes.

Benefits of using a CMP:

  • Simplified implementation
  • Pre-built integrations
  • User-friendly interface
  • Compliance with data privacy regulations

Worried about Consent Mode v2?

Implement Google Consent Mode with ease using CookieYes

Try for free

14-day free trialCancel anytime

How to check if Google Consent Mode is enabled?

Want to verify if your website has implemented Google Consent Mode correctly?

You can use our free Google Consent Mode Checker to scan your site in seconds.

Here’s how:

  1. Open the ool
  2. Enter your website URL
  3. Click “Scan website” to see if Consent Mode v2 signals are detected

Try it now and make sure you’re compliant.

Common issues faced in Consent Mode v2 implementation

Here are some common issues you may face while or after implementing Consent Mode v2:

  • Misconfiguration of consent settings can make the consent tab appear empty, leading to data loss and compliance issues.
  • Incorrect default consent settings can cause Google tags not to fire correctly, impacting data collection and analysis.
  • Issues with integrating Google Consent Mode with CMPs can lead to discrepancies in consent management and the inability to update user preferences.
  • If other tags run before consent is recorded, it can cause measurement gaps and inaccuracies in data reporting.
  • Managing cookies and identifiers while respecting user consent can be complex, requiring careful attention to ensure compliance and accurate data handling.

CookieYes users can use the Google Consent Mode troublehsooting guide to ensure error-free implementation.

Best practices for implementing Google Consent Mode v2

Here are some of the best practices to implement Google Consent Mode v2:

  • Understand the basics of Consent Mode
  • Determine how to obtain and manage user consent effectively
  • Select the best approach based on technical expertise and website complexity
  • If using a CMP, ensure it’s Google-certified and IAB TCF-compliant
  • Ensure correct configuration of settings, such as default consent states, triggers, and variables, according to Google guidelines
  • Verify that the data collection and ad serving are correct based on consent
  • Check for potential issues and errors
  • Monitor consent rates and user behaviour and track the impact on website performance and ad revenue
  • Stay updated on data privacy regulations and Consent Mode requirements

How to configure Google Consent Mode v2 for GDPR compliance?

  • Review Google’s guidelines: Understand the technical details and new features of Google Consent Mode v2 directly from Google’s official documentation.
  • Audit data and consent management practices: Assess your existing consent management practices to align with Consent Mode v2’s integration capabilities.
  • Implement granular consent settings: Ensure that your CMP can handle the granular consent settings introduced in Consent Mode v2. These settings allow users to choose their preferences regarding various types of cookies, such as analytics or advertisement cookies.
  • Ensure good UX: Update your CMP to handle consent updates effectively, ensuring data collection respects user consent without disrupting their experience.
  • Enable consent sharing: Configure settings so user consent preferences persist over multiple sessions. This reduces consent fatigue by preventing repeated prompts for consent.
  • Enhance integration with other services: Ensure that Consent Mode v2 is compatible with your website’s other Google services and third-party platforms. This ensures that consent preferences are consistently respected and applied across all services.
  • Test and validate: Before going live, thoroughly test the implementation in various scenarios to ensure compliance and functionality. This includes checking how the consent mode interacts with different types of cookies and user settings.
  • Communicate changes to users: Transparently disclose the updated consent management practices to users. This fosters trust and ensures compliance by clearly explaining how websites manage and protect user data.
  • Monitor and maintain compliance: Regularly review and update your consent management practices to ensure ongoing compliance with GDPR and other relevant data protection regulations.

FAQ on Google Consent Mode v2

How do I update to Google Consent Mode v2 from an older version?

You can update Consent Mode v1 to v2 by configuring your CMP to handle the new consent parameters. Most CMPs offer automated updates or provide clear instructions on how to upgrade to v2. You should also modify your code or GTM triggers and tags to incorporate the new consent parameters (ad_user_data and ad_personalization).
Existing users of CookieYes can easily upgrade from Consent Mode v1 to v2.

How does Google Consent Mode v2 impact analytics and ad performance?

Google Consent Mode v2 impacts analytics by potentially reducing data volume and accuracy due to user consent choices. 
Ad performance tracking is affected by limited conversion data and personalized ad targeting. Businesses must balance privacy compliance with data collection by optimizing consent prompts, using privacy-friendly tools, and focusing on high-value metrics.

Is Google Consent Mode v2 useful when running ads in the US?

Google Consent Mode v2 is not mandatory in the United States. It was introduced to support compliance with European privacy laws such as the GDPR and the Digital Markets Act (DMA).
However, enabling it can still be beneficial if:

  • Your website receives traffic from both the US and EU: Consent Mode can help manage regional compliance more efficiently.
  • You want to stay prepared for evolving US privacy laws: States like California, Colorado, and others are introducing stricter data regulations, and Consent Mode may eventually play a role here.
  • You need better visibility into consented vs. non-consented data: This can improve reporting accuracy in Google Analytics and Ads.
  • You already use a CMP: If your CMP supports Consent Mode, implementation may be straightforward.
In short, while Consent Mode v2 isn’t required for US-based ads, it can offer long-term value—especially if you’re operating in multiple regions or planning ahead for regulatory changes.

Photo of Shreya

Shreya

Shreya is the Senior Content Writer at CookieYes, focused on creating engaging, audience-driven blog posts and related content. Off the clock, you’ll find her happily lost in the world of fiction.

Keep reading

Featured image of UK ICO Cookie Guidance Just Changed: What Your Website Must Do Now

ConsentCookies

UK ICO Cookie Guidance Just Changed: What Your Website Must Do Now

If you run an online service accessible from the UK, you need to know about …

Read more
Featured image of Guide to Alabama Personal Data Protection Act

Privacy Laws

Guide to Alabama Personal Data Protection Act

Alabama recently passed its comprehensive consumer privacy law. Governor Kay Ivey signed Alabama HB 351 …

Read more
Featured image of GDPR and AI Act: Similarities, Differences, and Overlaps

GDPR

GDPR and AI Act: Similarities, Differences, and Overlaps

Data protection is not new. The GDPR has been shaping how organisations handle personal data …

Read more

Show all articles