Consent Mode v2: How Conversion Modeling Works

What is Consent Mode v2?

Consent Mode is Google’s framework for adjusting tag behavior to each visitor’s consent choices. Version 2 added two signals, ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent to personalized ads), on top of ad_storage and analytics_storage (Google, consent mode overview).

If you serve ads to people in the European Economic Area, Google requires you to collect consent from EEA users and share those consent signals with Google for ad personalization, remarketing and measurement (Google Ads Help). Without valid signals, you lose EEA users from your remarketing audiences and your measurement gets thinner.

What is the difference between basic and advanced consent mode?

Basic consent mode blocks Google tags until the visitor interacts with the banner. If they decline, Google receives nothing from them. Google can still model conversions, but only with a general model (Google).

Advanced consent mode loads Google tags when the page opens, with consent set to denied by default. For visitors who decline, the tags send cookieless pings with functional data such as timestamp, user agent, referrer and the consent state. Google uses these pings to build an advertiser-specific model, which it describes as improved modeling (Google).

Advanced mode gives you better modeling. Check with your legal adviser before you pick it, because it sends cookieless pings before the visitor has chosen.

How do you implement Consent Mode v2?

1. Use a consent management platform (CMP) that integrates with Google Consent Mode, preferably one from Google’s CMP partner list.
2. Set default consent states to denied for EEA traffic before any Google tag loads.
3. Send the consent update as soon as the visitor chooses, before any conversion tag fires.
4. Confirm that all four parameters update, not only the original two.
5. Check in Google Tag Assistant that the consent state is right on the landing page and on the conversion page.
6. Check consent mode status in the Google Ads diagnostics for your conversion actions.

Where do Consent Mode setups break?

The faults we see most often in audits:

• Consent defaults set after the Google tag loads, so the first page view goes out without a consent state.
• The CMP updates analytics consent but never the advertising signals.
• A server-side container forwards events without the consent state, so Google can’t apply the visitor’s choice or model the gap.
• Single-page apps set consent once and never update it on route changes.

Each of these looks fine in a quick check and costs you measured conversions. If you run server-side tagging, make the consent state travel with every event. Why your ad data goes missing explains how server-side tracking and consent fit together.

When does Google model conversions?

Google Ads conversion modeling uses observed, consented conversions to estimate the ones it can’t observe. It needs volume: Google sets a threshold of 700 ad clicks over 7 days, per country and domain grouping (Google Ads Help, consent mode modeling).

If your account sits below that, modeling won’t fill the gap. Put the effort into your consent rate, because each extra visitor who accepts is a conversion Google measures instead of estimating.

How can you raise consent rates without dark patterns?

Treat the banner like any other conversion step:

• Keep it short and in plain language.
• Make “reject” as easy as “accept”. The French regulator CNIL fined Google €150 million and Facebook €60 million in 2022 because refusing cookies took more clicks than accepting them (CNBC).
• Explain the benefit in one sentence, for example “So we can show you relevant offers and improve the site.”
• Test placement and wording, and track consent rate as a metric.

You control consent rate more than any other part of measurement.

Should you pair Consent Mode with server-side tracking?

Yes. Consent Mode governs what you may collect (for the legal side, see GDPR and ad tracking in the EU). Server-side tracking gets more of the consented data to Google and Meta. Together they close more of the gap between orders in your backend and conversions in your ad accounts. To choose a server-side setup, read TAGGRS vs GTM server-side.

Review the setup each quarter and document your consent architecture. Our tracking service covers Consent Mode, CMP setup and server-side tagging, and our Google Ads management relies on that data for bidding.

FAQ

Is Consent Mode v2 mandatory?

For EEA traffic, Google requires you to collect consent and pass consent signals if you want ad personalization, remarketing and measurement to work for those users. Outside the EEA, it’s optional but useful wherever you run a consent banner.

Does basic consent mode allow conversion modeling?

Yes, but Google uses a general model. Advanced mode sends cookieless pings for visitors who decline, which lets Google build a model specific to your account.

How many clicks do I need for conversion modeling in Google Ads?

Google sets the threshold at 700 ad clicks over 7 days, per country and domain grouping.

Does Consent Mode work with server-side tagging?

Yes, if your server container receives and forwards the consent state with each event. If it drops the consent state, Google can’t apply the visitor’s choice.