Consent Mode v2, Six Months In: What It Means for Conversion Modeling

Six Months of Consent Mode v2: What Advertisers Are Still Getting Wrong

On March 6, 2024, Google made Consent Mode v2 mandatory for any advertiser using Google Ads, Google Analytics 4, or other Google services with traffic from the European Economic Area or the United Kingdom. Six months on, a significant share of advertisers are still running misconfigured implementations - and paying for it in modeled conversion quality, audience reach, and bidding accuracy.

This post is a practical look at what the mandate actually requires, what a correct setup looks like, and how to diagnose whether your account is leaking signal right now.

What Consent Mode v2 Actually Added

The original Consent Mode (2020) introduced two parameters: ad_storage and analytics_storage. These told Google tags whether to write cookies and send full measurement signals when a user consented - or to send cookieless pings when they did not.

Consent Mode v2 added two new parameters on top of those:

• ad_user_data - controls whether user data can be sent to Google for advertising purposes.
• ad_personalization - controls whether data can be used for personalized advertising, including remarketing.

Without these two new parameters set to denied by default (for users who have not yet consented) and updated to granted on consent, Google Ads and GA4 are no longer permitted to collect or use EEA and UK user data for personalization or conversion modeling. The result is not a warning - it is a hard loss of audience data and, in Google Ads, a degradation of smart bidding inputs.

Basic Mode vs. Advanced Mode

There are two tiers of implementation, and the difference in data recovery is substantial.

Basic Mode

Tags do not fire at all until consent is granted. This is the easiest setup to get right from a compliance standpoint, but it sacrifices all cookieless modeling pings for non-consenting users. Google cannot model conversions it never hears about. If your Consent Management Platform fires Google tags only after a positive consent signal, you are in Basic Mode whether you intended to be or not.

Advanced Mode

Tags fire immediately in a cookieless, data-minimized state for all users. When a user grants consent, the tags upgrade to full measurement. For users who decline or ignore the banner, Google receives anonymized behavioral pings that feed its conversion modeling algorithms. Advanced Mode is what allows GA4 and Google Ads to recover a meaningful share of conversions that would otherwise be invisible.

The practical implication: if you are seeing a large gap between observed conversions and modeled conversions in your Google Ads account for EEA campaigns, audit whether you are actually running Advanced Mode. Most CMPs support it, but it must be explicitly configured.

Diagnosing Your Implementation

A few checkpoints that surface the most common implementation gaps:

• Tag firing order: The gtag('consent', 'default', {...}) call must execute before any Google tag loads. If your CMP injects the default state asynchronously after the Google tag has already initialized, the default is ignored.
• All four parameters present: Use Google Tag Manager's consent overview or the Consent Mode debug view in GA4 to confirm ad_storage, analytics_storage, ad_user_data, and ad_personalization are all being set - not just the original two.
• Update call on consent: The gtag('consent', 'update', {...}) call needs to fire when the user accepts or changes their choices. Check that your CMP is triggering this correctly in GTM preview mode.
• GA4 consent signal report: GA4's admin section includes a consent signal diagnostic. If it shows a high percentage of sessions with no consent signal at all, the default call is not landing before the analytics tag.

What Modeled Conversions Actually Mean for Bidding

Conversion modeling fills in the gaps left by non-consenting users. Google uses observed behavioral signals - session depth, time on site, scroll behavior - to statistically estimate how many conversions occurred among users whose data it cannot directly observe. These modeled conversions are included in your reported conversion column and fed into Smart Bidding.

The key point for account managers: modeled conversions are not decorative. They are inputs into Target CPA and Target ROAS bidding. An account running Basic Mode loses those inputs for all non-consenting EEA users, which means Smart Bidding is operating on a thinner signal set and making noisier decisions. Advertisers who migrated to Advanced Mode correctly have reported more stable bidding behavior in EEA campaigns - not because their actual conversion rates changed, but because the model had more to work with.

Audiences and Remarketing

The ad_personalization parameter is the one most commonly overlooked. Even if your ad_storage and ad_user_data are configured correctly, a denied ad_personalization state means users cannot be added to Google Ads remarketing lists or used for similar audiences. For any account that relies on RLSA or customer match for EEA campaigns, this is a material gap - and it is silent. There is no alert in Google Ads when remarketing list growth slows due to consent configuration.

Audit your audience size trends for EEA segments. If list growth dropped sharply after March 2024 and did not recover, ad_personalization handling is worth examining.

Getting It Right Going Forward

Consent Mode v2 is not a one-time checkbox. It lives at the intersection of your CMP, your tag management layer, and your Google properties. Any CMP update, GTM container publish, or GA4 configuration change can break the consent signal chain. Build a quarterly consent audit into your measurement operations routine.

Proper first-party data tracking starts with a clean consent foundation. If consent signals are broken, everything downstream - attribution, audiences, bidding - is working with compromised inputs. For a hands-on audit of your Consent Mode setup and a full measurement health check, book a call with the AdStack™ team.