3rd-party Cookies

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.

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.

Google has released an article announcing the availability of Bidding and Auction services in the web version of FLEDGE, as well as the status on pending FLEDGE capabilities. These two Google releases could have a major impact on the adoption of FLEDGE in the near future.

In this Cookieless Newsroom, you can read about the recently announced third postponement of the third-party cookies deprecation, the freshest Privacy Sandbox commitments report by CMA, and more cookieless topics.