Strategy / June 3, 2026

Google Ads Consent Mode V2: How to Audit Your Setup Before It Costs You Conversions

Your Google Ads conversions might be lying to you. Here is how to find out, and what to do about it before the June 15 deadline.

Maxim Baeten
Maxim Baeten

12 min read

Your Google Ads conversions might be lying to you. Many advertisers have watched their conversion numbers drop by 30%, 50%, or even 90% without touching a single campaign setting. No bid changes. No budget cuts. No new competitors. Just a slow, silent bleed of data that makes every optimization decision unreliable.

The cause is almost always invisible: a Consent Mode V2 misconfiguration that quietly suppresses conversion data. Your consent banner looks fine. Your tags appear to load. But under the surface, Google is receiving no consent signals at all. With Google's June 15, 2026 consent changes taking effect in days, this is not something you can delay. Here is how to audit your setup, spot the problems, and fix them before you lose more data.

Why your setup might be broken right now

The frustrating thing about consent mode failures is that everything looks normal on the surface. Your consent banner appears. Visitors click "Accept." Your Google Tag Manager container shows tags firing. But the consent signals never reach Google's tags. Here are the most common failure modes we see.

1. The technical disconnect

Your consent banner collects visitor choices, but it does not pass those signals to Google's tags. The CMP stores the preference in a cookie or local storage. The Google tags never receive the consent update. This is the most common failure we encounter, and it is completely invisible without a technical audit.

2. CMP update broke the integration

Your consent management platform pushed an update. The banner still works. But the integration with Google Tag Manager Consent Mode broke silently during the update. No error messages. No alerts. Just a quiet disconnect that starts eroding your conversion data from the moment it happens.

3. Missing default consent state

Your tags fire before any consent state is set. Google requires a default consent state (typically "denied" for EU visitors) to be configured before any tags load. Without this default, Google treats all traffic as non-consented, even after visitors click "Accept."

4. Tag loading order issue

Google Tag Manager loads before the consent framework initializes. This has become a bigger concern following recent German court rulings on tag manager loading behavior. If GTM fires before consent is obtained, it can create compliance problems and also break the consent signal flow.

5. V2 parameters not configured

The ad_user_data and ad_personalization parameters are specific to Consent Mode V2. If your setup only handles the older ad_storage and analytics_storage parameters, Google treats the V2 signals as permanently denied. Your setup might have worked perfectly under V1 and still be broken under V2.

A real case: 90% conversion drop overnight

One of our clients saw conversions drop by 90% overnight. The consent banner looked fine visually. Tags appeared to be firing. The problem was invisible: consent signals were not reaching Google's tags after a CMP update. By the time we identified and fixed the issue, only about 40% of the lost conversions were recoverable through Google's behavioral modeling. The rest was permanently gone. Weeks of campaign optimization data, lost without a trace.

The June 15, 2026 changes you need to know

On June 15, 2026, Google restructures how advertising data flows through its ecosystem. These are not minor adjustments. They change the fundamental relationship between consent signals and ad data collection across Google's entire platform.

  • arrow_forwardad_storage becomes the single governing parameter. In Consent Mode, ad_storage will be the primary signal that controls whether advertising data is collected. Other parameters still exist, but ad_storage takes precedence.
  • arrow_forwardGoogle Analytics can no longer override Google Ads consent behavior. Previously, some configurations allowed GA4 consent settings to influence how Google Ads collected data. That bridge is removed. Google Ads consent must be handled independently.
  • arrow_forwardGoogle Signals loses its role as co-controller of ad data collection. Google Signals has been a fallback mechanism for some advertisers. After June 15, it will no longer serve as an alternative path for advertising data collection.
  • arrow_forwardGaps in your consent setup break everything downstream. Attribution, remarketing audiences, and conversion tracking all depend on proper consent signals. If your setup has gaps, all three break simultaneously.

This is not theoretical

Google has already disabled conversion tracking for non-compliant EU/UK accounts. No warnings. No grace period. Advertisers discovered the problem only when their conversion numbers dropped to near zero. If your Google Ads consent mode setup has gaps, the June 15 changes will expose them immediately.

How to fix the most common problems

Once you have identified the issue, the fixes are usually straightforward. Here are the most common problems and their solutions.

CMP is not passing consent signals

Check your CMP's Google Consent Mode integration settings. Most certified CMPs (Cookiebot, CookieYes, Usercentrics, OneTrust) have built-in support for Consent Mode V2, but the integration needs to be explicitly enabled. Look for a "Google Consent Mode" or "TCF v2.2" toggle in your CMP's dashboard. After enabling it, re-test with Tag Assistant to confirm signals are flowing.

Default consent state is missing

Add the default consent configuration in Google Tag Manager or in your gtag.js snippet. This code must run before the Google tag loads. In GTM, use the "Consent Initialization" trigger type, which fires before all other triggers. Set ad_storage, ad_user_data, ad_personalization, and analytics_storage to "denied" as the default for EU visitors. Your CMP will then update these to "granted" when consent is given. For detailed implementation guidance, refer to Google's consent mode documentation.

Enhanced Conversions are not set up

Enable enhanced conversions in your Google Ads account under Tools, then Conversions, then Settings. You can implement them through Google Tag Manager, the global site tag, or the Google Ads API. The GTM method is the simplest for most advertisers. Enhanced conversions supplement your consent mode setup by providing an additional signal path that does not depend on cookies.

Behavioral modeling shows low numbers

If your modeled conversions are lower than expected, confirm you are using Advanced Consent Mode rather than Basic. Basic mode sends no data at all from non-consenting users, which gives Google nothing to model from. Advanced mode sends cookieless pings that provide the foundation for behavioral modeling. Additionally, ensure you have enough consented traffic volume. Google needs a statistically meaningful sample of consenting users to build accurate models for the non-consenting group.

What aubado monitors for you

aubado's Google Ads monitoring tracks your conversion signals and flags anomalies. If your tracked conversions suddenly drop, you will know about it the same day, not months later when you finally notice your CPA has doubled. Budget Control catches spending anomalies, and the Google Ads Optimization Specialist surfaces conversion tracking issues as part of its regular analysis.

The goal is simple: catch problems like consent misconfigurations early, before they silently destroy months of campaign data. If your conversion tracking breaks at 9 AM, you should know by 10 AM. Not next quarter. Join the waitlist to get early access.

Frequently Asked Questions

Stop losing conversions in silence

aubado monitors your Google Ads performance and flags the drops that matter. So you catch consent misconfigurations before they cost you months of data.

Explore features

Related Resources

Share this article

send