2026-02-25 · Baduno Editorial Team · 8 blog.readMin · Blog & Knowledge
Consent Mode v2: What advertisers need to know now
Without correct consent signals, Google Ads accounts lose conversion data and functionality. The obligation explained clearly.
What Consent Mode v2 is
Google's method for your website to communicate what the visitor has consented to — in four signals: storage for advertising, use for ad data, personalization, and analytics. Without these signals, Google restricts measurement and audience functions in the EEA.
The basic rules
The default state is 'denied' before the user decides. Only consent in the banner switches signals to 'granted'. Tags must wait or send in data-saving mode — never full data before the decision.
Common mistakes
Banners that are merely cosmetic while tags already fire. Consent without a real opt-out option. Signals that are never updated. Each of these variants risks data loss, warnings, or both.
Clean implementation
Default-denied in source code, granular selection in the banner, update call after decision, revocation in the footer — and a test with developer tools to ensure nothing flows before consent. That's exactly how it's implemented on this website.
Consent Mode v2 and Google Ads: Concrete Impact on Campaigns
Without correct consent signals, Google Ads restricts crucial functions. Conversion data is no longer reported, remarketing lists cannot be populated, and bid adjustments based on user behavior become ineffective. Campaigns that rely on user recognition, such as dynamic remarketing or customer match, are particularly affected. The result: fewer conversions, higher CPA, and inaccurate performance data. In the EEA, this has been mandatory for all advertisers using Google Ads since March 2024. Even if you are running only a small local campaign, the signals must be correct. A common misconception is that using Consent Mode v2 is voluntary – Google has tied access to conversion data to the transmission of correct consent signals. Without these, data models risk being switched to a data-saving basis, severely complicating the optimization of your ad spend. Therefore, regularly check your campaigns for missing signals and correct errors immediately.
The Role of the Consent Management Provider (CMP)
A CMP is mandatory for correctly implementing Consent Mode v2. The tool must be able to set and update the four signals (ad_storage, ad_user_data, ad_personalization, analytics_storage). Google has published a list of certified CMP providers – only these guarantee compatibility. When selecting, pay attention to the granularity of settings: the user must be able to confirm or reject advertising and analytics purposes separately. A simple "Allow all" button is not sufficient. Additionally, the CMP must enable withdrawal of consent and report it to Google immediately. Ensure that your CMP correctly persists the signals even after a page change or during SPA navigation (Single Page Applications). Incorrectly configured CMPs are one of the most common sources of errors – they either fire too early or do not update signals after the user's decision. Therefore, test with Google's developer tools whether the signals are in the desired state.
Consent Mode v2 in Combination with Conversion Tracking and Tag Management
The integration of Consent Mode v2 into your tag manager (e.g., Google Tag Manager) requires a clean chaining of consent check and tag triggering. Tags may only fire after valid consent; beforehand they must either send in data-saving mode (Consent Mode v2) or be blocked. In Google Tag Manager, use the consent overrides or the new Consent API that reads the signals from your CMP. For conversion tracking tags, it is essential that they query consent for ad_storage and ad_user_data. A common mistake: the conversion tag fires, but the associated consent signals are not set correctly – then the conversion is not recorded in Google Ads. Use the preview function in GTM to check the data flow. Also pay attention to custom HTML tags: these too must consider the consent signals. A clean implementation saves a lot of debugging time later and protects against data loss.
Without correct consent signals, Google Ads accounts lose conversion data and functionality. The obligation explained clearly.
Legal pitfalls and review by supervisory authorities
Consent Mode v2 is not a license for data protection violations. Consent must be effective under GDPR: informed, voluntary, specific, and revocable at any time. A CMP that only requests consent once and later allows no change is insufficient. Data transfer to third countries (e.g., USA) must also be secured by appropriate guarantees (Standard Contractual Clauses, transparency report). Supervisory authorities such as the Hamburg Commissioner for Data Protection have already imposed fines due to missing or inadequate consent solutions. Consent Mode v2 alone does not protect against warnings if the banner is opaque or pre-filled. Therefore, have your solution reviewed by a data protection expert. Document the functionality of your CMP and the configurations made. In an audit, you must be able to demonstrate that consent was actually obtained and correctly transmitted to Google. A data processing agreement (DPA) with Google is also mandatory.
Performance Effects and Load Time Optimization with Consent Mode v2
Consent Mode v2 can impact your website's load time if misconfigured. In the default-denied mode, many tag platforms like Google Tag Manager pause until visitor consent is obtained. This delays the firing of tracking and advertising tags, extending the measured load time from the user's perspective. It is crucial that your CMP obtains consent as quickly as possible without blocking the rest of the website. Therefore, an asynchronous implementation of the consent manager is mandatory: the banner must not block page rendering. Additionally, you should check whether your CMP supports a data-saving mode (e.g., anonymous pings) that reduces network activity. Another point is the GTM container: if many tags wait for consent, the queue can slow down the browser. Use the option to load non-essential tags only after consent. Also, using gtm.js or gtm.dom as triggers can help avoid blocking page rendering. Test performance with tools like PageSpeed Insights and monitor the impact of the consent implementation. An optimized solution ensures that consent signals are set correctly without compromising the user experience.
Consent Mode v2 and Server-Side Tagging: Synergies and Challenges
Combining Consent Mode v2 with server-side tagging offers enhanced data control capabilities but also places higher demands on the consent logic. In the server-side model, you can evaluate consent signals directly in the server container before forwarding data to third parties. This reduces the risk of data leaks via the client and gives you full control over data sharing. However, you must ensure that your server container correctly interprets consent signals and only triggers tags like Google Ads or Facebook when valid consent is present. To do this, forward signals from the client container via event data or use a server-side consent API. A common mistake is that the server container does not check consent and sends data anyway. Therefore, you must consistently implement the consent logic both on the client and server side. Additionally, latency increases because data must first pass through your server. However, a well-configured server-side tagging setup with Consent Mode v2 is future-proof because it works independently of browser restrictions like Intelligent Tracking Prevention. Therefore, allocate sufficient resources for maintenance and logging to ensure compliance at all times.
Technical Implementation in Google Tag Manager: Consent Overrides and Triggers
Correct implementation of Consent Mode v2 in Google Tag Manager (GTM) requires a well-thought-out interplay of consent overrides and triggers. First, you must connect your CMP's consent settings to GTM. Use the consent API to read the four signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) from the CMP. In GTM, set consent overrides per tag: for each tag, define which consents are required before the tag fires. For example, a Google Ads conversion tag requires ad_storage and ad_user_data to be 'granted', while an analytics tag requires analytics_storage. Without this setting, tags fire regardless of consent. Additionally, configure triggers for the data-saving mode: before consent, tags must either be blocked or send in data-saving mode (Consent Mode v2). To do this, create a trigger that reacts to consent changes and only releases tags after consent is granted. A common mistake is the lack of a consistent default-denied setting. Therefore, set the default values to 'denied' in GTM or directly in the page code. Use GTM Preview to check whether tags really do not fire before consent and whether the signals are correctly updated after the decision. This technical discipline protects against data loss and ensures that your conversion measurement works reliably.
Consent Mode v2 and Google Analytics 4: Impact on Data Collection
Consent Mode v2 affects not only Google Ads but also Google Analytics 4 (GA4). For GA4, the signals analytics_storage and ad_personalization are relevant. analytics_storage controls whether cookies may be stored for analytics purposes. Without consent, GA4 continues to send data, but without cookies – this leads to reduced user numbers and limited analytical functions, especially with regard to user behavior and retention. ad_personalization concerns the use of analytics data for personalized advertising. In default-consent mode, conversions and events are transmitted with reduced information, which diminishes data quality. For precise reporting, you must therefore ensure that analytics_storage signals are set correctly. Implement your CMP so that consent for analytics purposes is requested separately from advertising purposes. Default-denied also applies to analytics_storage. After consent is granted, the CMP updates the signal to ‘granted’, and GA4 can set cookies. A common mistake is the lack of this separation: many banners combine all purposes into a single 'Allow all' button. This does not comply with GDPR requirements and can lead to data distortions. Test with GA4 DebugView whether events arrive in default-consent mode before consent and fully after. Only then can you ensure that your analyses are based on valid data.
blog.faqT
Do I need to use Consent Mode v2 if I only use Google Analytics and not Google Ads?
Yes, Consent Mode v2 is also important for Google Analytics. Analytics requires the analytics_storage signal to capture data anonymously without consent. Without correct signals, Google Analytics cannot deliver detailed reports, and data quality decreases. Additionally, proper implementation paves the way for future use of Google Ads.
Can I set up Consent Mode v2 on an existing website without affecting the tags?
Yes, subsequent integration is possible but requires careful planning. You must integrate your CMP, set the default-denied rules in the source code, and instruct all tags to wait for consent. Use Google Tag Manager preview to ensure no tags fire before the decision. A rollout in a test environment is recommended.
