> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/general/iab-tcfv2.0/general-iab-tcfv2.0.md).

# IAB Transparency and Consent Framework (TCF)

How the TCF records user consent, and what it means for Ad Servers and Publishers.

The TCF is an industry framework run by IAB Europe. It gives Publishers and their advertising partners a common way to record the choices a user makes about their data, and to pass those choices on.

## What is the TCF?

The Interactive Advertising Bureau (IAB) runs the Transparency & Consent Framework (TCF) – a collaborative solution for businesses conducting targeted advertising in compliance with GDPR. The purpose of TCF is to standardize how businesses - publishers, ad tech vendors, and agencies – can continue running advertising in a way that is compliant with GDPR. Adhering to the TCF is crucial for Ad Servers, Publishers, and other Ad Tech Vendors looking to be fully compliant with GDPR and keeping up to date with evolving guidance and legislation. The framework provides guidelines for Consent Management Platforms (CMPs) to inform website visitors as to the purposes for which data is being collected, how it will be used, and how visitors can give or withhold their consent.

## What is a TC String? <a href="#what-is-a-tc-string" id="what-is-a-tc-string"></a>

Technically, TCF relies on the Transparency & Consent String (TC String). It contains all the user choices when it comes to accessing or storing information on their device and the use of their personal data as well as the publisher preferences when it comes to vendor use of data. In this way, it serves as a means of communication within the TCF.

The TC String can be communicated either via OpenRTB (e.g. in a bid request) or in the following URL parameters:

* gdpr: contains a flag (0,1) that informs if GDPR & ePrivacy applies.
* gdpr\_consent: contains the TC String (base64 string).

## What are the Legal Bases for Data Usage Under TCF? <a href="#what-are-the-legal-bases-for-data-usage-under-tcf" id="what-are-the-legal-bases-for-data-usage-under-tcf"></a>

There are 2 legal bases for which vendors can process data under TCF. These are:

* **Consent** - The data to be stored and processed requires consent from the data owner.
* **Legitimate Interest** - Legitimate interest is based on an overriding benefit of using personal data without obtaining consent, such as ensuring fraud prevention and providing flexibility for vendors to operate in different markets under different legal bases.

## What Purposes are Defined with TCF for the Processing of User Data? <a href="#what-purposes-are-defined-with-tcf-for-the-processing-of-user-data" id="what-purposes-are-defined-with-tcf-for-the-processing-of-user-data"></a>

Data can be gathered and processed by vendors for the following purposes as laid out in TCF, and in line with the following allowable lawful bases.

<table data-search="false"><thead><tr><th>TCF Purposes</th><th>Consent</th><th>Legitimate interest</th></tr></thead><tbody><tr><td>1. Store and/or access information on a device.</td><td>Yes</td><td>N/A</td></tr><tr><td>2. Use limited data to select advertising.</td><td>Yes</td><td>Yes</td></tr><tr><td>3. Create a personalized ad profile.</td><td>Yes</td><td>N/A</td></tr><tr><td>4. Select personalized ads.</td><td>Yes</td><td>N/A</td></tr><tr><td>5. Create a personalized content profile.</td><td>Yes</td><td>N/A</td></tr><tr><td>6. Select personalized content.</td><td>Yes</td><td>N/A</td></tr><tr><td>7. Measure ad performance.</td><td>Yes</td><td>Yes</td></tr><tr><td>8. Measure content performance.</td><td>Yes</td><td>Yes</td></tr><tr><td>9. Understand audiences through statistics or combinations of data from different sources.</td><td>Yes</td><td>Yes</td></tr><tr><td>10. Develop and improve services.</td><td>Yes</td><td>Yes</td></tr><tr><td>11. Use limited data to select content.</td><td>Yes</td><td>Yes</td></tr></tbody></table>

| TCF Special Purposes                            | Consent | Legitimate interest |
| ----------------------------------------------- | ------- | ------------------- |
| 1. Ensure security, prevent fraud, and debug.   | N/A     | Yes                 |
| 2. Deliver and present advertising and content. | N/A     | Yes                 |
| 3. Save and communicate privacy choices.        | N/A     | Yes                 |

To learn more about these purposes, see the [IAB Europe TCF policies](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies).

## What Does this Mean for Ad Servers? <a href="#what-does-this-mean-for-a-d-servers" id="what-does-this-mean-for-a-d-servers"></a>

If you are a TCF-approved vendor, when you serve ads using our Ad Server, you know that you are doing so within the remit of this framework. Where user information can be collected for the purpose of serving ads, analytics, or delivering personalized ads, you know that any Publisher integrated with an IAB TCF-approved CMP has captured the relevant consent from their end user to serve those ads via our Ad Server accordingly.

If you haven't already, you can register to become a TCF-approved Vendor on the [TCF Vendor registration portal](https://register.consensu.org/).

EXADS Ad Server clients can then provide their TCF Vendor ID to their EXADS representative for enablement. Once enabled, TCF-registered CMPs will be able to communicate the relevant consents required for their Publishers’ websites.

## What Does this Mean for Publishers? <a href="#what-does-this-mean-for-publishers" id="what-does-this-mean-for-publishers"></a>

Should a Publisher be integrated with an IAB TCF compliant CMP, and as long as your Ad Server has been enabled for the TCF framework, our platform will work out of the box and provide transparency on all the relevant consent needed from the end user to display ads.

To find out whether a third-party CMP provider is TCF compliant or not, you can look into the [IAB Europe CMP list](https://iabeurope.eu/cmp-list/).

## Benefits of TCF for Ad Servers and Publishers <a href="#benefits-of-tcf-for-a-d-servers--publishers" id="benefits-of-tcf-for-a-d-servers--publishers"></a>

* Ability to fully comply with GDPR laws.
* Transparency for Publishers and their end users regarding what cookies are used by their Ad Server for ad serving and analytics.
* Better collaboration with data protection bodies and vendors.
* Facilitates integration with TCF Approved Consent Management Platforms for Publishers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.exads.com/general/iab-tcfv2.0/general-iab-tcfv2.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.