# IAB TCF

<details>

<summary>Who is part of the TCF?</summary>

* Compatible CMPs are officially referenced after full audit and validation for each version.&#x20;
* Advertising industry players aka 'vendors': adserver, dmp, advertising measurement tool.&#x20;
* Some advertising players are not in the TCF, so Google has developed the Google Consent mode for these players.&#x20;
* The major advertising players use TCF as the single standard for the data/consent chain.
* In its first version TCF allowed the reading of consents from one site to another (global consent) this function is not allowed by Google in V2.

</details>

<details>

<summary>Who is the TCF for?</summary>

* TCF is potentially applicable to all digital devices: website, mobile app, etc.&#x20;
* It is preferred for sites and apps with a large audience monetization: media, advertisers with advertising.&#x20;
* Its adoption is not massive because there is a strong impact on the user experience.&#x20;
* The trade-off between business, project and brand/customer relationship issues must be taken into account.

</details>

<details>

<summary>What are the impacts?</summary>

* The trade-off between business, project and brand/customer relationship issues must be taken into account.&#x20;
* TCF will be a CMP project to manage and implement.&#x20;
* Can I test on a TCF template? YES, YOU CAN.

</details>

<details>

<summary>Will TCF have a negative impact on my consent rate?</summary>

NO.

Why: because the first screen that collects 99% of the consent will be little changed except its text. The default one from the IAB or a modified text validated by IAB. The impact will therefore be minimal

</details>

<details>

<summary>By passing the TCF I would have to resubmit consent to my entire audience?</summary>

YES.

Why: to have the totality of my audience with an exploitable consent in the framework.

</details>

<details>

<summary>What are the advantages of taking the TCF ?</summary>

* The main interest lies in the collaboration opportunities with TCF Vendors.&#x20;
* These opportunities are accessed on audience monetization and advertising mainly.&#x20;
* Be able to quickly test and activate new TCF Vendor devices based on the chosen configuration.&#x20;
* Supporting the only advertising industry standard in the context of consent and GDPR

</details>

<details>

<summary>Disadvantages of taking the TCF ?</summary>

* You must adhere to all the specifications.&#x20;
* The UX of the preference center is broad and complex. <mark style="color:red;">The IAB purposes are mandatory and cannot be merged with your own purposes.</mark>&#x20;
* It is necessary to follow the evolutions of the TCF according to the current events and following a timing imposed by the IAB.&#x20;
* In case of a new collaboration with a vendor, it will be necessary to wait for the consent to resubmit or to resubmit to the whole hearing.

</details>

<details>

<summary>Migration to the TCF?</summary>

* This is a CMP project with purpose and design choices on the preference center.&#x20;
* The consent will have to be resubmitted to the entire audience to be available in the framework.&#x20;
* Make choices upstream, particularly on vendors, and measure the potential impact.&#x20;
* Stay alert and responsive to our recommendations and to changes in the framework.

</details>

<details>

<summary>Do you have any examples of clients using TCF?</summary>

*

 <figure><img src="https://1613709692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0zW0zvGDZaiNuIFweCtu%2Fuploads%2FrxnYkGke8cID2FJwV39n%2FIABTCFREF.jpg?alt=media&#x26;token=1c9779d0-b799-499c-bf06-24b2facdcab2" alt=""><figcaption></figcaption></figure>

</details>