What Is the IAB TCF?
The IAB TCF, short for the Transparency and Consent Framework, is a shared set of rules for recording and passing along what a website visitor agreed to.
It was created by IAB Europe to solve a practical problem. A single web page might involve dozens of advertising companies. Under European privacy law, each of them needs a legal basis to use someone's data. Asking a visitor about each one individually would be unusable.
The framework's answer is to ask once, in plain categories, then package that answer into a standard format every participating company can read.
Purposes, Not Cookie Categories
Most cookie banners ask about categories of cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits.: necessary, analytics, marketing. The TCF works differently and asks about purposes, meaning what the data will be used for.
There are several, but the ones that matter most for conversion tracking are storing information on the visitor's device, measuring how content performs, and using data to build profiles for personalized advertising.
Storing information comes first, because if a visitor declines it, there's nowhere to keep the record of what they did and nothing else can happen.
Why It Matters for Conversion Tracking
If your site uses a TCF banner, your analytics and advertising tools shouldn't be reading cookie categories. They should be reading the framework's signal and acting on the purposes the visitor agreed to.
Getting this wrong goes badly in both directions. If you read it too loosely, you track people who declined, and if you read it too strictly, you lose measurement from people who actually agreed.
The framework can also report a third state, not yet decided, either because the visitor hasn't chosen or because the banner is still loading. That is not consent, so tracking that treats a missing answer as a yes is tracking people who never agreed.
The TCF and the Global Privacy Platform
The TCF was built for European law and works on an opt-in basis, meaning nothing happens until the visitor actively agrees.
Much of the United States works the opposite way, on an opt-out basis, where data can be used unless the person says stop. That's handled by a newer standard, the Global Privacy Platform, which many of the same banners also support.
A visitor might fall under both. When that happens, the safe approach is to track only when every applicable set of rules allows it.
IAB TCF on WordPress Sites
Plenty of WordPress consent banners support the TCF, and some are delivered as a script from an ad network rather than as a plugin, so there may be nothing installed for your other tools to detect.
Whatever handles your tracking must read the framework's signal directly, wait until there's a real answer, and update immediately if the visitor changes their mind later.
How Conversion Bridge Helps
With the ConsentManager (IAB TCF & GPP) banner option selected, Conversion Bridge reads the TCF signal and holds tracking for every analytics and advertising platform you've enabled until there's a clear answer, then allows only the analytics or marketing tracking the visitor agreed to.
If it can't get a usable answer, it keeps waiting rather than assuming permission. If the visitor reopens the banner and changes their choices, tracking updates straight away.
Frequently Asked Questions
Do I need the TCF for my site?
Only if you work with advertising partners who expect it, or your consent banner is built on it. A small site running its own analytics generally doesn't need it, though it still needs valid consent.
Is a TCF banner enough to make me compliant?
No, the framework is a way of recording and sharing a decision. Whether your setup is lawful depends on what you collect, how you ask, and whether you honor the answer.
What happens if a visitor ignores the banner?
Nothing should be tracked, because no answer is not a yes and a visitor who never responds has not agreed to anything.