Standards

Velo and the IAB TCF.

Where Velo stands on the Transparency and Consent Framework, what we are building for TCF v2.3, and whether you need it at all.

Last updated 15 July 2026 · Velo, a product of AmplioData OÜ

This page is the honest record of Velo's TCF status. We update it as our registration with IAB Europe moves forward.

1. What the TCF is

The Transparency and Consent Framework is IAB Europe's standard for collecting consent for programmatic advertising and passing it down the adtech chain. Under the TCF, a consent management platform has four duties: show users which vendors a publisher works with and let them choose, do the same for the purposes each vendor wants to rely on, capture those choices in a TC String, and make sure the choices reach the vendors that must honour them.

The current version is TCF v2.3. IAB Europe runs the framework, keeps the official list of registered CMPs, and validates every CMP before it gets an ID. Details live on the TCF for CMPs page.

2. Where Velo stands today

Velo is not yet a registered TCF CMP. We would rather say that plainly than imply otherwise.

What Velo does today is a consent banner with Google Consent Mode v2 wired natively, which is what advertisers need to keep their own measurement whole. Full TCF v2.3 support is in development, and we are preparing our CMP registration with IAB Europe. Once we pass CMP validation, Velo receives a CMP ID and appears on the official CMP list. This page will say so the day it happens.

3. What we are building for TCF v2.3

  • The __tcfapi CMP API, so vendors on the page can read consent the standard way.
  • TC String encoding and storage, including the disclosedVendors segment that every TC String created after 28 February 2026 must carry.
  • Global Vendor List fetching and caching at the edge, so vendor disclosures stay current without slowing the banner down.
  • The standard TCF purposes, with the official translations and illustrations.
  • Google Additional Consent, the AC string, so Google ad partners outside the Global Vendor List are covered too.

4. Do you need a TCF CMP?

It depends on how your site earns.

  • You sell ad space. If you monetise with AdSense, Ad Manager or another programmatic stack in the EEA, the UK or Switzerland, Google requires a certified TCF CMP. Velo cannot serve that need until our registration completes, and we will not pretend it can.
  • You buy ads. If you run your own campaigns and need conversions measured and modelled correctly, the piece you need is Google Consent Mode v2 done well, not the TCF. That is what Velo ships today.

Plenty of publishers end up needing both: the TCF for the ad stack, Consent Mode v2 for their own measurement. One banner should handle the two together, and that is exactly the shape Velo is building toward.

5. Questions, answered

Is Velo a registered TCF CMP?

Not yet. Registration is in progress. You can verify any CMP's status on IAB Europe's official CMP list, which is the only source that counts. When Velo's CMP ID is live, we will announce it and update this page.

What is a TC String?

A compact, encoded record of a user's consent choices: which purposes they allowed, which vendors, and on what legal basis. CMPs create it, store it, and pass it to vendors so the whole adtech chain sees the same decision.

Can I use Velo with AdSense or Ad Manager today?

If Google requires a certified TCF CMP for your setup, not yet. Use a registered CMP in the meantime, or talk to us about timing at hello@veloconsent.com.

Does Consent Mode v2 replace the TCF?

No. They do different jobs. Consent Mode v2 tells Google how to treat and model your own measurement. The TCF tells the entire adtech chain what the user allowed. Publishers monetising with programmatic ads usually need both.