Why customize your banner?
Unless your site serves only a single homogeneous audience, a single banner configuration is not sufficient. Here are some common examples:
🌍 Multilingual site and translation management: a banner in French for the .fr site, in English for the .com, etc.
⚖️ Different regulations: GDPR for Europe, CCPA for the United States, LGPD for Brazil…
🧩 Different content or services: some versions use different third-party services (Google Ads, YouTube, etc.)
To do this properly, you should create multiple configurations of your banner: each version of your site must have its own Axeptio configuration.
What happens when your banner contains multiple configurations?
An Axeptio banner can contain multiple configurations, for example to manage different languages, different countries, or multiple versions of the same site.
However, simply creating multiple configurations does not trigger any automatic behavior.
Axeptio does not select a configuration for you. If no specific setup is put in place, no configuration will be loaded dynamically based on the visitor's browsing context.
This is precisely the purpose of this section Customize your banner for each version of your site: to present you with the different methods to explicitly indicate which configuration should be loaded depending on the version of the site being visited.
Independent configurations from each other
When a banner contains multiple configurations, they function in a completely independent manner.
This means that:
a modification made to one configuration does not impact the others
each configuration can contain different services
you can precisely tailor your banner to each version of your site
This independence offers great flexibility, particularly for multilingual or international sites.
On the other hand, this implies that:
the configurations are not synchronized with each other
any updates must be applied to each affected configuration
To save you time, Axeptio does however allow:
to duplicate an existing configuration, in order to create a new base without starting from scratch
to use automatic translation, to quickly adapt the banner content to another language
Here are the main possible methods, from simplest to most flexible:
If you integrate Axeptio via your CMS
Our CMS extensions/modules allow you to choose which Axeptio configuration to load based on the language of the site selected by the visitor.
They automatically detect the languages configured on your site, and allow you to associate an Axeptio configuration for each language through dropdown menus.
Example for our WordPress extension
By default, the "Dynamic (based on Axeptio)" option is selected for each language. In other words, no configuration is associated with your languages.
You should only leave the "Dynamic (based on Axeptio)" option selected if you wish to use another method among those listed below.
Load a fixed configuration in your integration
This is the simplest method: when integrating Axeptio — whether through a hardcoded script in your code or our GTM tag template — you can explicitly define the technical name of a configuration to load (via the cookiesVersion parameter).
Concretely, this means that:
on a specific version of the site, you integrate Axeptio with the configuration dedicated to this version
Axeptio always loads this particular configuration, without trying to detect anything on the page
This method is ideal for sites where each version is deployed independently (e.g.: fr.mysite.com and en.mysite.com each have their own integration).
Use URL-based rules in the Axeptio administration
If the language or version information is directly visible in the URL (e.g.: /fr/, /en/, or fr.mysite.com), you can create multiple configurations in the Axeptio administration and associate them with URL rules or regular expressions.
This way, Axeptio automatically loads the correct configuration based on the page visited.
This method is simple to manage if you are comfortable with URLs and prefer to manage everything in Axeptio!
Dynamically load the configuration with GTM or custom code
In some cases, the active language information is not directly in the URL. You must then find another way to access the language information, such as via the lang attribute of the <html> tag, or via a JavaScript variable.
In this case, you can use Google Tag Manager (or another Tag Manager) to:
dynamically read the active language on the page (for example by reading the
langattribute)define a "lookup table" type variable that associates each possible language with an Axeptio configuration
load the Axeptio banner with the appropriate configuration based on this variable
This requires a bit more technical knowledge, but offers great flexibility for managing multilingual sites with complex URL structures or dynamic language changes.
Use Axeptio's geolocation feature
When geolocation is enabled, the banner configuration is automatically chosen based on the visitor's country of origin (via their IP address).
This is particularly useful if your site must apply different regulations depending on location, and if language is not the only relevant criterion.