Glossary

IAB TCF

The Transparency and Consent Framework, an advertising-industry protocol that encodes consent into a string vendors in the programmatic chain can read.

Artefact
The euconsent-v2 consent string
Audience
Programmatic advertising participants
In StrongPrivacy
Detected as a consent artefact, not implemented

What it is for

Programmatic advertising can involve multiple participants that do not have a direct relationship with the visitor. The TCF expresses a publisher’s consent information in a machine-readable string that identifies purposes and vendors for downstream participants.

It is a heavyweight framework commonly used by publishers and programmatic advertising participants. Whether an ecommerce or SaaS site needs it depends on the advertising platforms, demand partners and contracts in its stack; having named vendors and category controls does not by itself replace a TCF integration that a partner requires.

How StrongPrivacy treats it

StrongPrivacy is not a registered TCF consent management platform and does not emit a TCF string. What it does do is recognise one: the `euconsent-v2` and `addtl_consent` cookies are classified as an IAB TCF consent string in the functional category, so a scan of a site that already runs a TCF platform reports it accurately instead of leaving it unattributed.

If you run real-time bidding, check this first

A publisher whose ad stack requires a TCF string needs a registered CMP for that part of the site. This is a scoping question worth settling before a migration rather than after.

Common questions

Do I need TCF for a normal business website?

Only if your advertising stack or partners require it. Real-time bidding is a common case, but publisher tooling, demand partners, Google Ad Manager or contractual requirements can also be relevant. Inventory the actual integrations rather than deciding from the site’s business label.

Will a scan show me if a site is running TCF?

Yes. The consent string cookies are in the classification catalogue, so they appear attributed rather than as unknown functional cookies.

Sources and verification

Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.

See what your own site is loading

A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.