Google Consent Mode v2
Consent Mode v2 wired correctly — no modelled-conversion mystery, no drift between the banner and Google Ads.
Google Consent Mode v2 works well when the signal is honest and consistent. Most implementations aren't — the banner and Google Tag Manager disagree on what "denied" means, the CMP silently changes state on route changes, modelled conversions drift further from reality every quarter. Gravito is the CMP that treats Consent Mode v2 signalling as a first-class API.
What the platform gives you.
TCF strings, GPP signals and Consent Mode v2 events stay aligned in the same tick — no drift between what each downstream tool sees.
Consent state is replayed to Google Ads server-side, so the signal doesn't depend on the browser being cooperative.
Every state change — banner interaction, preference update, route change — is stamped with a timestamp and the reason it changed.
The Consent Mode signal Google Ads receives matches the consent event in your warehouse. Modelled conversions stop drifting.
What we hear from teams like yours
- Consent Mode is running but Google Ads reporting looks nothing like reality
- The banner and Google Tag Manager disagree on what "denied" means
- Consent state silently changes on route changes and hurts modelled conversions
- The audit trail for what state was live at any moment doesn't exist
TCF, GPP and Consent Mode v2 in the same tick.
Gravito treats consent as a single event that produces three synchronised signals — TCF, GPP and Consent Mode v2. All three fire in the same tick, from the same source of truth, so downstream tools don't disagree with each other or with your warehouse.
- ◆ One consent event, three synchronised outbound signals
- ◆ Server-side replay for tools that miss browser events
- ◆ Audit trail shows exactly which signals were live at any moment
The number Google reports matches the number in your warehouse.
When Consent Mode is wired correctly, modelled conversions should reconcile with your first-party data. When it's wired wrong, they drift. Gravito's server-side replay to Google Ads means the same consent event lands on both sides — and the reconciliation stops being a project.
- ◆ Server-side Enhanced Conversions with the consent state attached
- ◆ Modelled conversions reconcile with warehouse events by default
- ◆ Signal-quality dashboard shows where the two ever diverge
What customers see
The signal Google actually wants
Consent Mode v2 works well when the signal is honest and consistent. Gravito makes that the default — and gives you the audit trail to prove it every time your analytics team wonders why the numbers don’t match.