IAB Transparency and Consent Framework v2.4
Lawwwing supports IAB TCF v2.4 and TCF Policies v5.0.b. TCF is IAB Europe's standard for communicating user privacy choices in digital advertising.
Lawwwing is a CMP registered with IAB Europe. CMP ID: 405.
If IAB TCF is already enabled on your property, you do not need an extra option. Lawwwing already applies TCF v2.4.
The changes in this version are in TCF v2.4 and Policies v5.0.b.
What is the IAB TCF?​
The IAB Transparency and Consent Framework (TCF) is a framework from IAB Europe. It defines how publishers, CMPs, and advertising vendors exchange a user's privacy choices.
TCF sets a common format for:
- processing purposes
- vendors that may process data
- consent and legitimate interest
- Features and Special Features
- other framework signals (for example, which vendors were shown to the user)
A CMP such as Lawwwing collects those choices. Vendors that participate in TCF read them and act on them.
Transparency and control​
The TCF banner presents purposes and vendors. The user can accept, reject, or configure those choices. They can also object to legitimate interest where the framework allows it.
Interoperability​
Choices are stored in TCF signals (the TC String and the CMP API). Participating vendors read them in a uniform way.
If the integrations are enabled, Lawwwing also communicates consent to Google Consent Mode v2 and Microsoft UET Consent Mode. Those integrations use their own mechanisms. They do not replace the TC String.
Using TCF does not, by itself, mean you comply with the GDPR or other data protection rules.
The publisher remains responsible for their configuration, the vendors they enable, and the legal bases they apply.
Evolution of TCF v2​
TCF v2 has been updated in several iterations. The current version is v2.4, together with Policies v5.0.b.
| Version | What changed |
|---|---|
| TCF v2.2 | Stricter legal bases, more vendor transparency, and new rules for CMPs. |
| TCF v2.3 | The Disclosed Vendors segment becomes mandatory in the TC String. |
| TCF v2.4 | standardTexts field and illustrations in the GVL, Policies v5.0.b, and changes to vendor disclosure. |
v2.3 and v2.4 do not replace the v2 architecture. The Disclosed Vendors segment from v2.3 is still part of v2.4.
TCF v2.4 and Policies v5.0.b​
v2.4 updates the technical specifications. Policies v5.0.b update the framework rules. There is no TC String 2.4 and no CMP API 2.4. Those artefacts have their own versioning. v2.4 also does not add new purposes.
Feature details, standardTexts, Special Feature 2, and IAB deadlines are in TCF v2.4 and Policies v5.0.b.
Multi-device consent​
Policies v5.0.b allow persisting choices across devices. That is not mandatory.
Lawwwing applies TCF choices per browser and device. It does not sync consent across different devices.
How Lawwwing uses it​
Lawwwing reads the Global Vendor List (GVL) for purposes, vendors, Features, and Special Features. With v2.4 it also reads standardTexts and Feature illustrations.
Choices from the banner are represented with TCF signals. If the integrations are enabled, Lawwwing also updates Google Consent Mode v2 and Microsoft UET Consent Mode.
To enable IAB TCF, follow the implementation guide. To check it, use the validation guide.
TCF v2.4 and Policies v5.0.b describes the changes in this version.
If you need help with the setup, contact us.