Deprecating Duplicated Data Processing Services

Overview

What is happening

As our template database is continuously being updated, we created new templates for service providers that have changed their names or split up their products. We will now remove some duplicated Data Processing Service templates to ensure more clarity. These duplicates will no longer show in the Admin Interface, meaning they can’t be selected anymore from our database. Your current implementation will not be affected, however legal updates on our templates will from now on only be done for the new templates.

What is the timeline

There is no specific timeline by which you must have exchanged the templates. However, we recommend to exchange the templates as soon as possible so that you can continue using our maintained texts and templates.

Which Data Processing Service Templates need to be replaced?

In each case the new Data Processing Service template can be found in the information field in the Admin Interface. Find the full list of deprecated Data Processing Services and their replacements under the following link.

Open

Adjustment Step 1: Add new template in Admin Interface

If one of your Data Processing Service templates got marked as deprecated in the Admin Interface, it should be replaced by the new template.

Now go to your Admin Interface under Service Settings / Data Processing Services and add the new template from our database by clicking on “Add Data Processing Service via Database”. If you are currently using the CMP version 1, this step needs to be done directly under Service Settings.

Open

Adjustment Step 2: Adjust Implementations

2.1 Direct Implementation

If you have the respective service you want to change implemented directly in the code of your website according to our guide, make sure to adjust the data attribute (if necessary). For example if the template name changed from “Taboola Europe” to “Taboola”, make sure to change the data attribute in your Taboola script from

to

2.2 Tag Management Systems e.g. Google Tag Manager

If you have the respective service you want to change implemented via a Tag Management System like Google Tag Manager, Tealium, Adobe Launch, Oxid Plugin or other 3rd Party Plugins, you need to adjust your setup based on the new template name.

Example Google Tag Manager
In the Google Tag Manager you need to adjust the data layer variable and trigger to the new template. For example if the template name changed from “Taboola Europe” to “Taboola”, create a new data layer variable in line with our GTM implementation guides (CMP v2 | CMP v1).

In the next step add the new data layer variable to you existing trigger and replace the old variable.

2.3 Smart Data Protector

If you are using the default Smart Data Protector (blocking every supported technology), we will from now on support both versions - the deprecated version of the template and the new one. Therefore when adding the new template and deleting the old template in the Admin Interface, there is no further to do from your side. A few examples of Data Processing Services that are currently affected are listed below. See the full list of supported technologies in our technical documentation.

• yumpu.com (9BBsmV62) → yumpu (6LdBYXdAl)

• Google Web Fonts (HkYNq4sdjbm) → Google Fonts (HkPBYFofN)

• Amazon Adsystems (gvWsZJmVT) → Amazon advertising (N2spyFPL)

However, if you are using the Smart Data Protector with additional scripts from the technical documentation, please make sure to adjust the respective Template-IDs. This needs to be done if you only block specific services using uc.blockOnly(); or exclude services using uc.deactivateBlocking();

Furthermore, you need to adjust the Template-ID if you use Custom Data Processing Services for one of the affected templates with uc.setServiceAlias() or force a reload when a user interacts with the Smart Data Protector overlay using uc.reloadOnOptIn('BJz7qNsdj-7'); or uc.reloadOnOptOut('BJz7qNsdj-7');.

2.4 API

If you used the name or Template-ID of one of the deprecated services within a function / method / event listener from our API (CMP v2 | CMP v1), make sure to exchange it with the new name or Template-ID - depending on what you are using / what is required. For example if you used the acceptService method for our CMP v2, exchange the method from

to

2.5 Embeddings

If you are using the Privacy Policy Embeddings (CMP v2 | CMP c1) and more specifically only some Data Processing Services, make sure to adjust the name in the code. For example if you were showing the information for Taboola Europe in your privacy policy for the CMP v2, exchange the code from

to

2.6 DPS Scanner

If one of the duplicated Data Processing Services has already been added to your settings, the other one will not appear in your DPS Scanner results. This means for example if Taboola Europe has been added to your settings, the DPS Scanner will not show Taboola as a newly detected service.

Adjustment Step 3: Delete old template in Admin Interface

Once you added the new template as described in Step 1 and did all the adjustments under Step 2, the old and deprecated template can be removed from your Admin Interface by clicking on it → Select Delete at the right.

Do you need further help?

How can I get help with technical questions?