Free Google Consent Mode v2 checker
Is Google Consent Mode v2 really on?
Most guides tell you to open DevTools and decode Google's network hits by hand. Paste your address and we do it for you in a real browser: we read the consent signals Google tags send before a visitor has chosen anything, then check the cookie banner too.
What we test
Ad consent starts as denied
We read the gcs and gcd values on Google Analytics and Google Ads hits before any choice. Ad storage, ad user data or ad personalisation set to granted is flagged.
PECR Reg. 6 · ePrivacy Art. 5(3)
Consent Mode v2 signals present
Hits with no consent signal, or only the older v1 fields (no ad_user_data / ad_personalization), are flagged as a warning.
PECR Reg. 6 · ePrivacy Art. 5(3)
Trackers firing before consent
Every analytics and ad tag that sends data before your banner is touched.
PECR Reg. 6 · ePrivacy Art. 5(3)
Rejecting really stops tracking
We click 'Reject' and watch for tags that keep firing anyway.
UK/EU GDPR Art. 7 · PECR Reg. 6
What your free report shows
Free
- Your Risk Score and risk band
- Pass or fail on Consent Mode and each cookie test
- The law each test relates to
- Full detail and fix for 1 lower-risk issue
Paid plans
- The exact Google hits and consent values we saw
- Full detail on serious issues
- Step-by-step fixes for your tag setup and consent tool
- Screenshot evidence and PDF export
Not a 12-step DevTools tutorial
| Halvus | Typical free checker | |
|---|---|---|
| No browser extension or DevTools | Yes | Manual network inspection |
| Reads real gcs / gcd values before consent | Yes | Often only checks the tag is installed |
| Spots v1-only setups | Yes | Rarely |
| Clicks 'Reject' and re-checks | Yes | No |
| Consumer law, accessibility, security too | Yes | No |
Questions
How do I check if Google Consent Mode v2 is enabled?
Load your site without clicking the cookie banner and look at the Google Analytics or Google Ads requests it makes. Consent Mode v2 adds gcs and gcd values that show whether ad_storage, analytics_storage, ad_user_data and ad_personalization are granted or denied. Halvus reads these for you in a real browser and tells you if any start as granted.
What does the gcd parameter mean?
gcd is Google's encoded consent state sent on each hit. It carries the default and updated value of each consent type. Letters in it show whether a signal is denied or granted and whether that came from a default or a visitor's choice. Halvus decodes it so you don't have to.
What's the difference between Consent Mode v1 and v2?
v2 adds two signals, ad_user_data and ad_personalization, on top of ad_storage and analytics_storage. Google requires them for advertisers using its ad features with visitors in the EEA and UK. A site sending only v1 fields is flagged as a warning.
Is Google Consent Mode v2 GDPR compliant?
Consent Mode is a way of passing your visitor's choice to Google tags; it doesn't make a site compliant on its own. Ad signals must start as denied, and non-essential cookies must not be set before consent under PECR and the ePrivacy Directive. Halvus checks both.
Do I need Google Consent Mode v2?
If you use Google Ads or Google Analytics with visitors in the UK or EU and want ad measurement and audiences to keep working, Google expects Consent Mode v2. If no Google tags load on your site, this check is marked not applicable.
Is the checker free?
Yes. You can scan any website once a day for free with no sign-up. Paid plans unlock full evidence, fixes and regular monitoring.
Will it tell me my site is compliant?
No. Halvus reports the risks it finds with evidence. It is not legal advice and never certifies a website as compliant.
Halvus reports risks found, not legal advice.