Paste a URL and the scanner checks how your page implements Google Consent Mode v2. It verifies every required parameter, your consent management platform, and whether tags load in the right order.
Scanning page for consent mode signals...
Consent Mode lets your tags respond to user choices instead of disappearing when consent is denied. Tags still fire, but in a mode that respects the visitor's decision and sends only what privacy law allows. For sites under GDPR, ePrivacy, or CCPA, that balance between compliance and measurement has become the standard way to work.
The v2 update in 2024 added two parameters that matter for advertising: ad_user_data and ad_personalization. Google requires them for ads measurement in the EEA and UK. Without them, conversion reporting goes quiet and campaign decisions get made on partial information. For any business spending on Google Ads, this is not a nice to have.
When consent signals are set up correctly, Google can model the missing conversions using consent aware modeling. You keep useful reporting while still honouring every visitor's choice. That combination of legal safety and measurement accuracy is why Consent Mode now appears in most professional analytics audits.
Enter a public URL and the tool pulls the page source, then looks for every Consent Mode signal. It checks the consent default call, the actual granted and denied values on each storage parameter, the update mechanism, and the consent management platform in use. Every check comes back with a pass, partial, or fail status and a severity level, so you know where to start.
Order matters, and the scanner verifies it. The consent default must fire before the config call, otherwise browsers may record the wrong state. The scan also detects advanced settings like URL passthrough and ads data redaction, plus region specific defaults. Run a scan, fix the critical items, then scan again. The checklist turns an abstract compliance task into a short list of concrete edits.