What changes with TCF2 for me as a publisher?

Help! What is it.

TCF2.0 is the name of the revised version of the "GDPR Transparency and Consent Framework (TCF)". Version 1.1 was launched in March 2018 by the industry association International Advertising Bureau (IAB) Europe. It is a standard in the technical infrastructure that passes user information for consent or refusal of data processing between publisher and advertiser as well as all other partners - always with the prerequisite of acting DSGVO compliant.

This is necessary because the user must not only be informed that their data is being collected and evaluated by the website owner, but must now actively consent. The user's response is carried from partner to partner based on the consent string. This ensures that all websites behave in accordance with the user's response (i.e. store data, analyze it or play out personalized content based on it).

So as a publisher, you want to design all embeds so that we can receive and pass the Constent String.

Is it relevant to you?

I'm not participating in TCF 2.0?

Easy - you don't have to do anything with AdUp. The ads will continue to play.

I participate in TCF 2.0?

Depending on your setup at AdUp you either don't have to do anything, the consent string will be passed automatically. In some cases you should become active. When exactly, you can read in the next paragraph.

What do you have to do to be DSGVO compliant and pass the user's consent string?

There are two options: Either we can determine the GDPR data automatically or you submit it to us manually.

• The prerequisite for an automatic transmission is that we are integrated on your page in a Javascript. Then the GDPR data will be read out automatically via the TCF-API. It is important that the Consent API is loaded first, except for img tags or URL calls.
• If no TCF-API is available or if we are embedded in an "unfriendly IFrame", we do not have access and need the GDPR data manually via the corresponding script.