Google Consent Mode v2: A marketer’s guide to consent, measurement and campaign decisions

When is it relevant to your business?

Review Consent Mode if you use Google Ads or Google Analytics and need your measurement or advertising features to respond to visitors’ consent. It is particularly relevant when operating under Google’s EU user consent policy, which covers the EEA, UK and Switzerland.

Start with your business goals: conversion measurement, audience building, remarketing or analytics. Each may rely on different signals and settings. A working page-view report does not prove that consent is correctly configured for advertising.

Google’s policy and local law are separate obligations. A setup can send technically valid signals while still presenting an inadequate consent choice.

What the four signals mean

Google’s Consent Mode overview describes how tags adapt to the consent state. For marketing teams, four signals deserve particular attention:

• ad_storage: whether advertising-related storage, such as relevant cookies, is permitted.
• analytics_storage: whether analytics-related storage is permitted.
• ad_user_data: whether user data may be sent to Google for advertising purposes.
• ad_personalization: whether data may be used for personalised advertising.

The last two were added with Consent Mode v2. Treat the signals as different permissions, not four names for the same “accept” button.

Map each visitor-facing purpose to the correct signals. Someone accepting analytics should not automatically be marked as consenting to personalised ads. Also review any additional Google settings relevant to your implementation.

Basic or advanced: understand the trade-off

Basic Consent Mode

In basic mode, Google tags are blocked until the visitor interacts with your consent mechanism and grants the relevant consent. When consent is not granted, no data is sent to Google through those blocked tags, including consent status.

This creates a clearer boundary before permission. It can also leave less information available for measurement. Google may use more general modelling where applicable, rather than modelling informed by consent-denied pings from your site.

Advanced Consent Mode

In advanced mode, Google tags load with the configured default consent state. When relevant consent is denied, tags can send cookieless pings. Where consent is granted, behaviour changes accordingly.

These pings can support more specific modelling, subject to Google’s eligibility and data requirements. Cookieless does not mean anonymous or automatically lawful. Assess the information sent, the purpose and the rules applying to your visitors before choosing this mode.

Google’s implementation guide explains the setup. Choose based on your obligations and measurement needs, and make the choice visible in your internal measurement plan.

Five things to get right

1. Define what a successful setup means

Write down the products and conversion actions you depend on. For an online store, that might mean completed purchases in Ads, ecommerce reporting in Analytics and a separate remarketing audience.

For each, identify the permission required and the expected behaviour when it is denied. This makes testing concrete and avoids treating “Consent Mode enabled” as the finish line.

2. Set the default before tags act

The default state must be established before tags perform the affected activity. Where permission is required, a visitor should not briefly be treated as opted in while the banner loads.

Review regional defaults and page templates. A correct homepage setup can still leave campaign landing pages, checkout or a separate booking domain behaving differently.

3. Send updates that reflect the actual choice

When a visitor accepts, rejects or changes settings, the relevant signals should update. Check repeat visits as well as the first interaction.

Do not assume a saved banner preference has reached Google. Verify the actual consent state and tag behaviour. Keep non-Google advertising and analytics tools within the same consent review, even though Consent Mode does not control them automatically.

4. Validate the measurement journey

Use Google’s consent verification guidance to inspect consent defaults and updates in Tag Assistant. Test one purchase or lead journey in each relevant state.

Check duplicate conversion events, missing updates and cross-domain transitions. A consent change should not make one purchase appear twice. Record the test date, configuration and outcome so future reporting changes have a useful reference point.

5. Explain modelling accurately

Google describes basic and advanced behaviour in its Consent Mode help guide. Modelled results are estimates based on available information; they are not a list of identified people who declined tracking.

Availability and impact depend on the product, traffic and eligibility. Conversion modelling and Analytics behavioural modelling are also different features. Do not promise a fixed uplift or assume every account will see the same result.

What this means for campaign reporting

After a consent implementation change, annotate your reporting. A change in recorded conversions may reflect different collection or modelling as well as real performance.

Compare advertising reports with completed orders or qualified leads in your business systems. Check attribution settings, reporting delays and conversion definitions before changing budgets.

For example, a store switching from an incorrectly permissive setup to a consent-aware one may initially see fewer observed conversions. That does not by itself prove the campaign has deteriorated. Establish a new reporting baseline and explain what is observed, what is modelled and what remains uncertain.

Marketer’s checklist

• Check objectives: list the Ads and Analytics features your team actually uses.
• Check the mode: document whether the implementation is basic or advanced.
• Test defaults: confirm the consent state is set before affected tags run.
• Test all choices: accept, reject, partial consent and withdrawal.
• Check all four signals: verify each matches the visitor-facing purpose.
• Test key journeys: include landing pages, checkout, lead forms and returning visits.
• Check other vendors: confirm non-Google tools respect the same relevant choices.
• Review reporting: annotate changes and compare with actual business outcomes.

FAQ