Blog

Your TCF v2.0 transition: a practical checklist for publishers

Sourcepoint
July 15, 2020

The August 15 deadline to switch over is rapidly approaching. The Transparency & Consent Framework v2.0 is complex, but with the proper preparation and the right partner, you can ensure no impact on your revenue. For a good overview of the process, view our webinar “The TCF v2.0 switchover: What do publishers need to know?” or check out our blog post.

1. DO YOUR VENDORS SUPPORT V2.0?

This question is an important starting place. Have a discussion with your key vendors about when they’re planning to join, and coordinate your launch date around when they’re able to support v2.0.

If you’re working with a vendor who doesn’t use the framework, decide how you want to integrate them — can they be triggered by a tag manager?


2. DO YOU WANT TO USE A PRIVACY MANAGER IN THE FIRST-LAYER MESSAGE?

Making a Privacy Manager the first message that consumers see provides more transparency and the ability to take quick action. It also allows publishers to easily present region-specific privacy laws. On the other hand, there is less opportunity for education: consumers might decline to consent without fully understanding the value exchange. The pros and cons will depend on the relationship with your audience.

3. DO YOU KNOW HOW PURPOSE 1 IMPACTS YOU?

Purpose 1, “Store and/or access information on a device”, must appear as a consent-based item, never under legitimate interest. It’s an unusual purpose in the TCF in that it’s not a purpose for personal data processing in itself, because any personal data stored and/or accessed via Purpose 1 would require another purpose to be processed. It’s designed to support not just GDPR, but also the ePrivacy directive.

If you’re using it, you should make sure the legal teams in the countries where you operate have a plan for how to comply, since the Data Protection Authorities in some jurisdictions do not require disclosure; in others, it must be disclosed. The Sourcepoint CMP will allow you to configure the Privacy Manager either way, depending on geolocation. But whatever you do, make sure your legal team has reviewed your approach.

4. WHich stacks do you want to use in the first-layer message?

Because stacks are designed to simplify communication with the consumer and thereby reduce redundancy, you can’t include a purpose in more than one stack, or present a purpose both inside a stack and outside of one.


5. HOW WILL YOU PRESENT NON-TCF VENDORS AND PURPOSES?

If your UI includes non-TCF vendors or purposes, they must be visually separated — with an icon or some other special treatment.

6. HOW ARE YOU GOING TO HANDLE LANGUAGE SUPPORT?

Which languages will you support? How will you present a language to the user? Will you present the default or will you rely on the user’s browser to determine which language to support? The Sourcepoint CMP provides the standard IAB translations for all IAB definitions.

7. HOW EASY WILL IT BE TO IMPLEMENT V2.0?

How many properties do you have? How many vendors? How many custom purposes? When selecting a CMP partner, choose one who can help you navigate your level of complexity and create scalable processes.

Latest Blog Posts

FTC rulemaking and CPRA comment periods close

November 28, 2022

Comments from the News/Media Alliance requested that any FTC...

Google settles in multi-state location tracking suit

November 21, 2022

Google settled a multistate privacy lawsuit with 40 state Attorneys General based...

Colorado Posts Public Comments to CPA Draft Rules

November 14, 2022

The Data Protection and Digital Information Bill, which was...

Latest White Papers

Benchmark Report: US Privacy Compliance

August 19, 2022

The current state of publisher compliance with CCPA, and...

Ebook: A Publisher’s Guide to Vendor List Curation

December 16, 2021

How to review your vendor list to mitigate compliance...

Keep in touch

Sign up for our newsletter to keep up with privacy news for adtech and martech,
plus occasional company news.

Let's explore what we can do together.

We'll be in touch within 48 hours

[contact-form-7 id="593" title="Schedule a Demo"]