Consent Mode v2: how much data you really lose and what it does to your campaigns

What Consent Mode v2 is — in one sentence

Consent Mode v2 is the mechanism by which your site tells Google's tags what a user has consented to, and Google adjusts its data collection accordingly. Since March 2024, it's effectively mandatory in the European Economic Area for anyone who wants to use remarketing, audience lists, and full conversion measurement in Google Ads and Google Analytics 4. Without it, Google stops accepting EEA traffic data for those features. It's a technical cutoff of the signal: the data simply stops arriving.

In practice, Consent Mode v2 adds two new consent parameters to the standard setup: ad_user_data (whether user data may be sent to Google for ads) and ad_personalization (whether it may be used for personalization and remarketing). These decide whether a given user feeds your campaigns at all, or disappears from measurement. The rest of this article is about how much you lose and how to limit it.

How much data do you lose without Consent Mode v2?

Without a correctly implemented Consent Mode v2, you lose exactly as much measurement as the share of users who reject marketing cookies. That share depends on the industry and how the consent banner is built. Those users still buy, fill in forms, and call, but their conversions have no way to reach Google, so in the dashboard they look like they never happened. The result: understated conversion volume, overstated cost per acquisition, and Smart Bidding optimizing against an incomplete picture.

That „other half” is half your budget being judged blind. If you're working to make the dashboard numbers match the company's profit (we covered this in our piece on the marketing dashboard), the consent layer is the foundation the rest of measurement stands on.

Basic or Advanced — the difference and what to choose

There's one difference, but it's decisive: in Basic mode, Google's tags don't fire at all until the user clicks „accept,” while in Advanced mode the tags load immediately and, when there's no consent, send anonymous cookieless pings (Google Ads Help on consent mode). Those pings are exactly what later lets Google model the lost conversions. For most results-driven companies, that settles it in favor of Advanced. Basic is simpler and feels „safer” legally, but it gives up more data that you'll never get back.

If you operate in the EEA and care about Smart Bidding and remarketing, default to Advanced. Basic makes sense where volume is so small that modeling won't trigger anyway, or where the legal team demands a hard „no signal before consent.” Choosing it means deciding how much measurement you knowingly give up.

How many conversions does Google's modeling really recover?

Modeling recovers only part of the lost conversions, and it's better to know that before you believe the marketing slides. Based on cookieless pings and historical data, Google estimates how many conversions „probably” came from unconsented traffic and adds them to reports as modeled conversions. That's a statistical estimate, so treat it as a good approximation of counted transactions.

The catch: modeling only kicks in above a volume threshold. In Google Ads the threshold is 700 ad clicks over 7 days per country and domain grouping, and only above it do the models start training. A small account with a dozen-odd conversions a month won't get modeling and is left with a hole in the data. That's why the smaller your traffic, the more it matters not to lose a single conversion to implementation errors.

What Consent Mode v2 does to your Smart Bidding and remarketing

Consent Mode v2 affects campaigns in two places at once: it feeds (or starves) Smart Bidding with conversion data, and it decides how many users reach your remarketing lists at all. With no consent and no Advanced mode, a user won't feed any audience list, so your remarketing audience shrinks by exactly the share of people rejecting cookies. Smaller lists mean more expensive, narrower remarketing, and the bidding algorithm gets a weaker signal to learn from.

It's the same mechanic we described with Performance Max and inflated ROAS: the automation is only as good as the data you feed it. If Smart Bidding sees only half your conversions, it will underbid where it „can't see” the result and shift budget toward campaigns that happen to have better-measured traffic. Those may well earn the least. Correct consent is fuel for the bidding.

Consent Mode v2, server-side, and Enhanced Conversions — how they fit together

Consent Mode v2, server-side tagging, and Enhanced Conversions are three different layers and work best together. Consent Mode sets what's allowed to be sent; Enhanced Conversions improves the match on the conversions you do have consent for (via hashed data such as email); and server-side tracking moves data collection to your server, where you have more control over what reaches Google and when. Order matters: consent first, then match quality, then infrastructure.

In practice, investing in a server-side GTM setup or solid GA4 measurement makes little sense if the consent layer leaks and half your conversions can't count anyway. Seal Consent Mode v2 first, then build the rest on top of it. As a marketing agency, this is usually the layer we start a measurement audit from, because an error here contaminates every number above it. You can run a first check yourself: the GA4 audit scans your site by URL and shows which tags and events it actually sends.

How to check whether Consent Mode v2 works correctly

You can check Consent Mode v2 in a few minutes by looking at which consent parameters leave the site before and after the banner is accepted. An installed plugin settles nothing: an implementation can look enabled and still send the wrong signals, or none at all. The Consent Mode Checker covers some of these points for you, and the list below is the minimum you run after every implementation and every change to the consent banner.

• In Google Tag Assistant, check that before clicking the banner the tags send a default consent state (denied), and that after acceptance it updates to granted.
• Confirm both new parameters are passed: ad_user_data and ad_personalization. A missing one is the most common Consent Mode v2 error.
• In GA4, set the reporting identity to Blended (Admin → Data display → Reporting identity) and check the data-quality icon in reports: when it says the report includes estimated user data, behavioral modeling is working. DebugView shows only raw events from devices in debug mode, so modeled data never appears there; use it to check that events with a consent state reach GA4 at all.
• Verify the consent banner (CMP) is integrated with Consent Mode and passes a signal to the tags. A cookie notice on its own, however nicely displayed, doesn't do that.
• Verify the default state before consent: it should be denied for all marketing categories, or you risk collecting data with no basis.

FAQ: Consent Mode v2