Supporting privacy regulations in the IX Library

Note: The IX Library™ is compliant with IAB frameworks TCF v1.1 and v2.0.

Under the California Consumer Privacy Act (CCPA), users can opt out of having their personal data collected or processed. Under the EU Transparency and Consent Framework (TCF) v1.1 and v2.0 users must provide consent before their personal data can be collected or processed. Publishers can use a Consent Management Platform (CMP) (or a proprietary solution) to collect and store site visitor’s consent. The IX Library supports the automatic retrieval of this consent information from the site.

To easily integrate the IX Library with a CMP, we recommend selecting a CMP (or a proprietary solution) that's compliant with the following IAB Frameworks: CCPA Compliance Framework for Publishers & Technology Companies, and the Transparency & Consent Framework (TCF) v1.1 as well as v2.0.

To enable support for privacy regulations in your IX Library, see Enable privacy regulation support in the IX Library.

How it works

When privacy settings are enabled in the IX Library, the IX Library attempts to connect with a CMP as soon as it loads on the publisher’s page. Once connected, the IX Library waits to receive one of two signals:

  • An encoded string, representing the site visitor's consent from the CMP
  • The privacy settings timeout, set in the IX app

When it receives one of these signals, the IX Library makes the consent information available to certified adapters and the header auction begins.

If the IX Library fails to connect with the CMP or the privacy settings timeout elapses, it continues with the header auction. However, instead of making the consent information available, it shares empty consent strings with the adapters to indicate unknown consent.

For more information, see: