The digital advertising ecosystem is moving toward its next technical milestone. By 28 February, all publishers, their vendors and and consent management platforms (CMPs) must transition to the IAB Transparency and Consent Framework (TCF) version 2.3.<\/p>\n\n\n\n
This is not a total overhaul of how consent is gathered. Instead, it is a technical refinement designed to improve the reliability of the signals sent to your demand partners. For publishers, understanding this update is essential to maintaining stable monetisation and ensuring that ad requests are not downgraded by major partners like Google or The Trade Desk<\/a>.<\/p>\n\n\n\n The primary update in version 2.3 is the transition of the Disclosed Vendors<\/em> segment from an optional field to a mandatory one within the Transparency and Consent (TC) string.<\/p>\n\n\n\n Historically, there has been an element of ambiguity regarding whether a specific vendor was actually shown to a user in a CMP interface. This was particularly relevant for vendors relying on Legitimate Interest. TCF 2.3 removes this uncertainty by requiring a clear binary signal: a ‘1’ indicates a vendor was disclosed to the user, and a ‘0’ indicates they were not.<\/p>\n\n\n\n For the technical team, this means the TC string structure will now strictly follow a pattern that includes the Core segment, the mandatory Disclosed Vendors segment, and the Publisher TC segment.<\/p>\n\n\nWhat is changing in TCF 2.3?<\/h2>\n\n\n\n