Blocking & consent
Google Consent Mode v2
How CookieRay tells Google's tags what each visitor allowed, and the exact signals it sends.
Google Consent Mode lets Google’s tags (Analytics, Ads) know what a visitor allowed instead of being blocked outright, so measurement keeps working in a modelled form. CookieRay supports version 2, and it is on by default.
The default, before anyone answers
Before any Google tag runs, CookieRay sets every signal to denied except the two that are always allowed:
| Signal | Default |
|---|---|
ad_storage |
denied |
ad_user_data |
denied |
ad_personalization |
denied |
analytics_storage |
denied |
personalization_storage |
denied |
functionality_storage |
granted |
security_storage |
granted |
It also asks Google’s tags to wait briefly (wait_for_update: 500) for the visitor’s answer.
When the visitor answers
| Visitor allows | Signals granted |
|---|---|
| Marketing | ad_storage, ad_user_data, ad_personalization |
| Analytics | analytics_storage |
| Functional | personalization_storage |
CookieRay also stops other scripts on the page from sending a “granted” update before the visitor has actually answered.
Turning it off
Consent Mode can be switched off in Settings, but leaving it on is one of the checks in your compliance score.