The IAB Transparency and Consent Framework is the advertising industry’s standard for capturing a person’s consent choices and carrying them, as an encoded string, through the programmatic supply chain. It exists because the GDPR and the ePrivacy Directive made consent a legal precondition for the tracking that funds digital advertising.
IAB Transparency and Consent Framework
The TCF encodes what a person agreed to — which purposes, which vendors — into a compact string that travels with the bid request, so every party downstream can read it. Whatever one thinks of the cookie banner it produced, the artifact itself is notable: it is machine-readable consent, standardised across thousands of counterparties, at global scale.
- A consent string - Purposes, legitimate interests and vendor permissions encoded compactly enough to travel in a bid request.
- A global vendor list - A registry of participating vendors, so a permission can name who it applies to.
- CMP conformance - Consent management platforms are validated against the specification rather than self-declaring.
- Carried in-band - The string moves with OpenRTB rather than being fetched separately.
The TCF is the sharpest fact in The State of Marketing & Advertising APIs. That market describes consent in its own customer-facing APIs at 3.1% — below the whole-catalog rate — while simultaneously operating the most sophisticated machine-readable consent artifact any market has built. The capability is real and it is pointed at the ad auction rather than at the interface a customer integrates. Aiming the same idea at the API is the largest unclaimed position in that market.
Industry: Advertising
