Usercentrics v2 - What are the differences?


A major update has been released at Usercentrics. Usercentrics itself even speaks of Usercentrics Version 2. The update must be requested, and there are many things to consider. 

Here are some differences and notes as bullet points:

  • Usercentrics Version 1 will run until the end of 2021, when it will be "forced"
  • There is only one event left: "consent_status"
  • Customized CSS is no longer supported in the backend. If necessary, this must be built into the page
  • Integrated blocking scripts do not need to be adapted
  • The update from version 1 to 2 must be requested via a Jira support ticket so that it is available in the UC backend (both versions seem to be able to be used after approval)
  • GTM: Change of the CMP event necessary, if necessary adjust exception trigger
  • Consent is keeped over from V1 to V2
  • Smart Data Protector continues to work with both versions
  • Design options are significantly expanded (fonts, branding colors, logo, etc.)
  • Categories can now also be shown in the first layer
  • Own icon for privacy button possible
  • Performance optimized UI
  • New features such as TCF 2.0, as well as cross device consent sharing for enterprise customers
  • Customization and self-programmable UI (Browser SDK) for enterprise customers
  • The CSS classes of the CMP banner have changed.
  • v2 offers an API (the JS API has changed.)
  • There is the possibility to build "own" custom banners (via API)

The following tasks should be clarified / completed before an update:

  • Apply for v2 activation in the Usercentrics Service Desk (Jira)
  • Which current design adjustments are available, which are not compatible (custom CSS)
  • How should the new design options be used to optimize the banner?
  • Adjust further adjustments and content to the V2, or check whether it still works (for example, the display of the privacy button only on the data protection page)
  • Check to what extent the new v2 codes have to be adapted (due to the A / B test that you are running, a custom version of the v1 code is used)
  • Check the new code version in a test environment (test server)
  • Adjust GTM for test and live



Mathias Bendl