Are you using Google Tag Manager to load Axeptio? We’ve prepared a full video tutorial just for you!
If you’re using Google services on your website, this concerns you! Failing to adopt it may result in non-compliance with regulations and could impact data collection in Google Analytics and Google Ads.
Configuration involves 2 main steps:
In the Axeptio administration interface, you’ll activate the dedicated screen for Consent Mode v2.
In your Axeptio integration and consent logic, you will:
Set default signals for the 4 Consent Mode parameters
Adjust your conditioning logic based on the Consent Mode v2 approach you choose (basic or advanced)
⚠️ Both steps are required for a valid Consent Mode v2 implementation!
💉 Need a refresher on what Consent Mode v2 is? Check out our blog post on the subject.
Enable the dedicated screen in your banner
First of all, you will need to activate Consent Mode at your cookie widget level.
With Axeptio, you can control 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 so, go to your widget configuration. Below the “classic” screens, you’ll find the “Enable Consent Mode v2 (step)” option:
Once this option is checked, a new screen will be added to your widget, including the 4 Google Consent Mode parameters:
Once enabled, don’t forget to republish your project!
Set default Consent Mode parameters
Here, you’ll configure the default values for each Consent Mode parameter—accepted or denied—before the user has made any choice.
This setup must be done where you load Axeptio.
For example:
If you use our WordPress module: configure it there.
If you use our script directly in your code: configure it in the script.
If you use GTM: configure it in GTM.
Find the section below corresponding to your integration method.
If you’re using Google Tag Manager
Don't feel like reading and want to watch a video tutorial instead? We've got your back!
First, you’ll need to retrieve our “Axeptio CMP” tag template from the Google Tag Manager Template Gallery.
🚧 If you’re already loading Axeptio in GTM via a Custom HTML tag, we recommend replacing it with the Axeptio CMP tag we’ll create here.
Go to Templates in your GTM container and click “Search Gallery”:
Search for “Axeptio CMP”. Once found, add it to your workspace:
Now that the template is added, let’s create a tag using it.
Go to the Tags section and create a new tag. For tag configuration, select “Axeptio CMP” as the tag type:
Fill in your Axeptio project ID and cookie version. This section controls Axeptio loading.
Reminder: if you were previously loading Axeptio in GTM another way, disable the old tag in favor of this one.
If you’re already using the Axeptio CMP template and these fields are filled, you can skip this part.
Now focus on the “Google Consent Mode v2” section of the tag.
There you’ll find a checkbox to enable Consent Mode v2 support.
Once enabled, new fields will appear:
You can now define default Consent Mode values based on region.
Click “Add Row”:
In the Region field, enter the region code this row applies to. Leave it empty to apply globally. Use ISO 3166-2 codes—e.g., “FR” for France.
Each of the 4 parameters has a dropdown to set its default value:
Granted
Denied
Reminder: the 4 Consent Mode parameters are:
analytics_storage: allows Google Analytics to track user interactions
ad_storage: allows Google to store ad-related data on the user’s device
ad_user_data: allows sharing of user activity data with Google for targeted ads
ad_personalization: allows Google to personalize ad experiences for the user
Here’s an example where ad_storage and analytics_storage are granted by default, while ad_user_data and ad_personalization are denied:
This is only an example—compliance recommendations may vary. For GDPR-covered EU visitors, we recommend setting all four parameters to “denied” by default.
Once done, confirm the row. You can create multiple rows, e.g. to configure different regions.
Example:
Default row: all parameters denied
US row: all parameters granted
You’ll end up with two rows like this:
This means visitors won’t be tracked by default—except US visitors.
As for the last two options:c
Redact Ads Data
Pass through URL parameters
These are optional behaviors explained via the “?” tooltip next to each.
All that's left is to load our tag at the right time, which is 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's left is to save your tag, and the Consent Mode is now active on your site! Congratulations
If you’re using the direct script integration
If you’re loading Axeptio via script, your setup likely looks like this:
<script>
window.axeptioSettings = {
clientId: "yourProjectID",
};
(function(d, s) {
var t = d.getElementsByTagName(s)[0], e = d.createElement(s);
e.async = true; e.src = "//static.axept.io/sdk.js";
t.parentNode.insertBefore(e, t);
})(document, "script");
</script>
Add a googleConsentMode object inside axeptioSettings, specifying the default status of each Consent Mode parameter—granted or denied before any user interaction.
As a reminder, here are the 4 parameters of the Consent Mode:
analytics_storage: allows Google Analytics to measure how the visitor uses the site
ad_storage: allows Google to save advertising information on the visitor's device
ad_user_data: allows the sharing of the visitor's activity data with Google for targeted ads
ad_personalization: allows the personalization of the visitor's advertising experience by allowing Google to customize the ads he sees.
Each of these parameters can be set by default either to "denied" or to "granted".
We will also pass a "wait_for_update" parameter which will allow to indicate to Google services to wait for consent for a set time before doing anything.
This parameter takes as value an integer, which corresponds to the number of milliseconds that this waiting period will last.
Another optional parameter is the "region" parameter, which allows to indicate default settings specific to a given region. This parameter takes as value the ISO 3166-2 code of the region. For example, for France, this code is "FR".
Here is an example in which the 4 parameters are accepted by default, for all regions combined, with a delay of 500 milliseconds, which is the standard waiting time.
window.axeptioSettings = {
clientId: "yourProjectID",
googleConsentMode: {
default: {
analytics_storage: 'denied',
ad_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied',
wait_for_update: 500,
}
}
};Let's now look at an example, where for all my visitors, everything is refused by default, except for those from the United States, where the Consent Mode parameters will be accepted by default.
window.axeptioSettings = {
clientId: "yourProjectID",
googleConsentMode: {
default: [
{
analytics_storage: 'denied',
ad_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied',
wait_for_update: 500,
},
{
region: ['US'],
analytics_storage: 'granted',
ad_storage: 'granted',
ad_user_data: 'granted',
ad_personalization: 'granted',
wait_for_update: 500,
}
]
}
};Once your settings are well defined, the Consent Mode is now active on your site. Congratulations!
If you’re using a CMS integration
Here we’ll show WordPress, but the same logic applies to other CMS modules.
In your WordPress admin, go to the Axeptio module. In the "Configuration" section, you will find a brand new option to activate Consent Mode v2.
If you don't see this option, check if you have the latest version of our WordPress module.
For each parameter, you can set its default value by checking or unchecking the box to the left of the parameter. If the box is checked, the parameter will be in "Granted" by default, whereas if the box is unchecked, the parameter will be in "Denied" by default.
It is recommended for your visitors from the Euro zone to set all four parameters to "Denied" by default, as in the example above.
Once your settings are done, don't forget to save your changes at the bottom of the page.
Consent Mode v2 is now activated on your site!
Basic or advanced Mode: which one to choose?
Google describes two operating modes of Consent Mode: basic mode and advanced mode.
Basic mode
In basic mode, your Google services should only be loaded after consent. This corresponds to a "classic" integration of Axeptio, where Axeptio will be the conductor who decides when Google services are loaded. To set up this integration, you can rely on our existing documentation:
If you load your Google services with Google Tag Manager: Google Tag Manager Interface
If you load your Google services with Gtag.js: Custom Integration / synchronization
With basic mode, you can be sure that nothing is loaded on your site before the visitor's consent!
Advanced mode
In advanced mode, your Google services will be loaded as soon as you arrive on the site, regardless of whether the visitor has already accepted cookies or not. This mode allows Google to make more precise models on visitors who have refused, by collecting anonymous data on them.
In this mode, you will therefore not have to control consent before loading your Google services.
For example:
in Google Tag Manager, you can load your Google tags on "All pages"
or if you load your Google services via Gtag.js, you can load the script directly without any conditions, as would be the case in a "classic" Axeptio integration.
With advanced mode, you give all their chances to your Google services to have the most qualified data!
📌 For more details, please refer to the official Google documentation.
Verify your Consent Mode v2 setup
Check your implementation using one of our tutorials:
About the old “Axeptio Consent Mode v2” tag template
About the old “Axeptio Consent Mode v2” tag template
🚧 If you previously followed our older documentation using the “Axeptio Consent Mode v2” tag template in GTM, you do not need to update your setup.
Also, you don’t need to enable the Consent Mode screen in the widget, because this older tag relies directly on the acceptance of Google Analytics and Google Ads.
Just make sure both services are properly configured in your Axeptio cookie widget.
The older tag will still work, but might not be maintained if future Consent Mode updates are released. You can update to the new method now if you wish, but it’s not required.
Need help?
If you notice issues related to missing Consent Mode or TCF signals on Google tags, please contact Axeptio first.