Kacper Polewiak

This article aims to complete the round of quality tests performed on the sampled Seller-Defined Audiences signals we received from the sell side. While the previous article investigated contextual SDAs, this one will focus on user SDAs and verify how they reflect reality. The tests in this section varied from the ones performed on the contextual signals as the nature of the user type differs. The first test relied on a manual check of an assignment mechanism, while the second one was based on a survey campaign.

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.

Despite their seemingly innocent name, cookies have found themselves at the heart of one of the internet’s biggest privacy revolutions. Specifically, third-party cookies have come under fire from privacy-advocacy groups, ultimately leading Google to work towards a cookieless future. This change will have significant implications for advertisers, as third-party cookies have been an essential targeting technology since their inception.

Let’s dive into the implications of Google’s decision and how you can prepare for the cookieless future.

The cookieless future is fast approaching. This decision by Google, sparked by very real privacy concerns, removes a key personalization capability for advertisers: third-party cookies. To counteract this, Google has been building a series of tools to replicate their functionality, and today we’re going to dive into one of them: Google Topics API.

Google is coming for your cookies, and not the tasty kind lying safely in a tin in your kitchen, but the third-party ones that sit in your browser, watching, waiting, and storing all kinds of information. This has major implications, some good and some bad, for marketers and consumers alike. It also means that many of our old tools will soon become obsolete. However, you don’t need to crack open your tin of real cookies and start stress-eating yet. There are plenty of new tools on their way, one of which we’re going to get into today: The Protected Audience API.

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.