Use case

What Velo can and can’t do for consent on ad funded sites

Velo is not yet a registered IAB TCF CMP. This page sets out which ad funded sites Velo can serve today, and which need a registered CMP instead.

Examples on this page use sample data. This is not legal advice.

Read this first

Velo is not yet a registered IAB TCF CMP, and not a Google certified one

If your revenue depends on AdSense, Ad Manager or programmatic partners in the EEA, the UK or Switzerland, you need a consent platform that is both. TCF v2.3 support is in development, and we do not give a date.

How is your site paid for?

Advertisers buying through exchanges read consent from a TC string, written by a consent platform registered with IAB Europe. Other kinds of revenue do not need one.


RevenueWhat reads the consentVelo today
Sponsorships sold directlyNothing automated. The sponsor’s creative is part of your page.Fits
Affiliate linksThe affiliate network’s script, which you mark as advertising.Fits
Your own products or subscriptionsYour analytics and advertising tags, through Consent Mode v2.Fits
AdSense or Ad Manager in the EEA, the UK or SwitzerlandGoogle, which asks publishers for a certified CMP.Not yet
Header bidding and exchangesEach buyer, from a TC string.Not yet

Two sites with two different answers

Two ad funded sites ask the same question.

Illustrative example with sample data, not a customer story.


A recipe blog paid by affiliates and a sponsor

No exchange is involved, so nothing reads a TC string. Velo sets Consent Mode for analytics, holds the affiliate network’s script until advertising is allowed, and records each choice.

A news site running AdSense and header bidding

This site needs a consent platform registered with IAB Europe and certified by Google. Velo is neither yet, so it is the wrong choice for this site today.

What Velo does on an ad funded site

On the sites it fits, Velo does three things.

Get for free

Hold advertising scripts

Mark a script with the advertising category and it stays inert until the visitor allows advertising. Scripts you do not mark are not blocked.

The Velo console overview: two newly detected scripts, each with its provider and category and the status held until consent, above a preview of the live consent banner.

Signal Google, Meta and Microsoft

Velo sends Consent Mode v2 to Google tags, plus the matching consent calls for the Meta Pixel and Microsoft UET.

Respect opt out signals

In opt out regions, a browser that sends Global Privacy Control has advertising switched off automatically, and the decision is recorded as a GPC refusal.

What Velo covers, and what it does not

The limits, stated plainly, so you can decide before you install anything.


TCF statusNot yet a registered CMP. TCF v2.3 support is in development and registration with IAB Europe is being prepared.
Google certificationVelo is not a Google certified CMP for AdSense, Ad Manager or AdMob.
No TC stringVelo does not write a TC string or expose the TCF API today.
Consent Mode v2Supported on every plan, for sites that buy advertising.
No date promisedWe do not publish a date for TCF registration. The TCF status page says where it stands.
Not legal adviceVelo gives you the banner, the signals and the records. Whether your setup meets the law in your sector is for you and your advisers to decide.

Questions and answers

Can I use Velo with AdSense or Ad Manager?

Not for visitors in the EEA, the UK or Switzerland if Google requires a certified CMP for your setup. Velo is not certified yet.

I only buy ads. Do I need the TCF?

Usually not. Advertisers measuring Google Ads, Meta or Microsoft campaigns need accurate consent signals for those tags, which Velo sends. The TCF matters when you sell ad space.

When will Velo be a registered TCF CMP?

We do not give a date. Support for TCF v2.3 is in development, and the TCF status page says where it stands.

Free for one site

Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.