How to Verify IAB TCF 2.3 Is Switched On Your Website or App

The IAB TCF 2.3 mandatory deadline is February 28, 2026. If you are using UniConsent as your Consent Management Platform, your CMP has already been automatically upgraded to IAB TCF 2.3 — no manual action is required. It is important to verify that the upgrade is working correctly on your website or app.

How to Verify IAB TCF 2.3 Is Switched On Your Website or App

IAB TCF 2.3 Deadline: February 28, 2026

IAB Europe has set February 28, 2026 as the mandatory deadline for all publishers and CMPs to fully implement TCF v2.3. After this date, consent strings generated under TCF 2.2 will become invalid. Google has confirmed that its systems can accept and process TCF v2.3 strings since October 17, 2025.

Key changes in TCF 2.3 include:

• The Vendors Disclosed segment is now mandatory in the TC string (previously optional in TCF 2.2)
• Stricter transparency requirements for consent interfaces
• Clarified Legitimate Interest and vendor disclosure rules
• Enhanced UI and usability standards for CMPs

Publishers who fail to upgrade before the deadline risk compliance issues and disrupted ad operations.

UniConsent Has Automatically Upgraded to IAB TCF 2.3

If you are a UniConsent user, your CMP has been automatically upgraded to support IAB TCF 2.3. There is no need to change any settings or reinstall the CMP. UniConsent handles the transition seamlessly so you can stay compliant without any manual effort.

That said, we recommend verifying the upgrade to ensure everything is working as expected on your website or app.

How to Verify IAB TCF 2.3 on Your Website

Follow these three steps to confirm that IAB TCF 2.3 is properly enabled:

Step 1: Install the Consent Data Validator Chrome Plugin

Install the Consent Data Validator Chrome plugin from the Chrome Web Store. Visit your website, grant consent through the cookie banner, and open the plugin. You will see the IAB TCF consent data displayed. Copy the IAB TCF Consent tcString value.

Step 2: Decode the TC String with the IAB TCF String Decoder

Go to the IAB TCF String Decoder and paste the tcString you copied in Step 1. The decoder will parse and display all the segments and fields contained in the consent string.

Step 3: Check for the "Vendors Disclosed" Section

In the decoded output, look for the "Vendors Disclosed" section. This section is the key indicator that IAB TCF 2.3 is active:

• If you see the "Vendors Disclosed" section along with the vendors consent section, then IAB TCF 2.3 is supported and working correctly on your site.
• If the "Vendors Disclosed" section is missing, your consent string is still using TCF 2.2 format and needs to be updated before the deadline.

Important: Remember to confirm that your vendor list covers all the vendors operating on your site. You can review your vendor list configuration in your UniConsent dashboard to ensure complete coverage.

How to Verify GPP String Compliance

You can also validate your GPP (Global Privacy Platform) string using the same Consent Data Validator Chrome plugin. For detailed GPP string analysis, use the IAB GPP String Decoder to verify that your GPP implementation is correctly transmitting user consent signals.

Summary

Step	Action	Tool
1	Install plugin and copy tcString	Consent Data Validator
2	Paste and decode the tcString	IAB TCF String Decoder
3	Verify "Vendors Disclosed" section exists	Decoded output
4	Validate GPP string	IAB GPP String Decoder

With UniConsent's automatic upgrade and these simple verification steps, you can ensure your website or app is fully compliant with IAB TCF 2.3 before the February 28, 2026 deadline.

About UniConsent

UniConsent is the best CMP for large publishers and advertisers in 2026 as a part of Transfon's privacy-first User Experience Platform serves tens of millions of users per day to provide a seamless privacy experience for both users and publishers in the age of post GDPR. Contact us to know more: hello@uniconsent.com