Protected Audience API

Cookies play an essential role in the modern internet. These small pieces of data stored in your web browser can do everything from saving login details to enhancing website performance to helping marketers show users products that they will love. However, not all cookies are made equal, and there are significant differences between first-party and third-party cookies.

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.

In this Media Review, we present 3 stories from the last month, including the gaining momentum of the Privacy Sandbox, analyzing why the number of entities that tested FLEDGE was so small, and the newly launched tools from Google.

In this Media Review, we describe Google’s announcement on the Single Origin Trial, Google’s Header Bidding, considerations about FLEDGE, and Tim Cook’s call for a federal data privacy law.

In this Media Review, you can find out more about Google updating the Privacy Sandbox timeline, a proposal on how to optimize FLEDGE’s performance by leveraging cloud resources, and a hypothesis around Apple building a DSP.