If you would like to use a specific version of the iubenda cookie solution, you simply need to insert the following link in lieu of the one normally used in the Cookie Solution: https://cdn.iubenda.com/cookie_solution/versions/0.11.36.4/iubenda_cs.js.
The “0.11.36.4” value must be substituted with the number of the version to be used. Available versions are found in the Current and Stable channels , starting with version 0.11.36.4 (consult the complete changelog for a listing of all released Cookie Solution versions).
Unlike the default link, the link mentioned above has a very extended cache configuration as it points to a specific version which does not require future modifications.
By applying the modification described above to the Cookie Solution, the iubenda_cs.js resource will load a new file containing the desired version. It’s a best practice, also adopted by Google for the loading of Google Analytics, as a way to achieve a compromise between the need to update the Cookie Solution and the loading/cacheing speed. The iubenda_cs.js file is in fact a file with a brief cache of few bytes, which in turn calls the real Cookie Solution, whose cache is much more extensive.
Alternatively, you can bypass iubenda_cs.js and directly load the file with the hash of the version and you will be able to:
If Google Lighthouse provided you with a suggestion similar to the following, we can help you solve the problem:
Look through the browser’s cache: If there is a maximum age for statistic resources in the HTTP headers or if an expiry date is set, the browser will load the the resources previously downloaded from the local disk instead of from the network.
To bypass iubenda _cs.js, the first thing to do is get the hash from the desired version:
At this point you can compile the new URL with the hash of the chosen version. To do so, simply substitute the link above with the one normally called in the Cookie Solution code. To create the URL, you can use the following structure:
parameter value "e"
Using the last version’s hash for example, the result is the following:
Please note: if you decide to block the iubenda Cookie Solution at a specific version, we suggest that you manually update it so that you may continue to benefit from our updates.
The inclusion of the activator inside the page can only be done in the safemode version of our Cookie Solution. For an introduction to safemode, please see the following.
It’s possible to include the part of the code relative to the scripts, directly in-page (inline); this code is known as the inline activator. Scripts can be activated through the inline activator even if the iubenda_cs.js primary resource is generically unavailable or in error.
The inline activator only guaranties script activation but can also take on a provided permission (see the following
onActivationDone, while others will be ignored.
Two additional configuration options are available for the inline activator:
safeTimeout: (milliseconds, default 5000)– the time required for the inline activator to be triggered (before activating the script the following option will also present itself
forceSafeActivation: (boolean, default false) – – If true, scripts are activated regardless of consent obtained. If false, the inline activator activates the scripts only if consent has been provided ( and registered in the preference cookie in the page of the host domain)
The inline activation is available at the following URL:
The content of this file is to be included in-page AFTER the initial configurations AND before the code that loads iubenda_cs.js..
The activator code is an integral part of the iubenda Cookie Solution and as such can be modified to include new features, upgrades and fixes. Releases of new versions of the iuenda Cookie Solution that also include the modification of the inline activator are marked in changelog with the
[safe.js updated]. To facilitate the management of the activator version in your page, the
_iub.csSafeActivatorVersion variable is available, which recalls the iubenda_cs.js version from which the activator was extracted.
(Optional) Suggested settings for performance optimization
startOnDomReady (boolean, default false) – Set to ‘true’. Please refer to the documentation here for more details. *This setting may need to be tested on a site by site basis as it may not work on all websites.