What is the IAB TCF?
The IAB TCF stands for Transparency and Consent Framework and is a specification of the IAB which enables AdTech providers to find out whether a website visitor has given his consent to the data processing or not. More information can be found on the IAB Europe website.
IAB TCF v1 invalid as of April 2020
AdSpirit supports IAB TCF v1 and IAB CMP API v1.1. See also the article on Consent String. Support for the IAB TCF v1 will be discontinued from April 2020. Signals in v1 that subsequently arrive in the AdServer are ignored.
IAB TCF v2 valid from March 2020
AdSpirit will support the IAB TCF v2 from March 2020, i.e. TCF signals ("TC-String") sent to the AdServer will be processed accordingly by the AdServer. Furthermore, the existing automatisms (pre-targeting, asynchronous advertising space codes) for recording the signals are updated accordingly so that the new signals can also be recorded.
Important: Change of data protection settings in the AdServer
From April 2020, the minimum data protection settings of the ad server will also be adjusted. If it is currently still possible to set the ad server so that cookies and data processing can take place without the user's consent, this will no longer be possible from April 2020.
In order for cookies to be set by the AdServer from April 2020 and for the processing of personal data to take place, the IAB TCF v2 signal ("TC string") must be available from April 2020.
What does this mean?
In order to continue to be able to call up the full performance of the ad server, it is necessary that a CMP ("Consent Management Provider") is available on every website on which advertising is to be delivered. This CMP follows the IAB TCF v2 standard. We recommend www.consentmanager.de . Further CMP providers can be found in the list of CMPs on the IAB website. If the CMP is included, the information must be transferred to AdSpirit.
Note: This only applies to access from EEA countries (EU + Norway, Iceland, Liechtenstein).
Transferring TCF signals to placements
Advertising spaces can automatically detect the TCF signals. Please read the help article on Consent Strings.
Transferring TCF signals to pixels, tracking switches, piggybacks, etc.
For all other codes (action pixels, retargeting pixels, tracking switches, piggybacks, ...) the TCF signals have to be transferred manually from the website. Please read the help article about Consent Strings.
Transferring TCF Signals via OpenRTB
AdSpirit supports the IAB specifications with regard to signal transmission via OpenRTB. In this case you do not have to do anything.