This article describes all available fields in the Axeptio CMP GTM template. For step-by-step installation instructions, see Integrate Axeptio via Google Tag Manager.
Project ID
Required. The identifier of your Axeptio project. How to find your project identifier.
Cookies Version
Identifier of the cookie configuration to load. If you have only one configuration, leave this field empty. If you have multiple configurations and this field is empty, Axeptio will load the first configuration listed in your admin.
Cookie settings
Default values are suitable for most cases.
User cookies duration (in days)
Duration of storage for the cookie that stores user choices, in days. Default: 180 days.
User cookies domain
Domain on which the consent cookie is placed. If this field is empty, the cookie is placed on the current domain.
Fill in this field if you want to share consent across multiple subdomains (e.g. axept.io to cover www.axept.io and app.axept.io). For more information: Share consent between main domain and subdomains.
User cookies secure
When checked, the consent cookie is placed over HTTPS only. Default: checked.
Uncheck only if your site serves HTTP (local development environment, for example).
dataLayer Name
If you use a custom name for the dataLayer (e.g. customDataLayer), enter it here so Axeptio sends its events to the right place. Default: dataLayer.
Trigger GTM Events
Determines which Axeptio events are sent to the dataLayer, allowing you to reduce event volume or manage triggers differently depending on the case. Default: True.
Value | Behavior |
True | All events are sent (axeptio_activate_*, axeptio_update, etc.) |
Update Only | Only axeptio_update is sent (useful if you don't want to multiply events) |
False | No events are sent (reserved for cases where you only rely on cookies or JS variables) |
Server-side
Server-side URL
URL of your client's server-side infrastructure (e.g. metrics.domain.com). Leave empty if you are not using an Axeptio server-side configuration.
â ïž Warning â As soon as this field is filled in, consent requests will be routed to the specified infrastructure instead of Axeptio servers. Make sure your infrastructure is properly configured to handle /consents requests before filling in this field. Otherwise, your visitors' consents will no longer be collected in the Axeptio consent registry.
For more information: Server-side tracking.
Google Consent Mode v2
This section is only useful if you use Google services (Google Analytics 4, Google Ads, etc.) on your site.
For a complete explanation of Consent Mode and configuration instructions, see Configure Google Consent Mode v2.
Activate Google Consent Mode v2
Check this box to enable Consent Mode v2 support by the template. When checked, the template sends the gtag('consent', 'default', âŠ) command on load, before any Google tags.
When unchecked, no consent signal is sent. Google tags behave as if Consent Mode is not enabled.
Google Consent Mode â Default Settings
Table that defines the default values of the 4 Consent Mode parameters, by region. These values apply as soon as a visitor arrives on the site, before making any choices.
Column | Description |
Region | Region code in ISO 3166-2 format (e.g. FR, US). Leave empty to apply the row to all regions. |
Analytics storage | Allows Google Analytics to measure visitor behavior |
Ad storage | Allows the placement of Google advertising cookies on the visitor's device |
Ad user data | Allows the sharing of visitor activity data with Google Ads |
Ad personalization | Allows personalization of Google ads |
Each parameter can be set to Denied (refused by default) or Granted (accepted by default). For European visitors subject to GDPR, all 4 parameters must be set to Denied.
The template automatically applies a wait_for_update delay of 500 ms: GTM waits up to 500 ms for the Axeptio SDK to transmit the choices of a returning visitor before letting Google tags execute.
Redact Ads Data
When ad_storage is set to Denied, this option masks additional advertising data (click information in URLs, advertising third-party cookies) sent to Google.
Pass through URL parameters
Transmits advertising parameters present in the URL (e.g. gclid, fbclid) even when ad_storage is set to Denied. Allows Google to model unobserved conversions (Google documentation on URL passthrough).
This option can be activated in the Axeptio administration, directly in Google Tag Manager, or in both places â both settings work with OR logic. By default, it is disabled. Simply enabling one of the two settings is sufficient for URL passthrough to take effect; it is not necessary to enable it in both places.
Additional Axeptio Settings
Key/value table that allows you to pass advanced SDK parameters directly from GTM.
Column | Description |
Key | Name of the SDK parameter to set or override |
Value | Associated value |
For the complete list of available parameters, see Advanced options â axeptioSettings.