TCF Vendors

CookieFrame supports the IAB Transparency and Consent Framework (TCF) so you can collect, store, and transmit consent signals to ad tech vendors that require TCF compliance.

When to use TCF Vendors

Enable TCF Vendors if you serve ads in regions where TCF is expected (for example, the EEA and UK) or if your vendors require a valid TCF consent string.

Enable TCF

TCF works when both the framework and a vendor list are configured.

1. Go to Settings → Compliance and enable IAB TCF 2.3.
2. Open Settings → TCF Vendors.
3. Select a vendor template:
   • IAB Global Vendor List (default)
   • IAB + Google Additional Consent (includes Google ATP vendors)

Manage your vendor list

You can control which vendors appear in your consent dialog and are eligible to receive consent signals.

1. In Settings → TCF Vendors, select Customize Vendors.
2. Enable or disable vendors as needed.

Your selection determines the vendors shown to users and the list used when generating the consent string.

Vendor list updates

CookieFrame syncs the IAB Global Vendor List (GVL). When the list updates, your selected vendors remain selected unless a vendor is removed or deprecated.

Consent string and signals

When TCF Vendors are enabled, CookieFrame generates a TCF consent string (TC String) based on the user choices in your banner and preferences. The widget exposes the TCF CMP API (__tcfapi) so compatible tags can read consent.

The consent string and consent state are stored in localStorage as:

• cf_tcf_string
• cf_tcf_consent

Troubleshooting

• Vendor not showing: Confirm it is selected in Settings → TCF Vendors and still present in the IAB list.
• No consent string: Ensure TCF is enabled in Settings → Compliance and that the banner is live so users can grant consent.
• Integration not receiving consent: Verify the integration supports TCF 2.3 and is reading the TC String via __tcfapi.