Smart Data Protector - EN

With the Smart Data Protector, services can be blocked automatically if no consent is given. This means that snippets no longer have to be adapted manually, which saves effort, especially with large pages.

Advantages of the SDP:

No adjusting of individual services - this means
- less effort
- No video/no map/etc. can be missed
- Editors can continue to publish content as usual
way easier than other methods
In some cases, delivers useful replacement content such as a static image of the Google Maps map.

Disadvantages of the SDP:

Although the execution of JavaScript code is blocked, Smart Data Protector cannot prevent the download of the referenced JavaScript files. Since the IP address is sent in such a request, a third party company still receives the IP address of your visitors - and we consider this critical in terms of data protection!
References to third-party servers within CSS files with the @import statement cannot be blocked.
The feature is in some cases leads to compatibility problems with other parts of the site → Therefore, every functionality should be checked after installation!
The replacement content cannot be adapted
The SDP does not work with <noscript> - snippets
Not all services are supported (supported services)

Integration:

To use it, only the following snippets have to be integrated into the <head>:

<meta data-privacy-proxy-server="https://privacy-proxy-server.usercentrics.eu">
<script type="application/javascript" src="https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js"></script>

The <script> may only be loaded after the actual CMP, the <meta> tag can also be placed at the top near the other metatags.

Support for Custom Services

The Smart Data Protector recognises only the predefined service templates by default. Custom service templates can be supported by linking the template ID of the custom template to the corresponding predefined template. To do this, the custom service must be mapped with the "normal" database service:

<script>
uc.setServiceAlias({'BJz7qNsdj-7': 'XXXXX'}) 
// XXXXX needs to be the templateId of custom Youtube service template
// ... you can also map more service IDs similarly
</script>

Enable/disable for specific services

By default, the tool is automatically activated for all services. With the following scripts, the mechanism can be switched on or off service-specifically:

Disable services:

<script>
uc.deactivateBlocking([
  'BJz7qNsdj-7', // YouTube is not blocked
  'HkocEodjb7', // Google Analytics is not blocked
  // ... you can also add more service IDs similarly
]);
</script>

Or activate only certain services: