Consent Mode v2 checker
Enter a page and see whether it has a consent banner, a Consent Mode default with the v2 signals, and whether that default loads before the Google tags.
What "good" looks like
A consent default is set before any Google tag loads, with all four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. When the visitor makes a choice, the banner sends an update, and the choice is applied again on every later page view.
For the full setup, read our Consent Mode v2 implementation guide, or see privacy and consent setup if you'd rather we wire it for your client.
About this checker
4 questions
It reads the page's HTML source, the way a search engine would, and looks for a consent platform, a Consent Mode default command, the v2 parameters, and where the default sits relative to the Google tags. It doesn't run the page's JavaScript or click the banner.
Not necessarily. Many consent platforms set Consent Mode from inside Google Tag Manager, which this scan can't see. Open the site with Tag Assistant and check the Consent tab: the default should appear before any tag fires, and an update should follow when you click the banner.
Google tags read the consent state when they load. If the default is set after the Google tag has already loaded, the first hits can go out without consent information. Google's guidance is to set the default before any measurement commands are sent.
No. It's a technical check of how consent is wired, not a judgement about whether a site complies with GDPR, UK GDPR or any other law. That's for the client's legal or compliance team.
Got an account that doesn't add up?
Send us one account. We review it for free and send a short video of what's working and what isn't.