Consent frameworks (TCF v2.2 / GPP)

IAB TCF v2.2 and GPP are the standards for cross-vendor consent in EU ad-tech.

What we check

Detects IAB TCF v2.2 (__tcfapi) and GPP (__gpp) in the HTML.

Why it matters

IAB TCF v2.2 and GPP are the standards for cross-vendor consent in EU ad-tech.

Common causes

The site runs no programmatic advertising, then the finding is expected and not an error.
The CMP supports TCF, but TCF mode was never activated in the configuration.
A TCF-capable CMP runs in standard mode, the vendor list is empty.
The __tcfapi only gets injected after banner interaction, invisible to the scan in the initial HTML.

The fix

For IAB advertising: choose a TCF-v2.2-compatible CMP (OneTrust, consentmanager, Didomi); __tcfapi must be reachable.

Matching template

Consent Mode Audit Checklist

Seven layers, each with a check, a failure signal and an owner. Covers this finding and the six around it.

Get the checklist →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Related checks

Consent Mode V2 →Cookie banner / CMP →

Asked often

What does a failing "Consent frameworks (TCF v2.2 / GPP)" check mean?

IAB TCF v2.2 and GPP are the standards for cross-vendor consent in EU ad-tech. For IAB advertising: choose a TCF-v2.2-compatible CMP (OneTrust, consentmanager, Didomi); __tcfapi must be reachable.

How do you fix a failing "Consent frameworks (TCF v2.2 / GPP)" check?

For IAB advertising: choose a TCF-v2.2-compatible CMP (OneTrust, consentmanager, Didomi); __tcfapi must be reachable.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint