TCF 2.0 information
The TCF 2.0 comes into force on 15th August 2020. We have summarised for you the most frequently asked questions about TCF itself and the implementation via the Usercentrics CMP.
- What is the TCF?
- What is the IAB?
- For whom is TCF 2.0 intended?
- Why do I need the TCF 2.0?
- What is the difference between TCF 1.0 and TCF 2.0?
- When should I start the transition?
- What will happen if I don’t transition in time?
- How must I implement the Usercentrics CMP so that I can use TCF 2.0?
- What creative possibilities do I have with the individual CMP elements once TCF 2.0 is activated?
- Can I display a Privacy Wall instead of the banner?
- Which vendors use TCF 2.0?
- Will Google require TCF 2.0 as a standard?
- Can I continue to work with non-IAB vendors?
- Can I incorporate non-IAB vendors into the CMP?
- Can I simply incorporate the entire Global Vendor List for TCF 2.0?
- Does the TCF demand that user consent be obtained every time the Global Vendor List is changed?
- Can I amend the text of the Data Processing Services (DPS)?
- What are so-called “Stacks” with TCF 2.0?
- Does the TCF require a “Reject” button in the first layer of the banner?
- Do I have to offer the user granular selection options in the first banner layer with TCF?
- As a publisher can I define the legal basis or purposes for individual vendors?
- What is the difference between Global Scope and Service Specific Scope?
- As a publisher can I define the legal basis for my own (data processing) purposes?
- Does TCF forbid “continuing to scroll” as consent?
- Where can I find further information about TCF 2.0?
- Guidelines of the Transparency and Consent Framework v2.0
Do you need further help?
https://usercentrics.atlassian.net/wiki/spaces/SKB/pages/234913848