Free tool · Consent Mode v2 checker
Consent Mode tells Google tags what a visitor agreed to. This check reads the consent signals your homepage sends and flags setups that leave out the v2 settings or set the default too late.
What this checks
Each item is something the scan records from the browser or reads from your published Tag Manager container.
Basic mode keeps Google tags blocked until the visitor chooses. Advanced mode lets them load first and send cookieless pings while consent is denied. The check reports which one it sees. Picking between them is a decision for your team, based on your banner and your privacy commitments.
Version 2 adds ad user data and ad personalization to analytics storage and ad storage. Google says consent is required in the European Economic Area, the United Kingdom and Switzerland, and that ad_user_data is required in regions that need end-user consent. The check looks for both signals in the defaults and updates it captures.
The default consent state has to be set before the first Google tag fires. If a Google request goes out before any default, it carries no consent state, and the check flags it.
After a visitor clicks Accept, the new consent state should reach Google. If it does not, Google keeps the default, and the check reports it.
Some ad tags in Google Tag Manager have a consent setting and some do not. A tag without one does not read the signals above, so the check reports the ad tags it can see in that position.
What the results mean
Each result says what the check saw. Some are information, and some are gaps to fix. The gaps from this check are listed first, then any other gaps the scan found.
Google tags wait for consent before sending anything. This is an information note about your setup, not a fault. Confirm it matches what your banner says.
Google tags load on page open and send cookieless requests before consent. This is also information only. Check that your banner and privacy notice describe it.
A Google request was sent before the default was set, so it had no consent state. Move the default above every Google tag in the container.
Only the older v1 signals were found. Add ad_user_data and ad_personalization to the default and the updates.
Accept was clicked, but no consent update reached Google. Google kept the default state after the visitor agreed.
Your site shows a consent banner, but the Google requests we saw carried no Consent Mode signals. The banner and Google’s tags are not connected.
How to fix it
Each one is a change to your site or your tag setup. Your team decides how to make it.
The consent default belongs at the top of the container, above every Google tag. Use Tag Manager preview mode to confirm the default event fires first.
Include ad_user_data and ad_personalization in the default and the update, next to analytics and ad storage. A consent platform may already handle this, so check its settings.
Pick one mode with your team and make sure the banner text describes it. Do not switch modes without retesting the banner.
Accept and Reject should both send a consent update that Google receives. Check the consent events in Tag Assistant after you click each button.
Limits
The limits of one homepage load, so you can read the result correctly.
Read more
Background reading for the same setup, with the steps behind each fix.
Other free checkers
The other free checks run the same scan and list the gaps for their own topic first.
Many sites load ad and analytics tags as soon as the page opens. This check loads your homepage once and records what fires before any choice is made on the banner.
A Reject button should stop optional tracking. This check clicks Reject on your homepage in a separate pass and records what keeps running afterwards.
A Meta Pixel that loads twice, or sends the same page view twice, can inflate the numbers Meta reports. This check counts what your homepage sends to Meta and shows where the Pixel is set up more than once.
A Google Ads conversion only counts if a tag sends it to Ads. This check reads how your conversions are set up in your published Tag Manager container and whether they are sent to Google Ads.
This check looks at what your homepage sends to Google Analytics 4. It flags setups with more than one property, retired Universal Analytics tags, and repeated page views.
Ad and analytics tags sometimes send personal details inside page addresses or request data. This check looks for categories, such as an email field, and never stores the values. It is built with healthcare and banking sites in mind, but any site can run it.
This check reads the published Tag Manager container your homepage loads. It looks at how the container is set up, not only at what reaches the browser.
When a visitor clicks an ad and fills in a form, the campaign details have to survive the trip. This check follows links to your lead pages and looks for the fields that carry them.
FAQ
Answers to the questions we hear most about this check.
Free Tracking Scan
Enter your website and we check your live site, then list every gap we find, starting with this check’s. No call needed.
