IAB TCF — what it is and how KukiBot handles it

An honest summary, so you can decide if KukiBot fits your ad setup.

What TCF is

The IAB Transparency & Consent Framework (TCF) is a standard used by the advertising industry. A registered Consent Management Platform (CMP) records the visitor's choices per purpose and per vendor and encodes them in a TC string that ad networks read through a JavaScript API called __tcfapi.

What KukiBot does

KukiBot provides a basic __tcfapi that answers ping and getTCData calls with the visitor's purpose choices (storage, analytics, marketing).
KukiBot is not an IAB-registered CMP, so it does not issue TC strings or per-vendor consent.

💡Full IAB TCF support — a registered CMP with TC strings for ad networks — is coming in 2027, included in every KukiBot plan, Free included.

When you need a certified CMP instead

If you show ads from Google AdSense, Ad Manager or AdMob to visitors in the EEA, UK or Switzerland, Google requires a Google-certified CMP that integrates with TCF. KukiBot does not meet that requirement — use a certified CMP for those sites.

When KukiBot is enough

For sites that use analytics and conversion tags (GA4, Google Ads, Meta, etc.) but don't sell ad space through programmatic ad networks, KukiBot's consent banner and Google Consent Mode v2 are what you need.

ℹ️Google's requirement: certified CMP requirements for AdSense, Ad Manager and AdMob.