This article describes all the fields available in the Axeptio CMP GTM tag template. For step-by-step installation instructions, see Integrate Axeptio via Google Tag Manager.
Project ID
Required. Your Axeptio project identifier. How to find your project ID.
Cookies Version
Identifier of the cookie configuration to load. If you only have one configuration, leave this field empty. If you have several and this field is empty, Axeptio will load the first configuration listed in your admin.
Cookie settings
Default values work for most cases.
User cookies duration (in days)
How long the cookie storing user choices is kept, in days. Default: 180 days.
User cookies domain
Domain on which the consent cookie is set. If left empty, the cookie is set 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). Learn more: Share consent between main domain and subdomains.
User cookies secure
When checked, the consent cookie is set over HTTPS only. Default: checked.
Uncheck only if your site serves HTTP (e.g. local development environment).
dataLayer Name
If you use a custom dataLayer name (e.g. customDataLayer), enter it here so Axeptio sends its events to the right place. Default: dataLayer.
Trigger GTM Events
Controls which Axeptio events are sent to the GTM dataLayer, allowing you to reduce event volume or manage triggers differently. Default: True.
Value | Behaviour |
True | All events are sent ( |
Update Only | Only |
False | No events are sent (reserved for cases where you rely only on cookies or JS variables) |
Server-side
Server-side URL
URL of your client's server-side infrastructure (e.g. metrics.yourdomain.com). Leave empty if you are not using Axeptio server-side tracking.
â ïž Warning â As soon as this field is filled in, consent requests will be routed to the specified infrastructure instead of Axeptio's servers. Make sure your infrastructure is correctly set up to handle /consents requests before filling in this field. Otherwise, visitor consents will no longer be collected in the Axeptio consent registry.
Learn more: Server-side tracking.
Google Consent Mode v2
This group is only relevant if you use Google services (Google Analytics 4, Google AdsâŠ) on your site.
For a full 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 in the template. When checked, the template sends the gtag('consent', 'default', âŠ) command on load, before any Google tags fire.
When unchecked, no consent signals are sent. Google tags behave as if Consent Mode were not active.
Google Consent Mode â Default Settings
Table that defines the default values for the 4 Consent Mode parameters, by region. These values apply as soon as a visitor lands on the site, before any choice is made.
Column | Description |
Region | ISO 3166-2 region code (e.g. |
Analytics storage | Allows Google Analytics to measure visitor behaviour |
Ad storage | Allows Google to set advertising cookies on the visitor's device |
Ad user data | Allows sharing visitor activity data with Google Ads |
Ad personalization | Allows personalisation of Google ads shown to the visitor |
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 send back the choices of a returning visitor before letting Google tags execute.
Redact Ads Data
When ad_storage is Denied, this option masks additional advertising data (click information in URLs, third-party advertising cookies) sent to Google.
Pass through URL parameters
Passes advertising parameters present in the URL (e.g. gclid, fbclid) even when ad_storage is Denied. Allows Google to model unobserved conversions.
Additional Axeptio Settings
Key/value table to pass advanced Axeptio SDK parameters directly from GTM.
Column | Description |
Key | Name of the SDK parameter to define or override |
Value | Associated value |
For the full list of available parameters, see Advanced options â axeptioSettings.
