IAB TCF 2.3 Vendor List: How to Configure Vendors in Your CMP
What Is the IAB Global Vendor List?
The Global Vendor List (GVL) is a registry maintained by IAB Europe containing every ad-tech vendor registered under the Transparency and Consent Framework. As of 2026, it includes 1,200+ vendors. Each vendor entry specifies which data processing purposes and features it requires.
TCF 2.3 Purposes
- Purpose 1: Store and/or access information on a device
- Purpose 2: Select basic ads
- Purpose 3: Create a personalised ads profile
- Purpose 4: Select personalised ads
- Purpose 7: Measure ad performance
- Purpose 9: Understand audiences through statistics
- Purpose 10: Develop and improve products
Special Purposes (1-2) and Features (1-3) are also defined. Special purposes do not require consent.
Consent vs Legitimate Interest
Vendors can request each purpose under consent or legitimate interest. Users can object to legitimate interest processing. Your CMP must present both options correctly.
Configuring Vendors in Your CMP
- Identify which vendors your site uses (Google, Meta, Criteo, etc.)
- Match them to GVL vendor IDs
- Test TC string generation and vendor signal passing
FlexyConsent TCF Configuration
FlexyConsent loads the current IAB Global Vendor List automatically and discloses every registered vendor with its purposes and legal bases. Visitors decide per purpose and per vendor, and the TC string is generated from their choices. FlexyConsent does not narrow the list to a few vendors: the vendors are the advertisers and ad-tech partners whose demand can reach your pages, including through Google. That is the default: a publisher can limit the list to the vendors it chooses. FlexyConsent supports TCF 2.4 and is certified by Google, IAB Europe and IAB Canada (CMP ID 317).