Consent Mode v2: what a site using Google Ads in the EU must have

Google Consent Mode v2 is the way a site tells Google the consent status of a visitor. It is not a replacement for the cookie bar and it is not legal consent in itself. It is a technical layer that tells Google tags what they can and cannot do based on the choice the user made in the cookie bar.

If you use Google Ads, Google Analytics 4, remarketing or conversion measurement and you have visitors from the European Economic Area, Consent Mode v2 is practically an essential part of measurement.

What Consent Mode does

Without Consent Mode a site often behaves too simply: either the Google scripts run at full power, or they are blocked entirely. That can be a problem.

If the scripts run before consent, a legal and reputational risk arises. If they are blocked entirely, you lose a large part of your traffic and conversion data.

Consent Mode solves this in-between space. It sends Google tags the information about whether the user agreed to analytics, advertising, personalization and the use of advertising data. Google then adjusts the behavior of the tags according to the consent status.

What version v2 brought

Consent Mode v2 mainly adds two signals:

• ad_user_data
• ad_personalization

These signals complement existing states such as analytics_storage and ad_storage. In practice they are about whether Google may use the user's advertising data and whether it may personalize advertising.

For companies that use Google Ads, this matters especially for remarketing, audiences and conversion modeling.

Who this concerns

Consent Mode v2 should be addressed by every site that:

• uses Google Analytics 4,
• uses Google Ads,
• measures conversions,
• uses remarketing,
• targets campaigns at users in the EU or EEA,
• works with an agency that manages performance campaigns.

If you only have a simple company website with no analytics and no marketing scripts, Consent Mode may not be a priority for you. But if you invest in PPC campaigns, it is one of the first things you should check.

What is at stake if Consent Mode is not set up

Here you have to separate two things.

The first is marketing and data. If Consent Mode v2 is missing or set up wrong, you may lose part of your conversion data, remarketing audiences and campaign accuracy. That does not automatically mean a fine from Google. It means worse measurement and worse decision-making.

The second is legal. If a site fires analytics or marketing cookies before consent, the problem is not in Consent Mode but in the incorrect collection of consent and blocking of scripts itself.

The correct solution is therefore not just to "turn on Consent Mode". The correct solution is to:

1. have a fair cookie bar,
2. block optional scripts before consent,
3. send Google tags the correct consent signals,
4. store a record of the consent,
5. allow the consent to be changed or withdrawn at any time.

Basic vs Advanced Consent Mode

In practice people often talk about two modes.

A basic implementation means the Google tags do not run until the user gives consent. It is easier to understand and for many sites it is a good foundation.

An advanced implementation means the Google tags load even before consent, but in a limited mode and without storing advertising or analytics cookies if consent is missing. This implementation can help with modeling, but it has to be deployed very carefully and in line with legal requirements.

For ordinary e-shops it is important that they understand at least what signals are sent before and after consent.

How to set it up in Cookienovo

In Cookienovo the goal is simple: the site owner should not have to assemble consent signals by hand or call a developer with every change.

A typical procedure:

1. You add the site to Cookienovo.
2. You insert the Cookienovo script into the site's header.
3. You run a cookie scan.
4. You check the cookie categories.
5. You turn on Google Consent Mode v2.
6. You verify the status via Google Tag Assistant.

Cookienovo makes sure that the consent from the cookie bar is reflected in the signals for Google.

How to verify that it works

After deployment we recommend checking:

• whether the banner is shown to a new visitor,
• whether it is possible to reject all optional cookies,
• whether marketing cookies do not fire after rejection,
• whether Tag Assistant sees the consent signals,
• whether the state of the consent signals changes after acceptance,
• whether data arrives in GA4 and Google Ads in the expected way.

If these points do not add up, the problem may be in the script order, in the GTM settings, or in the fact that some plugin inserts measurement code outside the CMP's control.

Conclusion

Consent Mode v2 is not just a checkbox in the settings. It is the connection between legal consent, technical blocking and marketing measurement.

If you have a site in the EU and use Google Ads or GA4, you should have it sorted out. Not because it is another bureaucratic requirement, but because without a correct consent setup your data will be less accurate and your site less trustworthy.

In Cookienovo you can turn on Google Consent Mode v2 together with the cookie bar and cookie scanning in one place.

Recommended sources:

• Google Consent Mode documentation: https://developers.google.com/tag-platform/security/guides/consent
• Google Ads EU user consent policy: https://support.google.com/google-ads/answer/10000067?hl=en
• GDPR art. 7 and art. 13: https://eur-lex.europa.eu/eli/reg/2016/679/oj

---