Automatic Data Processing Service blocking – Usercentrics Support - EN

About the Auto Blocking feature

The Auto Blocking feature prevents data processing services from loading prior consent without the need for manually marking up resources (scripts, images, iframes, etc.) on a website.

This makes it more convenient to ensure services only load when consent is given and allows you to control services that you're unable to manually mark up.

If you have the Auto Population feature enabled, this will essentially fully automate the process of ensuring that Data Processing Services only load if consent has been given.

How the Auto Blocking feature works

The scanner crawls through the website and identifies all third-party services loaded on the website.
The results of the scan are used to generate a configuration file which will serve as instructions for the Auto Blocking feature which technologies to block and how to identify the resources that load them.

The configuration file is updated after every scan and the most up-to-date information is applied when Auto Blocking is enabled on the website.

Implementation

Auto Blocking is available for paid subscribers and can be implemented by adding a script, which can be copied from the Usercentrics Admin and subsequently added to the website template along with the main Usercentrics CMP script.

With Auto Blocking selected, the following scripts (Auto Blocking and CMP) will be available to be copied and pasted:

<script src="https://web.cmp.usercentrics.eu/modules/autoblocker.js"></script>
<script
  id="usercentrics-cmp"
  src="https://web.cmp.usercentrics.eu/ui/loader.js"
  data-settings-id="XXXXXXX"
  async
></script>

If you’ve used an older version of the Auto Blocking script, please make sure that you trigger a new scan to ensure that the Auto Blocker configuration is up-to-date.

Manual mapping - Manual blocking

The Auto Blocking feature may not block all technologies present on your website. This is due to the scanner not being able to connect our current Data Processing Services for all detected third-party requests.
These services will subsequently be listed as “unknown”.

Steps to block unknown third party requests:

Manually adding services

Log into the Admin Interface and select the DPS scanner tab in the Service Settings section
Look for “unknown” in the Service column
1. Check whether the unknown request is already represented as a previously mapped DPS.
  If this is the case, the service should get blocked by the Auto Blocking feature. If it isn't, continue to next step.
Add the service using the Add Service link to the right of the unknown service.
You will have the options Assign Custom DPS and Create Custom DPS.
Select Create Custom DPS and provide the following information:
1. Service name
2. Service Description ^(optional)
3. Category (Marketing, Functional, or Essential)
You can also choose to ignore the service using the Ignore link in cases where the service was already added to the configuration, or if you don't want it to be listed on the consent banner and/or potentially blocked by the auto blocking feature.
Identify the corresponding script on your website.
Change the JavaScript type to "text/plain" and add the data-usercentrics attribute with the name of the data processing service.
This must be an exact match to the value you entered in step 3.

or:

Request the addition of a service to our DPS repository

Contact Usercentrics support with a mapping request for the unknown service.
Please be sure to provide the request URL (listed under the Domain column), and if possible the name and a purpose description.
Usercentrics will map the unknown service to a DPS.
Please keep in mind that these requests may take a while to process.
Once confirmed, you can trigger a new scan manually for your configuration. The mapping will take effect as soon as the scan is finished, enabling autoblocking for the now mapped service.