Protected Audience API

As Chrome plans the deprecation of third-party cookies for early 2025, and the deadline is fast approaching, the AdTech ecosystem is in pressing need of a detailed plan of how the phase-out of third-party cookies will look. A clear schedule will help ensure efficient planning and coordination, allowing for a smooth transition to a stable, vibrant ad ecosystem based on Privacy Sandbox. To help achieve this clarity—and to initiate a wider discussion—in this blog post, we will propose what we believe is a viable next step after the 1% deprecation.

In early 2020, Google first announced its intention to retire third-party cookies from Chrome. Despite numerous twists and turns, one thing remains certain: the relevance of third-party cookies is on a downward trend across most browsers, and this will likely affect Chrome as well. This development has marketers worried about the future of personalized and relevant advertising. The good news is they don’t need to be concerned. RTB House has managed to fine-tune Chrome’s new cookieless tool—the Privacy Sandbox—so that it can tailor ads to specific users while protecting their privacy. How is this possible, and what role does the Product-Level Turtledove play in the process? Let’s dive into it.

In this Media Review, you can read 5 stories, including Google renaming FLEDGE to Protected Audience API, results from Google Ads’ IBA testing, and more details about Apple’s change in Safari.