Consent Mode & Cookie Consent Checker — What Fires Before Consent?

Check a site’s cookie consent the way a regulator or an ad platform would. The page opens in a real browser and we record every tracking request and cookie before the visitor chooses — then we click Accept on the banner and record again. You see the consent banner in use, whether Google Consent Mode v2 sends denied signals first, and any pixels that fire too early.

Runs on our serverUpdated

Takes 10–25 seconds: the page opens in a real browser on devpack’s server (in the US — banners shown only to EU visitors may not appear).

This tool fetches the public URL you enter from our server. Results are held in temporary memory for a few minutes and never stored in a database.

How to use the Consent Mode Checker

  1. Enter the page URL — usually the home page, where most tags load.
  2. Keep Click Accept on to compare before and after consent.
  3. Click Check consent and wait while the page loads in a real browser.
  4. Read the verdicts: tags and cookies before consent, Consent Mode signals, and what Accept turns on. Fix problems with the Cookie Consent Banner Generator.

What it checks

  • Consent banner — OneTrust, Cookiebot, Usercentrics, CookieYes, Complianz, iubenda, Osano, Termly, Didomi, Quantcast, Axeptio, Finsweet, Cookie Script and devpack’s own banner are recognized, plus the IAB TCF and GPP APIs.
  • Before consent — every request to Google Analytics, Google Ads, Tag Manager, Meta, LinkedIn, TikTok, Pinterest, Microsoft Ads, X, Reddit, Snap, Hotjar, Clarity, Segment, Mixpanel, PostHog and HubSpot, and the tracking cookies they set (_ga, _fbp, _gcl_au, _uet…).
  • Google Consent Mode v2 — the gcs value on each GA4 hit: G100 means storage denied (a cookieless ping, which is allowed), G111 means granted. Hits with G111 before anyone clicked Accept mean consent defaults are missing or set to granted.
  • After Accept — we click the banner’s accept button and record again, so you can see that the tags you expect do turn on.

Reading the result

Under GDPR and the ePrivacy rules, marketing pixels and non-essential cookies need consent first. Google tags may load before consent when Consent Mode defaults are denied; they then send cookieless pings only. Since March 2024 Google also requires Consent Mode v2 signals for ads measurement in the EEA. This is a technical check from one visit, not legal advice. Related: Tracking & Pixel Checker, GA4 Request Decoder.

Also searched as: google consent mode v2 checker, cookie consent checker, gdpr cookie scanner, check cookies before consent, consent mode test, gcs parameter checker, cookie banner checker, tracking before consent.

Tools that pair well with the Consent Mode Checker

  • Google Tag Snippet Generator — Enter your GA4 measurement ID, Google Ads ID or Tag Manager container ID and get install code that is ready to paste — with Consent Mode v2 defaults, cross-domain linking, debug mode, manual page views and cookie settings switched on only when you need them.
  • Website Screenshot Tool — Enter a URL and get a full-page screenshot taken in a real Chrome browser — at desktop, tablet or phone width and up to 3× (Retina) resolution, with cookie banners hidden.
  • Event Tracking Script Generator — Track button clicks, links and form submits by adding attributes instead of code: data-track="sign_up_click" plus optional data-track-* parameters.
  • UTM Builder — Add utm_source, utm_medium, utm_campaign and friends to any link, see which GA4 channel the visit will land in, and tag a whole list of URLs at once.

Frequently asked questions

How do I check if Google Consent Mode v2 is working?
Run the check: if the first GA4 hits before consent carry gcs=G100 (or G101), defaults are denied and Consent Mode works. G111 before consent means the defaults are missing or set to granted.
Why does the checker see no cookie banner?
Many consent tools show banners only to visitors in the EU or UK, and the check runs from a US server. Your banner may still work for EU visitors; check with a VPN as well.
Is it OK that Google tags load before consent?
With Consent Mode defaults set to denied, yes: the tags load but store no cookies and send cookieless pings only. Marketing pixels like Meta or LinkedIn should wait for consent.
Why didn’t it click Accept?
It recognizes the common consent tools and buttons labeled Accept, Allow all, Agree and similar in several languages. Custom banners with other wording may not be clicked.

Related tools