How to Set Up Consent Mode v2 for Google Ads (EU Requirement)

Consent mode v2 is how you tell Google whether a visitor gave permission for advertising and analytics cookies. Since the European privacy rules around the Digital Markets Act, this is no longer a technical luxury but a hard EU requirement: without valid consent signals, Google no longer fills your remarketing audiences and no longer serves Customer Match in the EEA. This article explains what google consent mode v2 actually does, which choices you face, and how to set it up without losing your measurement and your audiences.

This guide belongs with our overview of what SEA is and the broader acquisition layer of your growth engine. Because consent mode touches exactly the place where paid and measurement meet.

What consent mode v2 is and why it became mandatory

Consent mode is a Google framework that adapts the behaviour of its tags to the permission a visitor gives. If someone consents, Google measures and personalises in full. If someone refuses, Google adjusts its tags so that no identifiable data is sent.

The “v2” refers to two new parameters that Google made mandatory in order to stay in line with European regulation:

• ad_user_data. May the user data be shared with Google for advertising purposes?
• ad_personalization. May that data be used for personalised advertising, such as remarketing?

These come on top of the existing analytics_storage and ad_storage signals. The difference with v1 is that Google now needs these v2 signals to process your audiences and your conversions in the EEA at all. If you do not pass them on correctly, Google stops filling your remarketing lists and your Customer Match segments for European visitors. That is why this is a requirement and not a recommendation.

How consent mode hits your measurement and remarketing

This is why consent mode v2 is an advertising question and not a purely legal file. The impact lands straight in your campaigns:

• Conversion measurement. Without consent, direct measurement falls away. Google fills that gap with modelling (estimated conversions), but only if you have set it up correctly. Otherwise you simply see fewer conversions and you steer your bids on an incomplete picture.
• Remarketing. Visitors who refuse ad personalisation do not end up in your remarketing audiences. Your remarketing lists shrink, and with them the scale of your repeat campaigns.
• Customer Match. Uploaded customer lists are only matched in the EEA if the underlying consent is in order. Without a valid consent basis, delivery stops.
• Smart bidding. Automated bid strategies lean on conversion data. If that data gets thinner, your bids perform worse, even though you change nothing about your campaign.

In other words: badly set up consent mode does not cost you a fine, but it does cost you return. You pay for clicks while you have lost the signal that tells you whether those clicks deliver anything. That is precisely the opposite of paid that buys pipeline instead of clicks.

Basic versus advanced consent mode

The main choice you make is between two implementation forms. The difference determines how much you still measure when someone refuses.

Basic consent mode. The Google tags only load after the visitor gives consent. If someone refuses, nothing is sent, not even an anonymised signal. You keep a cleaner privacy story, but you lose the visitors without consent entirely from your measurement. Modelling is limited here because Google sees no data point at all from the refusers.

Advanced consent mode. The tags always load, but on refusal they only send anonymised, cookieless pings without identifiers. Google uses those aggregated signals to model conversions for the part of your traffic that refused. So you keep an estimate of what you would otherwise not see at all.

For most B2B advertisers with paid traffic, advanced is the logical choice: you want to keep as much measurability as possible without breaching the privacy rules. Basic fits better when your internal policy strictly prescribes that nothing may go to Google before consent. Make this choice deliberately and not by accident, because it determines the quality of your entire conversion dataset.

Setting up consent mode v2 correctly

The setup revolves around three components that have to fit together. If one of them does not cooperate, the whole thing is wrong.

1. A certified consent management platform (CMP). Your cookie banner has to translate the consent choices into the Google signals. Use a CMP that supports consent mode v2 and holds the Google certification, otherwise ad_user_data and ad_personalization are not passed on.
2. Default state before the choice. Before the visitor clicks anything, all consent types must be set to denied. Only after an active choice do you update to granted where allowed. This “default denied, update on consent” pattern is the core of a correct implementation.
3. Passing signals via Tag Manager or gtag. In Google Tag Manager you handle the consent status with a dedicated consent initialisation that fires before all your other tags. If you work with gtag directly, you put the consent('default', ...) and consent('update', ...) calls in the right order.

Watch the timing. The default state has to be loaded before any measurement tag fires at all. If your conversion tag fires before the consent status is known, you pass on the wrong signals and you still lose data. This setup is directly connected to how you measure conversions in Google Ads: consent mode determines which of those conversions may be registered in the first place. Which actions you set as primary versus secondary conversion actions also helps determine what your bids steer on.

Common mistakes in the implementation

In the accounts we take over we keep seeing the same pitfalls. Every one of them is avoidable:

• Only passing on the old v1 signals. Many banners were set up years ago and do send ad_storage and analytics_storage, but not ad_user_data and ad_personalization. You then think you are fine while Google has already stopped filling your audiences.
• Leaving the default on granted. If your default state grants consent before the visitor chooses, you breach the rules and you risk Google treating your setup as non-compliant.
• Letting the consent tag fire too late. A correct configuration that loads in the wrong order still delivers polluted data.
• Not testing after every change. Every adjustment to your site, your banner or your tags can break the chain. Whoever does not retest only discovers the data leak weeks later in their reporting.

These mistakes explain why two companies with the same banner can have completely different data quality. It is not in the tool but in the configuration.

Testing whether your setup works

Never trust an implementation blindly. Check it. Google’s Tag Assistant shows you per page which consent signals fire and with what status. That lets you see whether granted and denied switch correctly when you accept or refuse in your own banner.

On top of that, Google Ads itself gives a diagnostic overview of your consent status and warns you when signals are missing or non-compliant. Go through that overview periodically, certainly after every site change. That kind of recurring check can partly be automated with automated rules in Google Ads. Only when both sources are green can you trust your conversion figures and your audiences again as a basis for steering.

Where consent mode fits in your growth engine

Consent mode is not an isolated technical chore. It is the gate through which all your pay-per-click data comes in. If that gate is set wrong, you weaken your measurement, your remarketing and your bids at the same time. If it is set right, you keep as much signal alive as possible in a privacy-friendly world to steer your budget precisely.

That is why we treat consent mode as part of the measurement foundation, not as a finishing touch. For anyone using SEA as the fast acquisition layer of one orchestrated growth engine, with offline conversions and lead-to-deal attribution, a watertight consent setup is the condition for that attribution to add up at all. If you would rather not figure this out yourself, our google ads specialist sets up the entire chain from banner to conversion correctly, so that you measure what you pay for.

A good starting point is a check on your current setup: are you still measuring everything you think you measure? Compare this alongside your conversion tracking and your attribution models to see where data falls away.

Ready to make your measurement watertight?

Consent mode v2 is an EU requirement you cannot ignore without losing your remarketing and your conversion data. The technical setup is straightforward, but the details determine whether your data is right or quietly leaks. Do you want certainty that your setup is compliant and your measurability stays maximal? Get in touch and we will go through your consent and conversion setup together.