Legal basics & privacy · · 6 min read · By Alexander
Google Consent Mode v2: What SMEs need to know
Google Consent Mode v2 controls how Google tags react to a visitor’s cookie-banner choice. It does not replace valid consent or a correctly configured banner, but it can align measurement and advertising technology with the selected consent status.
What is Google Consent Mode v2?
Google Consent Mode v2 is a technical interface between your consent management platform and Google services such as Google Analytics 4 or Google Ads. The website first sends a default status and updates it when the visitor accepts or rejects categories in the banner. Google describes Consent Mode as a method for adjusting Google-tag behaviour to the user’s consent status; source checked on 29 October 2026.
The distinction matters: Consent Mode is not a visible cookie banner, a privacy policy or an automatic legal audit. It transports choices to tags. Whether your banner is understandable, offers a genuine choice and accurately describes each service remains a separate task. SMEs should therefore ask how the banner, tag manager and Google services work together reliably, not whether they need Consent Mode instead of a banner.
Which signals are part of Consent Mode v2?
Version 2 uses four key consent signals. “analytics_storage” controls storage for analytics and “ad_storage” controls advertising storage. “ad_user_data” covers sending personal data to Google for advertising, while “ad_personalization” covers personalised advertising. Google lists these parameters in its official Consent Mode reference; source checked on 29 October 2026.
These values must not simply be set to “granted”. The initial state must match the actual choice and be available before affected tags execute. The consent platform sends an update after the visitor decides. Review regions, categories and Google products as well: a simple analytics site requires a different setup from a shop using remarketing and Google Ads conversions.
- analytics_storage: storage and access for analytics
- ad_storage: storage and access for advertising
- ad_user_data: sending user data to Google for advertising
- ad_personalization: personalised advertising and remarketing
Basic or Advanced Consent Mode: what is the difference?
In Basic Consent Mode, Google tags remain blocked until the visitor gives consent. If consent is refused, the tags do not load and no Consent Mode pings are sent. This is easier to understand and reduces data flows before consent, but Google receives fewer signals for modelled reporting.
In Advanced Consent Mode, Google tags load with a default denied status. When consent is denied, limited cookieless pings may still be sent; after consent, the configuration switches to the permitted status. Google says these signals can support conversion modelling. This does not make every Advanced setup automatically lawful. The actual requests, their content and the legal basis must be assessed for the specific website.
For many small firms, Basic is the clearer starting point. Advanced may be useful when Google Ads is commercially important, the consent platform is correctly integrated and data flows are documented and tested. Choose according to purpose, risk and maintainability rather than a vague promise of “more data”.
Does Consent Mode v2 replace the cookie banner?
No. Section 25 of Germany’s TDDDG generally requires consent when information is stored on or read from a user’s device, with exceptions including operations that are strictly necessary. The law also requires clear and comprehensive information. Source: German Federal Ministry of Justice, Section 25 TDDDG, checked on 29 October 2026. Whether a service is necessary depends on its real function, not the label used in the banner.
A useful banner should not display only a prominent accept button while hiding rejection. Categories, providers, purposes and withdrawal options must match the real technology. Consent Mode acts after the choice by supplying the status to Google tags. If Analytics or Ads is loaded uncontrolled beforehand, a later “denied” signal cannot undo the earlier data flow.
This guide is not legal advice. Sensitive data, complex remarketing, multiple advertising networks or international transfers should be reviewed by a data protection officer or specialist legal adviser.
Who needs Google Consent Mode v2 for Google Ads?
Consent Mode v2 is particularly relevant to businesses using Google Ads, Google Analytics 4, Floodlight or related Google advertising functions in the European Economic Area. Google required the additional “ad_user_data” and “ad_personalization” signals for certain personalisation and measurement functions from March 2024; the official help pages were checked again on 29 October 2026.
Without suitable signals, audiences, personalised advertising and parts of conversion measurement may be restricted. That is not a reason to pressure visitors into accepting. First measure which campaigns genuinely produce enquiries or sales and limit the setup to services you need. A company that uses neither Google advertising nor consent-dependent Google measurement will often not need Consent Mode.
With a managed website or website subscription, responsibility for jointly testing banner text, Google Tag Manager, Analytics and Ads after changes should be explicit. A formally installed Consent Mode is of little value if a later marketing script bypasses the banner.
How can SMEs check the setup step by step?
Start with an inventory rather than a new plugin. List external scripts, embedded content and Google products. Assign each service a purpose, category, legal basis and technical trigger. Then configure the default status, the update after a choice and the mapping of all four signals. In Google Tag Manager, review consent settings and additional consent checks for every tag.
Test at least three cases in a fresh browser: no decision, full rejection and selected consent. Use the network panel, Tag Assistant and the consent platform to see which requests are actually sent. Clear cookies and local storage between tests. Record the date, configuration and result so later changes remain traceable.
- Inventory services, cookies, local storage and external requests
- Set the default status to denied before Google tags where no consent exists
- Map banner categories to the four consent signals correctly
- Choose Basic or Advanced deliberately and document data flows
- Test rejection, partial consent, full consent and withdrawal separately
- Retest after plugin, tag or campaign changes
Frequently asked questions about Google Consent Mode v2
Is Google Consent Mode v2 mandatory?
Not every website must use Consent Mode. The v2 signals are relevant to certain Google Ads and measurement functions in the EEA. What matters is which Google services you actually use.
Do I still need a cookie banner?
Yes, when your services require consent. Consent Mode sends the selected status to Google tags but does not replace the banner or privacy policy.
Which is safer: Basic or Advanced Consent Mode?
Basic blocks Google tags until consent and is generally easier to understand. Advanced sends limited cookieless signals when consent is denied, so it requires particularly careful technical and legal review.
Can Consent Mode recover every lost conversion?
No. Google may model conversions from available signals, but this does not create complete user-level measurement or guarantee identical figures.
How often should the setup be checked?
Check it after every change to the banner, tag manager, Analytics, Ads or plugins and at regular intervals. A documented quarterly check is practical for many SMEs.