TCF 2.0

This page provides a summary of what the Transparency and Consent Framework (TCF) 2.0 is, outlines how IX (Index Exchange) is supporting it, and explains what changes we're making to our outgoing bid requests as a result of TCF 2.0.

What is TCF 2.0?

The IAB's Transparency and Consent Framework (TCF) 2.0 is effective as of April 1st, 2020. The TCF allows businesses to operate in a compliant way under the GDPR by providing a standard format to collect and communicate user consent signals to process their personal information. Feedback from EEA regulators on the initial version led the IAB to develop a more detailed set of specific signals.

How Does IX Support TCF 2.0?

IX is prepared to handle the TCF's new consent signals. We plan to support TCF 1.1 and 2.0 throughout the IAB's transition period, ending on June 30, 2020.


Work with your Consent Management Provider (CMP) in order to upgrade your integrations to TCF Version 2.0.

IX Library Partners

The IX Library will automatically communicate with your CMP to get and share the consent string with all certified adapters in your Library.


The consent string for TCF 1.1 and 2.0 will pass in the user.ext.consent field (user ext object) of a bid request. IX passes the consent string just as we receive it, so you should be ready to accept TCF 2.0 consent strings by the transition timeline set by the IAB.


Publishers can only send one version of the consent string. DSPs should be ready to receive the new version signals on April 1st.

How Does IX React in No-consent Cases?

When IX determines that an ad request is for a user who has not provided consent, we anonymize certain user information in the bid request sent to our DSPs in the following ways:

  • ip (device object): The last octet of the user’s IP address is replaced with a zero.

  • lat and lon (geo object): Latitude and longitude coordinates are reduced to two decimals which translates to accuracy no less than one third of a mile.

  • All unique IDs from the bid request in the device and user objects that indirectly identify a user are removed.

  • deals (pmp object): Audience segment targeted deal IDs are no longer added to the bid request.


Was this page helpful?

You are invited to take a 1-minute survey to help us improve this site.