TagPipes Companion for Chrome Add to Chrome →

Guide: Privacy

Consent Mode v2: Setup, Testing and Common Failures

Consent Mode passes the visitor's consent decision to Google tags. Version 2 added two parameters, ad_user_data and ad_personalization, alongside ad_storage and analytics_storage.

When consent is denied, tags adjust their behaviour, and Google can model the conversions it can't observe.

How many sites actually send it

From the Website Privacy Index (47,419 sites scored, crawled January to September 2026):

  • 23,307 sites ran Google tags with no consent signal at all (49.2%).
  • 2,108 sent a working Consent Mode v2 signal (4.4%).

Full breakdown: Consent Mode v2 adoption

Why it's a measurement problem, not only a compliance one

With no signal, there's no gap for Google to model, so reports look clean whether or not anyone is being counted. Read: Consent Mode Is A Measurement Problem Before It Is A Compliance One

Where it breaks

How to test it

  1. Load the site fresh, before touching the banner, and check what fires.
  2. Decline, then check again.
  3. Confirm the default and update consent commands both reach Google tags.

Read: Your Consent Banner Passed Launch Day. That Was The Easy Test.

This guide describes technical implementation and observed scan results. It is not legal advice and does not determine whether any site meets a legal requirement. Privacy and consent obligations depend on your jurisdiction and circumstances; confirm them with your counsel.

Have consent run properly, every day

Managed privacy keeps your CMP, consent gating and Consent Mode signal working as your site changes.