Google integrations
A CMP for Google Consent Mode v2
Connect banner choices to Google's four consent signals, decide Basic or Advanced behavior, and verify the real tag sequence in Tag Assistant.
For teams running GA4, Google Ads or GTM on an EU-facing site.
01 / The problem
A consent signal is easy to send at the wrong time
If the default arrives after a Google tag, the first request may already be gone. If Analytics and Advertising share one switch, a visitor's granular choice can turn into an unintended blanket grant. A CMP must coordinate the interface, defaults, updates and any required blocking.
Signs the setup needs a closer look
- No denied default on the first Tag Assistant event
- Analytics-only grants advertising signals
- A banner choice updates only after a reload
02 / What Consentory does
Consentory connects choices to Google and to other tags
The widget translates analytics or performance and advertising choices into Consent Mode v2 signals. Configure the default early in your actual GTM or gtag.js sequence, and use prior blocking when your chosen mode requires no Google requests before permission.
Four-signal mapping
Set analytics_storage separately from ad_storage, ad_user_data and ad_personalization.
Same-page updates
Send a consent update when the visitor accepts, rejects or changes preferences without relying on a reload.
Mode-aware controls
Use blocking for Basic behavior, or document denied-state pings when you intentionally use Advanced behavior.
03 / Technical implementation
A predictable implementation sequence
The exact code depends on whether GTM or direct gtag.js owns the default. Keep a single owner for each command.
- 01
Choose Basic or Advanced
Agree on what Google requests, if any, may happen before the visitor decides.
- 02
Set a denied default first
Use GTM Consent Initialization or an early head snippet before other Google tags evaluate consent.
- 03
Map the banner's categories
Keep Analytics and Advertising independent and update all four signals on the same page.
- 04
Inspect the event timeline
Use Tag Assistant and DevTools to check defaults, updates, tag firing, requests and storage.
04 / Evidence and verification
What a passing setup looks like
The immediate proof lives in the browser; GA4's administrative status may update later.
- First event
- The four expected defaults exist before relevant Google tags fire.
- Analytics-only choice
- analytics_storage changes to granted while the three advertising signals remain denied.
- Network behavior
- The trace matches the chosen Basic or Advanced mode, including pre-consent requests.
Keep exploring
Technical guides
Use these guides to check the details before you request access.
Related solutions
Choose the next question
Each page focuses on a different implementation decision.
05 / Request access
Check your Google consent setup
Share your GTM or gtag.js setup and the behavior you need before permission. We can scope a beta verification path.