Gravito CMP · Consent

One script, set up with you, updated without touching your sites.

Gravito CMP is a consent management platform (CMP) that serves TCF 2.4 on the web, IAB GPP (Global Privacy Protocol) and the Google, Microsoft and Amazon consent signals from a single script.

Book a demo See pricing

Illustration: Gravito's G at the centre of concentric orange circles

Consent that runs wherever your sites do.

One deployment applies the right framework for each region: TCF, GPP, a standard banner or no banner.

Every signal from one choice.

The visitor decides once; the CMP passes that choice to Google, Microsoft, Amazon and the ad chain in the form each one reads.

Configure once, publish everywhere.

One account for many domains; every published version is served through the same address.

A team behind the technology.

Our team does the wiring with you, and stays on after launch.

Load order

Loads first, so everything after it gets the right answer

The CMP is the first thing on the page: before your tag manager, your analytics and your ad stack. That is where the consent state is set, and it is the only point from which every system after it can be told the same thing at the same time.

A CMP does not stop tags from running by itself. It gives each system the visitor's choice in the form that system reads, such as a TCF string, a GPP string or Consent Mode parameters, and those systems act on it.

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

Decisioning layer

One decisioning layer for every region

For each region, the decisioning layer applies whichever framework or configuration fits: TCF, GPP, the Standard CMP with your own consent categories, or no banner where none is needed.

Your site tells the CMP the visitor's region, typically from your CDN, and the decisioning layer applies the rest. We configure it during implementation. After that, you choose who maintains it: your own team in the self-service configurator, our team, or a service provider you choose.

Decisioning layer

Example configuration

EEA IAB TCF
United Kingdom IAB TCF
California IAB GPP
Texas IAB GPP
Brazil Standard CMP
Elsewhere No banner

Your site supplies the region. Each region gets the framework or configuration set up for it.

Deployment

Configure once. Publish everywhere.

You configure the CMP in the Gravito Configurator and publish. The same published configuration is available as:

Script

A deployment script for websites
WebView URL

A URL for apps that show the CMP in a WebView
Google Tag Manager

A token for the Google Tag Manager template
WordPress

A token for the WordPress plugin

Each new version goes live at the same address, so nothing changes on the site itself, and earlier versions can be restored from the version history.

A Gravito CMP consent banner on a laptop and a phone

Your banner, in your brand and your visitors' language

The banner is built to look like part of your site: layout, colours, fonts, logo and texts are yours to set. We deploy it in whatever language your audience needs. The interface is lightweight, built on Preact.

Web and apps from the same configuration

Apps show the same CMP in a WebView, with platform bridges for iOS, Android, React Native and Flutter. The app stores the standard IAB keys, so the other SDKs in the app can read the choice too.

Consent memory

364

days, by default

Consent that is remembered

By default the CMP remembers the visitor's choice for 364 days and does not show the banner again in that time; after that, it asks for a new decision. You can set a shorter period, for example on legal advice.

The choice is also kept as a secure copy server-side, in your first-party context, on the same 364-day default. It is the record of what the visitor chose, and for a signed-in visitor it is what restores the choice when the browser has lost it. Where a strong legal reason applies, that copy can be kept for longer.

Know what your site sets

An automated cookie scan finds the cookies on your domains. You review the result, add what a scan cannot see, translate it and publish.

Multisite publishers: one choice across your sites

Consent can be bridged across your domain network: bridging consent is a feature of the Gravito CMP configurator, and we set it up.

Consent for signed-in users

Gravito CMP can connect a visitor's consent preferences to their signed-in account. If the browser loses its connection to them, for example after cookies are cleared, their preferences are restored when they sign in again. This works with whichever customer identity or access management system you run; it is not tied to a particular one.

Consent-or-pay, and other models

Because consent can follow the signed-in user, the CMP can carry models such as consent-or-pay, where visitors choose between consenting and a paid option. Consent-or-pay is one example of what can be built with Gravito CMP, and your subscription system stays your own. Which model fits your sites is your decision, with your legal team; we build it with you.