AdTech Europe

Consent on EU traffic: TCF 2.2 and Google Consent Mode v2

If your advertisers buy EU traffic, consent signals must travel correctly from the visitor to the bid. The platform supports this in several ways.

For publisher sites: TCF 2.2

  • Consent Manager — $990. An IAB TCF 2.2 consent banner for your publishers, so consent signals pass correctly into every bid request. Branded; described as GDPR and ePrivacy ready.
  • Cookiebot — $1,490 and OneTrust — $2,490. Connect an existing consent platform so each visitor's consent is passed into targeting and reporting automatically. Both TCF 2.2 ready.

For advertisers' landing pages: Google Consent Mode v2

Google Consent Mode v2 (included) sends the consent signals Google requires for EU traffic, so Google campaigns keep measuring and remarketing.

For publishers on the SSP side

The publisher panel includes GDPR, COPPA and CCPA settings (see Programmatic DSP — publisher panel).

Audience features and consent

Audience-based tools such as Value Bidding state that consent is respected. A per-advertiser Do Not Track toggle was added in release v6.10.

Who is responsible

As controller for your advertising data, choosing a lawful basis and collecting consent where needed is your responsibility. The tools pass the signals; they don't decide your basis.

This article explains how the platform works — it is not legal advice. Take your own advice on your obligations.

Related: GDPR: who is the controller? · Data subject rights

Nov 13, 2026

Not finding what you're looking for? Contact Us Directly