English version below

The following steps are necessary to forward the user's consent to tracdelight:

1. integrate CMP on your site

To obtain consent, you need a CMP (Consent Management Provider). For legal reasons, we cannot give you a recommendation for a specific CMP. You need the CMP not only for tracdelight, but also for other partners, e.g. advertising.  

2. Configure tracdelight & Partner 

Our partners at tracdelight are as follows (information without guarantee): 

3. pass on technical consent to us

Widget  

Each widget has an additional parameter "data-td-consent". 

The consent string must be appended there. This will automatically add this information to all products that have been installed in this widget. 

Example: 

<div class="td-widget" data-td-args="{'widget':'cypxko7i8nhgelj3'}" data-td-consent="<consent-string>">

 

Direct integration (API or text links) 

Each tracelight tracking link requires an additional consent parameter. 

For text links or API integrations, the parameter with the consent string must be appended to the tracking links. 

Example: 

https://td.oo34.net/cl/?aaid=c60oezwbj9ga1hb7&ein=5e8nvyorjbfc3skt&paid=puh1gkkuzdohpdaq&consent= 

Integrations via link generator 

Here, the Consent parameter must not be set to the last position of the tracking link. The last position must always be the target URL. 

Example: 

http://td.oo34.net/cl/?tt=slg&aaid=c60oezwbj9ga1hb7&paid=puh1gkkuzdohpdaq&consent=&link=http://click.linksynergy.com/link?id=WQ9UE8k8OoE&offerid=579407.12381830500&type=15&murl=https://www2.hm.com/de_de/productpage.0618329017.html


Here is a demo of the structure of a consent string: https://iabtcf.com/#/encode



English version:

Pass the user-consent to tracdelight needs the following steps:

1. integration of a CMP on your own website

To obtain the consent, you need a CMP (Consent Management Provider). For legal reasons we cannot give you a recommendation for a specific CMP. You need the CMP not only for tracdelight, but also for other partners, e.g. advertising.

2. configuration of tracdelight & partner

Our partners at tracdelight are according to the current status (information without guarantee):

3. pass the user-consent to us technically

Widgets

There is an additional "data-td-consent" parameter for every integrated widget. It's up to the publisher to fill this parameter with the consent string. Thus, all products that have been installed in this widget are automatically provided with this information.

Thus, all products that have been installed in this widget are automatically provided with this information.

Example:

<div class="td-widget" data-td-args="{'widget':'cypxko7i8nhgelj3'}" data-td-consent="<consent-string>"> 

Direct integration (API or textlinks) 

Each tracelight trackinglink adds an additional consent parameter. 

For textlinks or API integrations the parameter with the consent string has to be attach to the trackinglinks. 

Example:

https://td.oo34.net/cl/?aaid=c60oezwbj9ga1hb7&ein=5e8nvyorjbfc3skt&paid=puh1gkkuzdohpdaq&consent= 

Integrations via linkgenerator 

The consent-parameter are not allowed to be at the last position of the trackinglinks. The last position must always be the target URL.

Example:

http://td.oo34.net/cl/?tt=slg&aaid=c60oezwbj9ga1hb7&paid=puh1gkkuzdohpdaq&consent=&link=http://click.linksynergy.com/link?id=WQ9UE8k8OoE&offerid=579407.12381830500&type=15&murl=https://www2.hm.com/de_de/productpage.0618329017.html


You can see a demo for the structure of a constent-string here: https://iabtcf.com/#/encode

en_GBEnglish