IAB Tech Lab and IAB Europe released ‘pubvendors.json’ and updated the GDPR Consent Framework for publishers. Let’s learn what is pubvendors.json and how it’s going to help publishers.
Soon after announcing the first version of ‘GDPR Consent Framework’ to help publishers and Adtech Vendors to comply with the upcoming GDPR law, IAB Tech Lab and IAB Europe recently launched new supporting tech specifications.
- pubvendors.json for Publishers and
- Mobile In-app Framework for app developers.
What is pubvendors.json?
The pubvendors.json is an add-on to the initially released GDPR Consent Framework. It is intended to help publishers to handle and manage the Vendors more effectively.
- It provides guidelines for publishers to index the vendors (third-parties) they’ve partnered with and their respective data rights/policies.
- It allows vendors to check the consent status of the publisher and also, confirm the consent status of a string (DaisyBit) outputted by Consent Management Platform (CMP).
- It places a standard way for publishers to whitelist vendors.
- Most importantly, it enables publishers to limit features and purposes on a per-vendor basis. For instance, the publisher can set a purpose and limit features for a specific vendor, as promised by the last framework update.
“The feedback from publishers since we launched the public consultation on the first version of the specs for the Transparency and Consent Framework included a couple of strong messages,” noted Townsend Feehan, CEO, IAB Europe. “First, publishers wanted even more control with respect to data processing purposes, notably to be able to authorize different partners to leverage different purposes. Second, they wanted more control over which legal bases their partners could adduce. The pubvendors.json solution is a rapid response to accommodate these requirements.”
What is Mobile In-app Framework?
It’s the GDPR Consent Framework designed for App developers. Similar to publishers, mobile app developers can embrace the framework to comply with the law. In this announcement, IAB released the technical specifications such as CMP endpoints, App developers’ storage, API Specs and others.
“The continued dominance of apps in mobile environments made supporting tech specs on that front particularly vital, and we’re pleased that our working group moved quickly to close that gap.”
– Dennis Buchheim, Senior Vice President, and General Manager, IAB Tech Lab
Are they finalized yet?
No. The specifications are now open for feedback and comments from the publishers, developers, and vendors. IAB Tech Lab and IAB Europe will announce the revised version of these specifications after June 1, 2018.
Can I utilize the pubvendors.json now?
“Companies with urgent transparency goals are invited to adopt the pubvendors.json technology as a beta implementation, even before the specifications are finalized”, is the message from IAB Tech Lab and IAB Europe.
So, yes! You can deploy pubvendors.json on your site.
Pretty much the same. We’re in a loop here. IAB Europe partnered with IAB Tech Lab working group and released the framework to ease the GDPR panic. Then, it was kept open for comment and feedback and now it is live.
So, the same process will repeat with these specifications. But this time, we can expect an uplift in adoption as the consortiums showed that they will address the feedback and improve the framework.
Who are utilizing the GDPR Consent Framework?
Two publishers have endorsed the arrival of GDPR Consent Framework: Axel Springer and Schibsted. Furthermore, Axel Springer advises publishers to employ the framework or else, vendors like Google will gain more control over the process.
On the other hand, mid-sized publishers who lack the resource to build their own CMPs are still struggling to settle on a solution.
GDPR Update: Spend a minute more to learn about Consent Management Platforms (CMP)