This website makes use of Google Analytics cookies.
For more information on how to block such cookies, please read our cookie policy.
By using this website, you agree to the use of cookies as explained in the cookie policy.

TCF

TCF for Advertisers & Agencies

Advertisers like publishers are website operators that have a direct relationship with end users. This relationship can be via website, app or other content. Where digital advertisements are displayed or user information is collected and used for digital advertising, measurement and analytics, or content personalisation then the operator is required to capture user consent preferences and make sure that the consent signal is shared across the ecosystem of vendors that the website operator is working with.

Advertisers must read and follow TCF Policy, specifically Policy that relates to the user interface that ensures a consistent presentation of the purpose and legal basis for which the vendors they wish to work with may process personal data based on a user’s visit to the publisher’s website, app or other content.

Website operators need to select a CMP that provides a consent solution that meets their specific needs. Alternatively, website operators can choose to become a CMP and build their own consent solution

The development of a consent solution is not a simple task and requires developers with advanced skills in JavaScript, reading/writing of cookies, network configuration and the differences between browsers, especially around security setting defaults and responsive UX rendering. CMPs must also respond quickly to changes in IAB Europe TCF specifications and Policies. They must also pass the annual CMP validation test that ensures compliance with TCF specifications and Policies.

Resources

TCF Resources
· Explanatory Deck
· Explanatory Video

· Training Video

TCF v1.1
· List of registered TCF v1.1 Vendors
· List of registered TCF v1.1 CMPs 
· TCF v1.1 FAQs
· TCF v1.1 purpose translations

TCF v2.0

TCF v2.0 Information webinar for Agencies & Advertisers 

TCF v2.0 purposes translations:
(Available after September 3rd)
List of registered TCF v2.0 Vendors
(Available after Registration occurs)
List of registered TCF v2.0 CMPs
(Available after Registration occurs)
TCF v2.0 FAQs

 

Technical specifications

TCF v1.1
Consent Management Platform API
Transparency and Consent String with Global Vendor List format
Mobile InApp
TCF Implementation Guidelines:
Policy
Terms & Conditions

TCF v2.0

Consent Management Platform API 
Transparency and Consent String with Global Vendor List format
TCF Implementation Guidelines

Policy
Terms & Conditions 

 

Lines (1)