Skip to content

Google Consent Mode v2 missing required redaction parameters

This check looks at the site's Google Consent Mode setup for two specific settings, ad_user_data and ad_personalization, which have been required since March 2024. On this site, Google Consent Mode is present, but these two parameters are missing from the default configuration call, meaning the setup is incomplete rather than fully compliant. Without ad_user_data and ad_personalization configured, Google withholds conversion modelling for traffic from the European Economic Area (EEA), which means the site's own Google Ads reporting under-counts real conversions from those visitors. This has been required since March 2024, so a site missing it has effectively been running an outdated, partial version of Consent Mode. Your developer should add ad_user_data and ad_personalization to both the default Consent Mode call and any subsequent update calls that run when a visitor accepts or changes their cookie choices. This is a small, well-documented code change, typically about an hour, and can be verified using Google Tag Manager's preview mode or the browser's network tab.

Why this matters

Without ad_user_data and ad_personalization configured, Google withholds conversion modelling for traffic from the European Economic Area (EEA), which means the site's own Google Ads reporting under-counts real conversions from those visitors. This has been required since March 2024, so a site missing it has effectively been running an outdated, partial version of Consent Mode.

How to fix it

Your developer should add ad_user_data and ad_personalization to both the default Consent Mode call and any subsequent update calls that run when a visitor accepts or changes their cookie choices. This is a small, well-documented code change, typically about an hour, and can be verified using Google Tag Manager's preview mode or the browser's network tab.