Loader.js
is the newest version of our CMPv2 Script, with improved performance, by adding code splitting and automatically deciding what version of bundle.js
should you use, based on your browser version.
What should you do to update to Loader.js
Since the loader.js
is an all-new script, it also brings some new changes to our API and to our current Script implementation. So you will need to follow these steps to update to the newest loader.js
...
:
Update your current Usercentrics CMP Scripts → The
loader.js
is a new script, so you will need to change yourbundle.js
orbundle_legacy.js
scripts
...
. Do not worry about legacy browsers.
loader.js
will automatically decide if it should usebundle.js
orbundle_legacy.js
based in your browser and in your browser version. These are the new scripts that you should change to:For Normal Users
Code Block language html <script id="usercentrics-cmp"
...
src="https://app.usercentrics.eu/browser-ui/latest/loader.js" data-
...
settings-id="XXXXXXX" async></script>
...
For TCF2.0 Users
Code Block language html <script id="usercentrics-cmp" data-settings-id="XXXXXXX" src="https://app.usercentrics.eu/browser-ui/latest/loader.js" data-
...
tcf-enabled></script>
Adapt your current code → As you've seen in your consoles inside your pages, there are some functions from our API that are deprecated, so you will need to adapt them to the new versions:
getServices should be changed by getServicesBaseInfo or getServicesFullInfo
Why should you update to this new script
...
Having this change to the code increases the performance of our CMP and therefore increases the lighthouse performance of your page.
Code that also needs to be adapted
As you've seen in your consoles inside your pages, there are some functions from our API that are deprecated, so you will need to adapt them to the new versions:
...
getServices should be changed by getServicesBaseInfo or getServicesFullInfo, and
...
.
About the current scripts
...