Numuno Digital /
Consent Mode v2: what your business website needs to check
A visible cookie banner does not prove that website tags respect a visitor’s choice. Consent Mode communicates that choice to compatible Google tags. This guide explains what to agree with your website team, what to test and what measurement cannot promise.
By Numuno Digital, an independent web design and marketing studio in Marbella.
Separate visitor choice from tag behaviour
The banner or consent management platform collects a choice. Consent Mode communicates its state, and the tags need to behave accordingly. Installing one component does not verify the complete setup. The four main signals concern analytics storage, advertising storage, advertising user data and personalised advertising.
The v2 update added ad_user_data and ad_personalization. The other two are analytics_storage and ad_storage. These values must reflect the purposes a visitor actually accepted. Accepting analytics should not be treated as automatic permission for personalised advertising.
Basic and advanced are different implementations
Google describes a basic implementation that blocks its tags until consent is granted, with no data sent to Google when consent is denied. In the advanced implementation, tags load with configured consent states and can send measurements without cookies when consent is denied.
Cookieless does not mean no transmission. Google lists information such as timestamps, user agent and referrer among the possible contents of pings. Do not infer that every implementation is anonymous or suitable for every business. Agree the approach after reviewing the actual tools and intended processing.
Platform requirements do not replace a privacy review
Google’s EU user consent policy requires disclosures and consent for covered products and users in the EEA, UK and Switzerland. In Spain, AEPD guidance explains valid, informed consent and equally visible acceptance and rejection options. Its cookie guide distinguishes exempt cookies from those requiring consent.
Consent Mode does not replace the banner or guarantee legal compliance. Ask who is responsible for the technical integration, the information given to visitors and any case-specific legal review. Do not accept a blanket compliance promise based on a single green diagnostic indicator.
Agree an implementation scope and keep test evidence
Inventory the tools and where they load. Define the purposes, the basic or advanced approach and how choices are remembered and changed. Google’s implementation guide requires default consent before commands that send measurement data and updates where the visitor makes a choice. Its Tag Manager APIs and gtag.js instructions are not interchangeable snippets.
Google signals do not automatically configure Meta or other third-party tools. Review each tag. Test a fresh session with no choice, rejection, partial acceptance and a changed decision, including subsequent navigation and a phone. Google recommends Tag Assistant for checking default and updated consent states and tag behaviour; also inspect actual browser storage and transmissions.
Keep a dated record of the tested choices, devices and results, and repeat the relevant checks after adding a pixel, booking integration or plugin. An old test does not validate every future change.
Keep measurement expectations realistic
GA4 behavioural modelling has implementation and volume requirements; even reaching the published thresholds does not guarantee that a model can be trained. A small site should not expect every missing visit to reappear. GA4 behavioural modelling and Google Ads conversion modelling are different features and should not be discussed as if they were the same report.
Separate measured visits, contact clicks and enquiries actually received. Opening WhatsApp does not prove that a message was sent, and Consent Mode does not test the delivery of a contact form. Review the call-to-action guide for that separate journey.
For a website or Google Ads project, agree tools, integration, testing, licences and maintenance before commissioning. Numuno Digital defines these responsibilities within the agreed project scope. Technical work and specialised legal advice remain distinct.
Reviewed on 26 October 2026 using Google and AEPD documentation. This guide describes technical scope and checks; case-specific legal assessment depends on the actual processing.
Your checklist before starting.
- Tools, purposes and responsibilities documented
- A real visitor choice that can be changed
- An agreed basic or advanced approach
- Default states and updates checked
- Rejection, partial acceptance and changed-choice tests
- Received enquiries distinguished from clicks and estimates