IAB TCF 2.2
Overview
What Is The Transparency & Consent Framework?
The TCF’s simple objective is to help all parties in the digital advertising chain ensure that they comply with the EU’s GDPR and ePrivacy Directive when processing personal data or accessing and/or storing information on a user’s device, such as cookies, advertising identifiers, device identifiers and other tracking technologies.
TCF v2.2
TCF v2.2 enables consumers to grant or withhold consent and also exercise their ‘right to object’ to data being processed. Consumers also gain more control over whether and how vendors may use certain features of data processing, for example, the use of precise geolocation.
Publishers employing TCF v2.2 gain greater control and flexibility with respect to how they integrate and collaborate with their technology partners. New publisher functionality allows them to restrict the purposes for which personal data is processed by vendors on a publisher’s website on a per-vendor basis.
OneTrust Configuration guidelines
OneTrust helps you to configure the IAB TCF version for your application by building the IAB template in OneTrust’s environment.
Accessing TC Data
The CMP API service returns IAB related consents under storageKeys
.
IAB TCF Keys
UserDefaults Key |
---|
IABTCF_CmpSdkID |
IABTCF_CmpSdkVersion |
IABTCF_gdprApplies |
IABTCF_PolicyVersion |
IABTCF_PurposeOneTreatment |
IABTCF_UseNonStandardStacks |
IABTCF_SpecialFeaturesOptIns |
IABTCF_PublisherCC |
IABTCF_PublisherConsent |
IABTCF_PublisherLegitimateInterests |
IABTCF_PublisherCustomPurposesConsents |
IABTCF_PublisherCustomPurposesLegitimateInterests |
IABTCF_PurposeConsents |
IABTCF_PurposeLegitimateInterests |
IABTCF_TCString |
IABTCF_VendorConsents |
IABTCF_VendorLegitimateInterests |
IABTCF_PublisherRestrictions |
Updated 3 months ago