The TCF, or Transparency and Consent Framework, is IAB Europe's standard for recording what a visitor consented to and passing it to the advertising companies that buy and sell ad space. Your site needs it only if you sell advertising space, or if a vendor demands it. Sites that simply buy ads and measure them do not.
What the framework actually is
The Transparency and Consent Framework is published by IAB Europe. It exists because programmatic advertising involves a long line of companies who never meet the visitor, and each of them needs to know what that visitor agreed to. The framework standardises the answer: a fixed list of purposes, a register of vendors, and an encoded record called a TC string that travels with the ad request.
A consent platform that participates in the framework is registered with IAB Europe, presents the standard purposes, writes the string, and exposes it through a defined interface so the rest of the chain can read it. That registration is the part people mean when they say a platform is TCF certified.
What matters for the question in the title is what the framework is for. It is plumbing between businesses. It was designed for the case where your consent decision has to be understood by a company you have no relationship with, several steps away, in a real time auction.
Who actually needs it
If you sell advertising space on your site through programmatic channels, you are inside that chain and the chain will ask you for a string. Google also requires a certified consent management platform for serving ads to visitors in the EEA and the UK through its publisher products, and the framework is the usual way sites satisfy that.
If you are on the other side, buying advertising to bring people to your own site, you are not in the chain. Nothing in your stack is waiting for a TC string. What your tags are waiting for is a consent signal, which is a different mechanism entirely.
The confusion that costs people money
The framework and Consent Mode v2 get treated as two names for the same job, and they are not. Consent Mode is how Google's own tags on your own site learn whether they may use cookies. The TCF is how the advertising supply chain learns what was agreed. One governs the tags you installed. The other governs companies you will never speak to.
The practical consequence shows up in a familiar way. A site turns the framework on, sees the vendor list appear in the banner, and reasonably concludes that consent is now handled. The tags on the page never receive a Consent Mode signal, because nothing sent them one, and the analytics quietly go wrong in the way a missing consent state always makes them go wrong. The banner looks more sophisticated than it did before, which is precisely why nobody re examines it.
It happens in the other direction too. A perfectly wired Consent Mode setup says nothing at all to the supply chain, so a publisher who needs a string and does not have one finds their inventory treated as non consented regardless of what visitors actually chose.
How to decide, in about five minutes
Ask whether an ad request leaves your site
Not whether you advertise. Whether your pages call an ad server or an exchange to fill a slot. If nothing on your site sells space, the framework has no counterparty to talk to and you can stop here.
Check the products, not the brand names
Buying Google Ads is not the same as serving Ad Manager, AdSense or AdMob. The first makes you an advertiser and the second makes you a publisher, and only the second brings the certified platform requirement with it.
Read the contracts you already signed
Some vendors and networks name the framework explicitly in their terms. If one of yours does, that settles it for you regardless of the reasoning above.
Then check the signal you definitely need
Whatever the answer, your own tags still need a correct consent state. Decline everything in a clean browser profile and confirm the outgoing request says so. A consent platform that writes a TC string can still be failing this.
Most sites that ask us this question turn out not to need the framework, and are relieved, because it means a shorter banner and fewer choices to explain. The sites that do need it usually knew already, because a partner told them.
Velo sets the Consent Mode state from one snippet before your tags initialise and keeps the record of what each visitor chose. Where the framework itself fits, and where Velo stands on it, is written down on the TCF status page. The rest of the mechanism is on the product page.
Common questions
What is the TCF, and does my site need it?
The TCF is the Transparency and Consent Framework, a standard published by IAB Europe for recording what a visitor consented to and passing that record down the advertising supply chain as an encoded TC string. Your site needs it if you sell advertising inventory through that chain, or if a vendor or ad product you use requires a certified consent platform. A site that runs analytics and buys its own advertising does not need the TCF, and turning it on adds vendor lists and complexity without adding anything the site uses.
What is a TC string?
It is the encoded record the framework passes around: which purposes the visitor agreed to, which vendors were disclosed, which version of the policy applied, and when the choice was made. Ad tech partners read it to decide what they are allowed to do. It is written by the consent platform and travels with the ad request, which is why it only matters when there is an ad request going into the supply chain in the first place.
Is the TCF the same as Consent Mode v2?
No, and this is the most expensive confusion in the area. The TCF speaks to the advertising supply chain. Consent Mode speaks to Google's own tags on your site, telling them whether they may use cookies. They are two separate messages to two separate audiences. Turning the TCF on does not set your Consent Mode state, and a correct Consent Mode state says nothing to the supply chain. A site can have one right and the other broken, and the reporting damage looks the same either way.
Do I need a TCF certified consent platform to run Google Ads?
Buying Google Ads to bring people to your own site does not put you in the framework. What Google requires a certified consent management platform for is serving ads to visitors in the EEA and the UK through its publisher products. If you are the advertiser rather than the publisher, the requirement that applies to you is a correct consent signal to your tags, which is Consent Mode, not a TC string.
What happens if I turn the TCF on and my site does not need it?
You inherit a vendor list and a purpose model built for programmatic advertising, shown to visitors who will never be part of it. The banner gets longer and the choices get harder to read, which is a poor trade for a site that gains nothing from the framework. There is no compliance benefit to offset it either, because the obligations you actually have are met by asking clearly and honouring the answer.