Consent Mode signals
Supported signals include ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, and security_storage.
Integrations
Google Consent Mode for recorded purposes
When you enable Google Consent Mode for a website, Consent Guru can translate purpose choices into the consent signals Google tags expect.
Tags and banners that disagree create silent collection
Google tags can read consent signals such as ad_storage, ad_user_data, ad_personalization, and analytics_storage. If the banner stores a choice that never reaches those signals, the tag stack and the notice diverge.
Consent Guru’s SDK can set a default denied state for optional storage and update it after a recorded choice, when Consent Mode is enabled for that website.
How Consent Mode v2 is applied
Step 1
Enable it
Turn on Google Consent Mode in the website’s regulation settings. It is off until you enable it.
Step 2
Map purposes
Default mappings send analytics-style purposes to analytics_storage and advertising-style purposes to ad_storage, ad_user_data, and ad_personalization.
Step 3
Default deny
Before a choice, optional ad and analytics storage can start as denied, with a short wait for the CMP update.
Step 4
Update
After the visitor chooses, the SDK updates the signals to match the purposes they allowed.
Key capabilities
Purpose map
You can adjust which purposes drive which signals instead of accepting the defaults blindly.
Tag loader control
The SDK can also pause known Google tag loader URLs when the mapped purpose is denied. Tags already configured inside a container still need their own checks.
Ads data redaction
Ads data redaction defaults to on in the Consent Mode configuration. URL passthrough is off unless you enable it.
What teams use it for
- Google tags see the same purposes the banner recorded.
- A default that does not treat optional storage as granted.
- A mapping you can inspect, not a hidden global switch.
- A path that still keeps your own consent record.
Google Analytics
Tie measurement purposes to analytics_storage.
Advertising tags
Tie marketing purposes to ad storage and ad user-data signals.
Tag managers
Use Consent Mode alongside, not instead of, consent checks inside the container.
Privacy considerations
Google Consent Mode is a signaling protocol. It does not decide whether you have a lawful basis, and enabling it is not GDPR or DPDP compliance.
The integration updates signals for tags that respect Consent Mode. It cannot retract a request a tag already sent before the SDK ran.
Technical capabilities
Wait for update
The default wait is 500 milliseconds and can be configured between 0 and 5000 milliseconds.
Region behavior
You choose where the experience applies. The product does not infer a country rule unless you configure it.
Questions
1.What is Google Consent Mode?
It is Google’s mechanism for tags to adjust storage and ads behavior based on consent signals such as analytics_storage and ad_storage.
2.What is Google Consent Mode v2?
Version 2 adds ad_user_data and ad_personalization alongside the earlier storage signals. Consent Guru’s signal list includes those fields when the integration is enabled.
3.Does Consent Mode replace a cookie banner?
No. The banner collects the choice. Consent Mode tells participating Google tags how to behave after that choice.
Related pages
- IntegrationsConsent Mode, tag control, and webhooks.
- Cookie consent managerThe categories those signals should follow.
- Consent Mode articleA plain-language explanation of the signals.
This page describes how Consent Guru supports privacy operations. It is not legal advice, and using the product does not by itself make an organization compliant with GDPR, CCPA, CPRA, the DPDP Act, or any other law.