\n<\/p>\n
Here we go again\u2026<\/p>\n
After months and months of promises, pinky promises, and stone-faced utterances of \u201cNo, we really really<\/em> mean it this time!\u201d, Google has officially announced what in recent weeks appeared increasingly inevitable: Third-party cookie deprecation in Chrome will be delayed. Again. This time, to an as-yet unannounced time beyond Q4 2024.<\/p>\n The deciding blow to this latest missed deadline came after a damning\u00a0report\u00a0by the UK\u2019s Competition and Markets Authority (CMA) indicating that Google\u2019s Privacy Sandbox would fall short of meeting the country\u2019s regulatory standards.<\/p>\n Per Google\u2019s\u00a0announcement: \u201cWe recognize that there are ongoing challenges related to reconciling divergent feedback from the industry, regulators and developers, and will continue to engage closely with the entire ecosystem. It\u2019s also critical that the CMA has sufficient time to review all evidence including results from industry tests, which the CMA has asked market participants to provide by the end of June. Given both of these significant considerations, we will not complete third-party cookie deprecation during the second half of Q4.\u201d<\/p>\n The news was met with a mix of intrigue, side eye, and shrugs from an industry that has grown increasingly frustrated with Google\u2019s approach to the issue and largely unsatisfied with the Privacy Sandbox\u2019s inconsistent rollout.<\/p>\n \u201cThe entire ad industry can\u2019t be ready for change if Google isn\u2019t ready for it,\u201d said Noor Naseer, VP of Media Innovations & Technology at Basis Technologies. \u201cAs things stand today, there\u2019s a lot of ambiguity around the application of Privacy Sandbox tools\u2014almost everything the average advertising professional knows about Privacy Sandbox is hearsay. Few have tested it, and they\u2019re all waiting for more reviews on who else has done it, how they\u2019ve done it, and to what degree of success. So this update is not a surprise, but a welcome sigh of relief, even if it\u2019s just a temporary one.\u201d<\/p>\n For now, it appears that Google is\u00a0eyeing\u00a02025 as its latest target for deprecating cookies from Chrome. But the delay is expected to be temporary, with the goal of giving the company, industry partners, and regulators enough time to work through their laundry list of concerns with the Privacy Sandbox APIs.<\/p>\n \u201cWhile the industry is getting a bit more time\u2014which certainly provides some relief\u2014the way I see it, this isn\u2019t a reason to take the foot off the accelerator,\u201d said Ian Trider, VP of Product \u2013 DSP at Basis. \u201cNo matter what, the status quo will not persist forever, and there’s basically zero chance that third-party cookie deprecation doesn\u2019t happen at all.\u00a0At this stage, it\u2019s a matter of making sure that there are sensible technical solutions, and that Google is addressing any risk of anti-competitive behavior to the satisfaction of regulators.\u201d<\/p>\n At Basis, the news of Google pushing back the third-party cookie phase-out to early 2025 is being seen as an opportunity for further refinement. \u201cThe delay isn’t ideal, but it’s an opportunity,\u201d said\u00a0Robert Kurtz, Group VP, Search Media Solutions at Basis. \u201cWe were prepared for the initial 2024 deadline, but with this extended runway, we can double-down on our cookieless targeting strategy, with more in-depth testing and optimization of privacy-focused solutions, first-party data initiatives, and additional partnerships to ensure a smooth transition.\u201d\u00a0<\/p>\n \u201cBy utilizing this delay strategically,” said Kurtz, “the industry can emerge stronger in the cookieless future.\u201d<\/p>\n —<\/p>\n While third-party cookie deprecation in Chrome may be delayed, the advertising industry is already working to embrace a more privacy-friendly future. Learn more about how marketers are confronting signal loss in our report, Identity vs. Privacy: Digital Advertising in a Cookieless World<\/strong>.<\/p>\n<\/div>\n