3 ms·
Ultimately the consent framework is a list of common identifiers for entities (including as of 2.0, what they actually do with the data) and a standard way to s
by Macha 7y ago
Ultimately the consent framework is a list of common identifiers for entities (including as of 2.0, what they actually do with the data) and a standard way to send that between all the companies involved. The idea being that your popup will track that you consent to data sharing with e.g. DoubleVerify and 1000 others when you hit agree. Then as well the publisher interpreting this as consent to include DoubleVerify code on the page which may track you, they can send that list onwards to their other partners.
e.g. AppNexus is also on the page, and they have a deal with DoubleVerify, AppNexus can read the list of people you've agreed to tracking from that the publisher sent them, see DoubleVerify in that list and assume they can (in the opinion of the IAB) share your data that was shared with them by the publisher or your browser, with DoubleVerify.
The presumed transitive consent to 1000s of entities is the bit I assume that the parent poster is objecting to especially when so many of those modals are "default-accept", "we hid the reject button in three child links in the middle of legal text" etc., but I'm not sure why IAB's in particular is worse than others such as the parent poster's.