You have just published an update to your Axeptio banner, but the wrong configuration, version, or language is displaying on your site?
No worries! Several causes could explain this behavior. This article helps you identify them.
My banner displays an old configuration
You have modified and published your banner, but the changes are not displaying. In most situations, the issue is related to browser cache or cookies.
What to check
Clear the cache and cookies in your browser
Reload the page in private browsing mode
Test from a different browser or device
👉 Why?
Your browser may cache an older version of the banner and continue displaying it, even if a new configuration has been published on the Axeptio side.
My banner does not display the same steps as those I see in the Axeptio admin preview
If you integrated Axeptio via a CMS integration (Shopify, WordPress, etc.), the integration may automatically add an additional step to manage services specific to the platform:
Shopify cookies in the case of a Shopify integration: the purposes listed on this step are not editable and this screen cannot be removed for regulatory reasons
cookies generated by your other plugins in the case of a WordPress integration
... and so on!
My banner displays in the wrong language
If your site is multilingual and the banner is not displaying in the expected language, it is likely that language management is not configured correctly.
What to check
Have you properly configured language management in accordance with our documentation?
Does the language detected by Axeptio match the language of the page displayed?
Is a language not being forced in your integration (CMS, JavaScript, Google Tag Manager, etc.)?
👉 Axeptio relies on your configuration to determine which language version to load. Incorrect configuration can result in loading a different language.
My banner displays different configurations unpredictably
It is possible that Axeptio is integrated multiple times on your site, sometimes with different configurations.
What to check
Open your browser console
Check if an error of the following type is displayed:
"Axeptio SDK is already loaded"
If that is the case:
Make sure to keep only one integration method
direct integration in the code
via Google Tag Manager
or via your CMS
👉 Loading Axeptio multiple times can cause unexpected behavior and prevent the correct configuration from being applied.
Otherwise, it is also possible that certain configuration options influence the version of the banner loaded on your site.
Step 1: check the cookiesVersion parameter
Make sure you are not forcing the loading of a specific configuration via the cookiesVersion parameter:
directly in the Axeptio script
in a Google Tag Manager tag
or in your CMS integration
If this parameter is set, Axeptio will only load this version, even if another configuration is published.
Step 2: check other targeting rules
Then verify if you have configured:
URL-based rules
geolocation rules
👉 These rules can result in loading a different configuration depending on the page visited or the user's country.