The cookie is already gone. The budgets have shifted. All the howlers screaming about Chrome’s road map for deprecation are akin to the last soldiers standing on the battlefield clinging to the flag of a fallen nation. In short, it’s over.
But we can’t measure the downfall of cookies by looking at the bidstream. There is still plenty of cookie-based buying going on. The old user-sync systems are still playing pixel ping-pong with cookie-enabled browsers.
This article was originally posted on Advertising Week. Be sure to pop over there when you’re done and catch up on identity, privacy, and the latest industry news.
What can playfully be described as a kerfuffle around how DSP IDs are being derived in the bidstream, the recent discord at the IAB Tech Lab has exposed not only shortcomings in the RTB protocol, but also a functional deficit in the programmatic ecosystem.
At the heart of the debate is the issue of how some SSPs and publishers are using probabilistic methods to apply DSP user IDs to requests from browsers that do not have 3rd party cookies enabled. Historically, DSP IDs have only been pinned to a cookie. Any bridging of IDs from a cookie-enabled browser to another browser, no matter how reliable the methodology, is not in-line with many DSP expectations. A shorthand term for this activity could be ID-Bridging. This is not the worst form of the practice. And it can grant a publisher additional coverage of DSP IDs, resulting in more revenue, but can result in some blowback when the DSPs realize that the user’s browser doesn’t actually have their cookie.
Read more
