Free · no sign-up · 10 checks an hour

Check your Google Consent Mode v2 setup

Paste a URL. We load the page like a first-time visitor and check whether a consent default comes before gtag.js or Google Tag Manager, what ad_storage, analytics_storage, ad_user_data and ad_personalization start as, and which tags fire before anyone clicks.

Also in:ItalianoFrançaisDeutschEspañol

Free and anonymous: we don't keep the address you check. Up to 10 checks an hour. Privacy policy

What the checker looks at

  • 1

    Google tag and Tag Manager

    gtag.js, Google Tag Manager containers (we read up to three of them) and Google Ads tags, with their IDs.

  • 2

    A default before the tags

    gtag('consent', 'default', …) has to run before any config or event command and before Tag Manager loads. We check the order.

  • 3

    The four v2 signals

    ad_storage, analytics_storage, ad_user_data and ad_personalization should start as denied for visitors in the EEA, the UK and Switzerland.

  • 4

    Region-specific defaults

    If you only deny consent in certain regions, we list every EEA country, the UK and Switzerland that the default leaves out.

  • 5

    wait_for_update, url_passthrough, ads_data_redaction

    Whether each one is set, and when it's worth adding.

  • 6

    Banner and early tags

    Which consent tool loads, and which tags fire before consent. Consent Mode doesn't hold back Meta Pixel, TikTok or Hotjar.

What a static check can't see

The checker reads the page the way a first-time visitor's browser receives it. It doesn't run JavaScript or click your banner, so:

  • No JavaScript runs: the page, its response headers and its Tag Manager containers are read once, as a first-time visitor without consent.
  • Consent updates after someone clicks your banner can't be seen. Test Accept and Reject in Google Tag Assistant (Consent tab) or your browser's DevTools.
  • Defaults set inside a Tag Manager container or by a consent tool's own script can't be read from outside.
  • Visitors from other countries, signed-in users or bot protection can get a different page.

To see consent updates: open Google Tag Assistant (tagassistant.google.com), connect your site, click Accept or Reject on your banner and open the Consent tab. Each signal should only change from denied to granted for what the visitor accepted.

Fix it for free

Both set every Consent Mode v2 signal to denied before your tags, send the update when the visitor chooses and block other trackers until consent. No account, no licence key.

  • Rather self-host? Use the open-source banner

    One 8.9 kB file under the MIT licence with Accept, Reject, categories and Consent Mode v2. It never calls our servers.

    v1.2.1 · MIT · GitHub

  • Running WordPress? Install the free plugin

    A settings page in your dashboard, Accept and Reject with equal weight, Consent Mode v2 and script blocking. No outside requests by default.

    v1.2.3 · ZIP 281 kB · GPLv2+

The free pre-consent scan lists every cookie and tracker your page loads before anyone clicks, with a GDPR score.

Run the free scan

Want this checked every month?

PrivacyPill Pro rescans each of your sites every month and flags new trackers in your dashboard, with EU/EEA and California geo-targeting and unlimited domains.

Pro: €9 a month or €79 a year, excl. VAT.

See plans

Consent Mode v2 questions

What does a Consent Mode v2 checker test?

Whether your page tells Google tags what they may do before the visitor answers your banner: a gtag('consent', 'default', …) call that runs before gtag.js or Tag Manager, all four v2 signals (ad_storage, analytics_storage, ad_user_data and ad_personalization) starting as denied for visitors in the EEA, the UK and Switzerland, and the optional wait_for_update, url_passthrough and ads_data_redaction settings. It also lists tags that fire before consent.

What should the Consent Mode v2 defaults be?

For visitors in the EEA, the UK and Switzerland, all four signals denied until the visitor chooses. Google's setup guide treats a signal you don't set as granted, so leaving out ad_user_data or ad_personalization isn't the same as denying them. When the visitor chooses, your banner sends gtag('consent', 'update', …) granting only what they accepted.

Why does the order of the default matter?

Google's guide says the default has to run before any command that sends measurement data, such as config or event. If Google Tag Manager or gtag('config', …) runs first, the first data goes out without it. Put the default, or a banner script that sets it, as the first script in <head>.

What's the difference between basic and advanced Consent Mode?

In basic mode, Google tags don't load at all until the visitor consents. In advanced mode they load straight away with the signals denied and send cookieless pings, which Google uses to model conversions. The checker tells you which one your page uses when it can see it.

Do I need wait_for_update, url_passthrough and ads_data_redaction?

None of them is required. wait_for_update (for example 500 milliseconds) helps when your banner loads asynchronously, so tags wait for its update. ads_data_redaction removes ad click identifiers from Google Ads requests while ad_storage is denied, which is worth turning on when you run Ads. url_passthrough carries click information in your internal links so conversions can be measured without cookies.

Can the checker see what happens after someone clicks Accept?

No. It reads the page once without running JavaScript, so consent updates, tags that other scripts add later and anything behind a login aren't visible. Test those in Google Tag Assistant: click Accept and Reject on your banner and check the Consent tab.

Does Consent Mode block Meta Pixel, TikTok or Hotjar?

No. Consent Mode only changes how Google tags behave. Every other tracker has to be blocked until consent by your banner, for example by loading it as type="text/plain" with a category attribute. The checker lists those tags separately.

Can my AI assistant run this check?

Yes. The same check is a free REST endpoint (GET /api/public/v1/consent-mode-check?url=…) and a free tool, consent_mode_check, on PrivacyPill's MCP server at /mcp. Neither needs an account, and they share the limit of 10 checks per visitor per hour with this page.

Developer docs: REST endpoint and MCP setup

Sources

Google's own documentation on Consent Mode, read on 13 November 2026.