As a follow-up to our previous message on the switch to IAB’s Transparency and Consent Framework version 2 (TCF v2), please note the following.
- On August 11th, all TCF installations will default to version 2 – this includes even cases where tcfVersion: 1 has been declared. Using version 1 will no longer be possible in anticipation of version 1 being deprecated by IAB starting August 15th.
- We’ve updated our mobile SDK for TCF v2, if you haven’t already, please be sure to update. You can read the guide here.
- If you’re using AMP, you must update your integration for TCF v2. You can update the plugin here or if you’ve built your own integration with AMP, you can update it to v2 by following this guide.
We now support Google’s “Additional Consent Mode”!
Please note that support for this feature is only available via the beta channel.
Additional Consent (AC) is meant to serve alongside TCF v2.0 “as a bridge for vendors who are not yet registered on the IAB Europe Global Vendor List (GVL)”. The AC specification enables the processing of additional consent – alongside the TCF v2.0 implementation — for Google’s partners who aren’t yet registered with the IAB Europe Global Vendor List but are on Google’s Ad Tech Providers (ATP) list.
Cookie Solution Fixes
IE11 / TCF v2 conflict fix
You can access the latest version of the Cookie Solution via your iubenda dashboard →
Other fixes and updates
- Cookie character-limit for long strings fixed. Service specific consent infrequently result in strings that are too long to save in a single cookie. We’ve added a fix for handling such very long consent strings, which allows the consent to be saved in multiple cookies.
- TCF banner shortened. IAB has agreed to remove some information from the required banner disclosures (e.g. the legitimate interest disclosure).
- IAB library bug solved. We’ve added a fix for an IAB library bug which resulted in the consent string non being passed correctly to vendors.
You can view all fixes and updates in the Cookie Solution changelog.