As soon as you use Google services on your website, this concerns you! If you do not adopt it, your Google services will not be able to adapt their behaviour to your visitors' consent choices, and you risk a deterioration of measurements in Google Analytics and Google Ads.

The configuration takes place in 2 steps:

With Axeptio, you manage the Consent Mode signals directly from your cookie banner. In just a few clicks, you can activate a dedicated screen for managing Consent Mode v2.

To do this, go to your widget configuration.

Under the "classic" screens, you will find the option "Enable Consent Mode v2 (step)":

By checking this option, a new screen will be added to your widget, with the 4 Google Consent Mode parameters:

Once the option is checked, don't forget to republish your project!

Here, you will configure the default values for Consent Mode, i.e. for each parameter, whether it will be accepted or denied, before any choice made by the user.

This configuration must be done in the same place where you load Axeptio.

For example, if you load Axeptio via our WordPress module, the configuration will be done in that module. If you load Axeptio directly via our hardcoded script, the change will be made directly in the script. And if you load Axeptio via GTM, it will be done in GTM.

Go to the section corresponding to your Axeptio integration method below!

First, you will need to retrieve our "Axeptio CMP" tag template, available in the Google Tag Manager tag gallery.

🚧 Note: if you are already loading Axeptio in GTM via a custom HTML tag, it is recommended to replace that tag with the Axeptio CMP tag we are about to create here.

To do this, go to the "Templates" section in your GTM container, then click "Search Gallery":

Search for "Axeptio CMP" in the window that opens. Once found, add it to your workspace:

Now that the template has been added, we can create a tag from it.

Go to the "Tags" section of your container and create a new one.

In your new tag's configuration, select the "Axeptio CMP" template:

Then fill in your Axeptio project ID and the cookie version in the corresponding fields. This is the section that will handle loading Axeptio.

As a reminder, if you were already loading Axeptio via GTM in another way, you will need to disable the old tag in favour of this one.

If you were already using the Axeptio CMP template to load Axeptio and these fields are already filled in, you can skip this step.

We will now look at the "Google Consent Mode v2" section of this tag.

You will find a checkbox to enable Consent Mode v2 support.

Once checked, new fields will appear:

Here we can define the default Consent Mode values, by region.

Click "Add a row".

In the "Region" field, enter the region code to which these default parameters will apply. If you leave this field empty, it will apply to everyone. This field must be filled in according to the ISO 3166-2 standard — for example, for France the code is "FR".

You then have a dropdown menu for each of the 4 Consent Mode v2 parameters. For each parameter, you can set whether it will be Granted (accepted) or Denied (refused) by default. As a reminder, here are the 4 Consent Mode parameters:

Here is an example where the ad_storage and analytics_storage parameters are accepted (granted) by default, while ad_user_data and ad_personalization are denied by default. This is only an example and regulations may vary by region.

Once the various fields are filled in, you can confirm the addition of your row.

Note that it is possible to create multiple rows, in particular to have different configurations depending on regions.

For example, I will create a default row, and a specific row for the United States.

In my default row, I will set all 4 parameters to Denied, while in the one for the United States, everything will be Granted. I then get two rows like this:

With this configuration, my visitors will not be tracked by default, except for visitors coming from the United States.

Regarding the last two options "Redact Ads Data" and "Pass through URL parameters", these are additional behaviour options explained when hovering over the "?" next to the option.

All that remains is to fire our tag at the right moment — as early as possible!

To do this, go to the "Triggering" section of your tag, and add a "Consent Initialization - All Pages" trigger like this:

All that remains is to save your tag, and Consent Mode is now active on your site! Congratulations

If you load Axeptio directly via our script, you should have something like this:

We are going to add a googleConsentMode object to the axeptioSettings object, which will contain the default Consent Mode parameters — i.e. for each parameter, whether it is accepted or denied before any choice by the user, from the moment they arrive on the site.

As a reminder, here are the 4 Consent Mode parameters:

Each of these parameters can be set by default to either "denied" (refused) or "granted" (accepted).

We will also pass a "wait_for_update" parameter which will tell Google services to wait for consent for a defined period of time before doing anything.

This parameter takes an integer value, corresponding to the number of milliseconds that this waiting period will last.

Another optional parameter is the "region" parameter, which allows you to specify default parameters for a given region. This parameter takes the ISO 3166-2 code of the region as its value. For example, for France, this code is "FR".

Here is an example in which all 4 parameters are denied by default, for all regions, with a 500-millisecond delay, which is the standard waiting period.

Now let's look at an example where, for all my visitors, everything is denied by default, except for those coming from the United States, where the Consent Mode parameters will be accepted by default.

Once your parameters are properly defined, Consent Mode is now active on your site. Congratulations!

Find other integrations here.

Google describes two operating modes for Consent Mode: basic mode and advanced mode.

In basic mode, your Google services must only be loaded after consent. This corresponds to a "classic" Axeptio integration, where Axeptio acts as the orchestrator deciding when Google services are loaded. To set up this integration, you can rely on our existing documentation:

With basic mode, you can be sure that nothing is loaded on your site before the visitor's consent!

In advanced mode, your Google services will be loaded as soon as the visitor arrives on the site, regardless of whether they have already accepted or refused cookies. According to Google, this mode allows more precise modelling of visitors who have refused, by collecting anonymous data about them.

In this mode, you will therefore not need to control consent before loading your Google services.

For example:

When a visitor refuses cookies in advanced mode, Google services continue to operate in cookieless mode: they do not use cookies and do not perform any individual targeting. Only anonymous signals are sent to Google to allow it to model unobserved conversions.

With advanced mode, you give your Google services every opportunity to get the highest-quality data!

📌 For more details, we invite you to consult the official Google documentation.

For your Consent Mode v2 implementation to be complete, Google requires that your consent banner meets three specific requirements:

When you add Google Analytics 4 or Google Ads to your Axeptio banner, the dedicated Consent Mode v2 screen is automatically activated. This screen presents the 4 Consent Mode parameters with the information and link required by Google — the three requirements above are thus satisfied without any additional action.

You can verify the correct implementation of Consent Mode v2 by following one of the tutorials below:

To go further on Consent Mode parameters and operation, consult the official Google resources:

If you detect issues related to the absence of Consent Mode or TCF signals on Google tags, contact Axeptio in the first instance.