Back to overview
Access

What changes with TCF2 for me as an advertiser?

Since August 2020, the updated TCF version 2.0 is in effect. We at AdUp have participated in the changeover. What this means for you, you can read here.

Help! What's that?

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 his data is collected and evaluated by the website owner, but must now actively agree. The user's response is carried from partner to partner using the consent string. This ensures that all websites behave in accordance with the user's response (i.e. store data, analyse it or play out personalised content based on it).

So as an advertiser, you want to get the consent string from us and read it.

Is it relevant to you?

I am not participating in TCF 2.0?

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

I participate in TCF 2.0?

It will be relevant for you if you use one of our pixels to measure conversion and engagement or the retargeting API. What you should adjust, you can read in the next paragraph.

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

There are two options: Either we can automatically determine the GDPR data 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.

Conversion Pixel

If you participate in TCF 2, you have to adjustyour conversion pixel , i.e. you have to add additional parameters (gdpr and gdpr_consent). You can find more about this here.

Parameter Description Example
gdpr
gdpr_consent

gdpr

1 = GDPR gilt

0 = GDPR gilt nicht

(weglassen) = Unbekannt (Standard)

gdpr_consent

Der IAB Consent String (base64url-encoded)

gdpr=1&gdpr_consent=[CONSENT_STRING]

Engagement Pixel

If you are participating in TCF 2 and haveincluded a CMP layer, you donot need toadjust your engagement pixel.

If you participate in TCF 2 and have included us in an iframe, you need to extend your engagement pixel. You can find more information here.

Parameter Description Example
gdpr
gdpr_consent

gdpr

1 = GDPR gilt

0 = GDPR gilt nicht

(weglassen) = Unbekannt (Standard)

gdpr_consent

Der IAB Consent String (base64url-encoded)

gdpr=1&gdpr_consent=[CONSENT_STRING]

Retargeting-API

If you are participating in TCF 2 and haveintegrated a CMP layer, you donot need toadjust the integration of the retargeting API.

If you participate in TCF 2 and have included us in an iframe, you need toextend the inclusion of the retargeting API. You can find more information here.

Methode Description Example
setGdpr

gdpr

true = GDPR gilt

false = GDPR gilt nicht

null = Unbekannt (Standard)

gdpr_consent

Der IAB Consent String (base64url-encoded)

api.setGdpr({
    gdpr: true,
    gdpr_consent: "CONSENT-STRING"
})

Related topics