Last updated: November 19, 2026
Google Consent Mode v2 is the way your website tells Google’s tags whether a visitor has agreed to cookies and to the use of their data for advertising. It uses four signals, ad_storage, analytics_storage, ad_user_data and ad_personalization, which your consent banner sets and Google tags obey. If you advertise to people in the European Economic Area or the UK, you need it to keep building remarketing audiences and to get modelled conversions for visitors who decline cookies.
This guide explains what each signal does, the difference between basic and advanced mode, how modelling works and how to implement and test Consent Mode v2 without breaking your measurement.
The original Consent Mode, launched in 2020, had two signals that controlled whether Google tags could use cookies for ads and analytics. In 2024 the EU’s Digital Markets Act required Google, as a designated gatekeeper, to obtain clear consent before using personal data from third-party services for advertising. Google responded by adding two signals and, from March 2024, requiring advertisers serving EEA users to send them. Without valid signals, Google limits audience building, remarketing and some measurement features for those users.
It controls whether Google’s advertising tags can read or write cookies, such as those used for conversion tracking and remarketing.
It controls whether analytics tags such as GA4 can read or write cookies used to identify returning visitors and sessions.
New in version 2, it tells Google whether data about the user, such as conversions or hashed contact details used in enhanced conversions, may be sent to Google for advertising.
Also new in version 2, it tells Google whether the data may be used for personalised advertising, including remarketing audiences.
Each signal is either granted or denied. Your consent management platform sets defaults when the page loads, usually denied in Europe, and updates them when the visitor makes a choice.
In basic mode, Google tags are blocked entirely until the visitor consents. If they decline, nothing is sent to Google. It is the most conservative option, but Google can only model conversions using general data, which is less accurate.
In advanced mode, Google tags load as soon as the page loads, with consent defaulted to denied. Until the visitor consents, tags send cookieless pings that carry no identifiers but tell Google an event occurred. Google uses these pings to model the behaviour of visitors who declined. If the visitor consents, tags switch to full measurement.
Advanced mode recovers more data, but some European regulators and legal advisers consider any data sent before consent to be processing that needs a lawful basis. Many businesses in strict markets such as Germany and Austria choose basic mode for that reason. Decide with your legal adviser, and document the decision.
When consent is denied, Google estimates the missing conversions and behaviour using the patterns of visitors who did consent and, in advanced mode, the cookieless pings. In Google Ads, modelled conversions appear in your conversion columns and feed Smart Bidding. In GA4, behavioural modelling fills gaps in user and session reports once your property meets Google’s eligibility thresholds for daily volume of consented and unconsented traffic.
Modelling is not magic. Small sites may never reach the thresholds, and the estimates are only as good as the share of visitors who consent. Improving your consent rate with a clear, honest banner is often worth more than any technical trick.
The simplest route is a Google-certified consent management platform with a Google Tag Manager template. The steps are similar for most tools:
If you use the Google tag directly without Tag Manager, the CMP will usually inject the gtag consent commands for you. Shopify, WordPress and other platforms also offer apps and plugins that handle the defaults.
In Google Ads, the ad_storage and ad_user_data signals decide whether conversions are measured with cookies and whether enhanced conversion data can be used. When they are denied, Google Ads relies on modelled conversions. The ad_personalization signal decides whether a visitor can be added to remarketing lists, so a low consent rate shrinks your audiences over time.
In GA4, analytics_storage decides whether GA4 can use cookies to recognise returning visitors. When it is denied, GA4 receives cookieless pings in advanced mode or nothing in basic mode. Behavioural modelling can fill the gap in reports once your property qualifies, and you can switch between observed and blended reporting identities in the property settings.
In Floodlight, Campaign Manager 360 and Display and Video 360, the same signals control cookies and audience building for enterprise advertisers. Search Ads 360 and Google Ads conversion imports also respect consent passed through the tag.
For Google Ads data imported from your CRM, such as offline conversions, the ad_user_data signal recorded at the time of the click matters. If the visitor did not consent, you should not upload their personal data for that conversion. Many CRMs and server-side setups now store the consent state with the lead so the right decision is made automatically.
Consent Mode works in a server-side setup too. The browser sends each event to your server container together with the consent state, and the Google tags in the server container read it just as browser tags do. This lets you keep the benefits of first-party cookies and data minimisation without losing consent controls. For the wider privacy picture, read our guide to server-side tracking and GDPR.
Open Google Tag Assistant, load your site from a European location or with your CMP in testing mode, and check that the consent default appears before the first Google tag fires. Accept and then reject cookies, and confirm the update command changes all four signals. In Google Tag Manager, the consent overview shows which tags require which signals. In Google Ads, the diagnostics in your conversion settings report whether consent signals are being received. Repeat the test after every change to your banner or tag setup, because a small update can break the timing.
The most common problems are tags firing before defaults are set, banners sending only the two original signals, defaults set to granted in Europe and assuming Consent Mode covers non-Google pixels. Another frequent issue is a CMP that loads asynchronously, so a fast Google tag beats it to the page. Fixing the trigger order usually solves it.
We reviewed Google’s developer documentation for Consent Mode and the tag platform, Google Ads and GA4 help material on modelling, the documentation of leading consent management platforms and guidance from European regulators. Read how we research and rank for more about our process.
Google’s requirement applies to traffic from the European Economic Area and the UK. Elsewhere it is optional, but it is still useful where local privacy laws require consent or opt-outs.
No. It only controls how Google tags behave based on consent. You still need a compliant banner, a privacy notice, records of consent and rules for every other vendor.
Advanced mode recovers more data through modelling, while basic mode is more conservative. Many businesses in strict markets choose basic mode. Decide with your legal adviser.
Observed conversions fall when visitors decline consent, but modelled conversions in Google Ads fill part of the gap. Without Consent Mode, you lose both the observed data and the modelling.
Google Consent Mode v2 is now a basic requirement for anyone advertising on Google to European audiences. Use a certified CMP, fire it first, send all four signals, choose your mode deliberately and test it regularly. Pair it with a sensible approach to non-Google tags and, ideally, server-side tagging, and you will keep as much useful data as the law allows.