Set up Google Consent Mode v2
By OptinStack Team - Jun 28, 2026 - 2 min read
Google Consent Mode v2 lets Google tags adjust their behavior based on the visitor's consent state. OptinStack maps its four categories onto the Google consent types and updates them whenever the visitor chooses.
For the full implementation reference, including dataLayer events and signal mapping, see the Google Consent Mode v2 docs page.
| OptinStack category | Google consent type |
|---|---|
| necessary | security_storage |
| analytics | analytics_storage |
| marketing | ad_storage, ad_user_data, and ad_personalization |
| preferences | functionality_storage and personalization_storage |
Enable Consent Mode v2
There is no separate project-wide dashboard switch for Google Consent Mode. If you install OptinStack directly on the page, the runtime's built-in Google consent bridge sets defaults from your banner mode and updates them when visitors change consent. If you use the OptinStack GTM template, leave the template's Enable Google Consent Mode v2 field turned on so GTM owns consent state inside the container.
When Global Privacy Control is enabled, OptinStack starts all optional consent types as denied, matching GPC's opt-out intent.
Related articles
Basic vs Advanced Google Consent Mode
Compare Basic and Advanced Google Consent Mode, including tag loading, cookieless pings, GTM settings, verification, and when each mode makes sense.
Integrate OptinStack with Google Tag Manager
Configure OptinStack with Google Tag Manager from start to finish, including the GTM template, Consent Mode v2 signals, defaults, triggers, consent settings, and testing.
The four consent categories explained
The four fixed consent categories: necessary, analytics, marketing, and preferences, and how their defaults behave.
Localize the banner and honor GPC
How default banner language, Business and Enterprise translation fetches, and Global Privacy Control defaults actually work in OptinStack.
How helpful was this article?