Google Consent Mode

Google Consent Mode v2 support in Gravito CMP

Whatever the region, Gravito CMP starts the consent framework that applies there, and the Google Consent Mode v2 signals are in place for anything that reads them. Gravito CMP is on Google's list of certified CMPs, for web and app, and sends the signals from the same script that runs the consent banner: a default before Google tags run, and an update whenever the visitor's choice changes.

Read the documentation Contact Consent Mode support

Page load, in order

1
Consent Mode default before Google tags run
2
Google tags adjust their behaviour
3
Update whenever the visitor's choice changes

Consent Mode v2 signals

ad_storage
analytics_storage
ad_user_data
ad_personalization
functionality_storage
personalization_storage
security_storage

What this page covers

This page describes how Gravito CMP supports Google Consent Mode, with a link to the documentation for each point. Consent Mode is not a banner and not a legal compliance solution; it works together with the CMP, and the site owner remains responsible for obtaining any consent that is required. Nothing on this page is legal advice.

Certified and registered

Google

Gravito is a Google Certified CMP Partner. Gravito CMP appears on Google's list of certified CMPs as "Gravito CMP", ID 302, web and app.

Google's list Google's partner directory
IAB Europe

Gravito is registered with IAB Europe as a TCF CMP, ID 302.

How the CMP sends Consent Mode signals

Consent Mode tells Google tags, such as Google Analytics and Google Ads, what the visitor has agreed to, and the tags adjust their behaviour. Gravito CMP sets the Consent Mode default before Google tags run and sends an update whenever the visitor's choice changes. It covers all seven Consent Mode v2 signals: ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage and security_storage.

Consent Mode is switched on in the CMP configuration, for both the TCF CMP and the Standard CMP. A site that does not want it leaves it switched off.

Configured in the Admin Portal

The banner, its texts and its Consent Mode settings are configured in the Gravito Configurator in the Admin Portal, and published from there.

Advanced and Basic mode

You choose the mode in the configuration. Advanced mode is on by default; switching it off gives Basic mode.

Advanced mode

Google tags load straight away and adjust their behaviour to the consent signals. When ads consent is declined, Google still receives basic, non-identifiable interaction data, which is not used for personalised advertising or for measurement that requires consent.

Basic mode

Google tags do not fire until the visitor gives consent, and no data is sent to Google before that. In Basic mode the deployment script carries the place for your Google Tag Manager snippet, and the Google Tag Manager template is not available as a deployment option.

Which mode fits a site is the site owner's decision. We set it up with you during implementation.

TCF and Google tags

In a TCF configuration, the CMP enables advertiser consent mode in the TCF data, so Google tags can read the advertising signals from the TCF string.
analytics_storage is sent alongside the TCF string. In the TCF CMP, ad_storage, ad_user_data, ad_personalization and analytics_storage come pre-mapped to TCF purposes.

Load order

The Consent Mode default has to be in place before Google tags run. Gravito CMP is built to load first, before your tag manager, analytics and ad stack. Our documentation shows how to load the TCF stub at the very top of the page, and how to start a Google tag only after the CMP's default is in place, using the CMP's gcmConsentUpdated event.

Page load, in order

1
Gravito CMP sets the consent state
2
Tag manager reads it
3
Analytics reads it
4
Ad stack reads it

Google Tag Gateway

With Google Tag Gateway, Google tags may be served from your own domain, which changes how tag loading and consent order should be handled. Gravito CMP works with Google Tag Gateway when the Consent Mode default is in place before the tags run. Our documentation explains how Google Tag Gateway changes tag loading, how to check in Google Tag Manager whether it is enabled for a domain, and three ways to resolve late consent, with links to Google's own documentation.

Google Tag Gateway documentation

Deployment and the Google Tag Manager template

The same configuration runs as a deployment script on the site, or through the Gravito Consent Management template in the Google Tag Manager Template Gallery.

Testing and support

Our support team provides tooling, including a browser extension and sample scripts, to check that Consent Mode is set up correctly on your site: you can see the consent values move from denied to granted in the dataLayer. Consent Mode questions have their own support address, gcm.support@gravito.net.

Signal mapping in detail

TCF CMP: functionality_storage, personalization_storage and security_storage map to your own settings, each with a default value you set.
Standard CMP: each of the seven signals maps to one of your own consent categories, with default mappings you can change.
Additional Consent Mode: Google's Additional Consent Mode can be switched on in a TCF configuration. In apps, the Additional Consent string is stored alongside the TCF data.

Published once, live everywhere

Every published version goes live at the same address, so nothing changes on the site. Our team sets up Consent Mode with you as part of implementation, and stays with you after it.