TCF v2.4 and Policies v5.0.b
TCF v2.4 updates the technical specifications. Policies v5.0.b update the framework rules. Lawwwing supports both.
v2.4 does not add new purposes and does not change how consent is collected. The main change is how the banner explains Features.
If IAB TCF is enabled, Lawwwing already uses v2.4. There is no extra toggle and no script change.
If you have not enabled it yet, follow the implementation guide. The general TCF overview is in What is IAB TCF.
Policies v5.0.b and specifications v2.4
IAB Europe published two documents together.
| Document | What it covers |
|---|---|
| Policies v5.0.b | Rules: how to inform the user, how to present Features, and how consent may apply across devices. |
| Technical Specifications v2.4 | Implementation: standardTexts field in the GVL, Feature illustrations, and vendor disclosure. |
There is no TC String 2.4 and no CMP API 2.4. Those artefacts have their own versioning.
How the banner changes
Purposes, toggles, and banner order stay the same. The visible changes are in the second layer (preferences).
Each Feature shows a standard GVL text (standardTexts). That text states that Features are means of processing tied to purposes the user can choose. They are not a separate toggle.
Each Feature also has an illustration, matching purposes.
| Special Feature 2 | Name |
|---|---|
| Before | Actively scan device characteristics for identification |
| Now | Identify devices based on information actively requested |
It is the same Special Feature. Where the framework requires it, it still needs opt-in.
The IAB controls TCF texts, translations, and illustrations. In Lawwwing you can change design and style, not that content.
Updating from TCF v2.3
Nothing to migrate if IAB TCF is already enabled.
To enable it, use the implementation guide. To check it, use the validation guide. In the second layer of the banner you should see the Feature texts and illustrations.
IAB timeline
| Date | Milestone |
|---|---|
| 29 May 2026 | Policies v5.0.b published |
| 23 July 2026 | Specifications v2.4 and the updated GVL published |
| 23 October 2026 | Deadline for CMPs in web environments |
| 23 February 2027 | Deadline for native apps and CTV |
Official resources: IAB Europe TCF Supporting Resources.
Frequently asked questions
Will my users see the banner again?
No. This update does not require showing the banner again or collecting a new consent.
Are the purposes the same?
Yes. v2.4 does not add or remove Purposes, Special Purposes, Features, or Special Features. It changes how Features are explained and the name of Special Feature 2.
Can I edit the new Feature texts?
No. Texts, translations, and illustrations come from the IAB GVL. You can still customize the banner design in Lawwwing.
Does Google Consent Mode still work with TCF?
Yes. You can use IAB TCF and Google Consent Mode together. TCF communicates consent to advertising vendors. Consent Mode communicates it to Google services.
The framework overview is in What is IAB TCF.
If you need help with the setup, contact us.