Implementation of the Interactive Advertising Bureau (IAB) Transparency and Consent Framework (TCF) v2.0
Transparency and Consent Framework (TCF) v2.0 launch in INVIDI Pulse
TCF v2.0 was released 21 August 2019 with industry adoption commencing first half of 2020. It introduces significant changes and is not backward-compatible with the earlier version. TCF v1.1 is deprecated and superseded by TCF v2.0.
IAB Europe will continue to support TCF v1.1 until 30 June 2020 and post that date support will be removed, which means support in Pulse ends at the same time.
- Vendor List Version: 34 or higher
- Vendor ID: 438
- Purposes for which personal data will be processed and the legal bases to
justify the processing:
- ID = 1, Store and/or access information on a device
- ID = 2, Select basic ads
- ID = 3, Create a personalised ads profile
- ID = 4, Select personalised ads
- ID = 7, Measure ad performance
- ID = 9, Apply market research to generate audience insights
- ID = 10, Develop and improve products
For purpose 1, consent is the sole legal basis. For purposes 2,3,4,7,9, and 10, the legal basis is consent (default) or legitimate interest, meaning they are flexible purposes.
- Features INVIDI relies on in support of one or more purposes:
- ID = 1, Match and combine offline data sources
- ID = 2, Link different devices
For more information on the purposes and features in TCF v2.0, see Appendix A: Purposes and Features Definitions. For more information on the IAB Transparency and Consent Framework v2.0, see Transparency and Consent Framework v2.0 and the associated links.
You need to make sure your Consent Management Platform (CMP) is IAB TCF v2.0 compatible. For more information, see TCF for Publishers.
This release includes the following documentation updates: