This is an evolving subject to write about, as nearly every day there is a new announcement out about how the deprecation (read, elimination) of 3rd-party cookies is going to affect advertisers, publishers, and ad-tech vendors. We’ll do our best to update this post as the latest changes emerge.
There is a lot being said about the “death of cookies” as Google and Apple remove support for 3rd-party cookies from their Chrome and Safari browsers. This is a big shift in the way advertisers identify and track consumers on their own sites and across the internet, so the changes to digital advertising are substantive. But the true impact is confusing, so let’s answer some of the key questions here.
In response to GDPR and other privacy legislation, Apple and Google have taken steps to remove 3rd-party cookie support from their browsers. It's important to note that this is only for cookies placed on sites by others (hence “3rd-party”) but doesn’t impact the beneficial experience of 1st-party cookies, those that make logging in and filling out certain forms a better experience for consumers.
An example? When you visit Amazon.com, your log-in information for Amazon remains intact. But if you visit a site like The Guardian, they can only maintain knowledge of who you are if you log into the platform, and then only know what you do on their site. If you go from Amazon to The Guardian, they won’t know you are the same person and target ads based on that. Similarly, Apple and Google are removing some support for device- and IP- based identifiers.
There are a number of new initiatives to help solve the problem of identifying a consumer across devices in this new post-3rd party cookie environment. Let’s separate them out here.
Aptly named to reflect the aggregation of data at the cohort level, Google's FLoC (Federated Learning of Cohorts) will allow marketers to target consumers at a less granular level than before. In the past, Google allowed targeting across devices even though no information was exchanged. The call for an ad used consumer data based on cookies placed on sites other than Google (hence “3rd-party”).
In their most recent announcement, Google agreed neither to allow others to sell ads based on anything more specific than this cohort-level abstraction, nor will they allow the use of other cross-site or cross-device identifiers that are being developed by The Trade Desk and others (see below). Google claims they are doubling down on their Privacy Sandbox, keeping the targeting of consumers further protected (though they are still able to target based on 1st-party data created by visits across Google properties like search and YouTube).
Apple and Firebox were the first to move away from the cookie in their browsers. Apple has received renewed attention as it relates to the mobile equivalent of cookies, their IDFA, which we wrote about here.
Data providers who work closely with marketers or media networks have been working on alternative identifiers to the 3rd-party cookie, including Unified ID 2.0 (developed by The Trade Desk) and LiveRamp’s ATS. They attempt to associate online behavior with a piece of first-party data like an email address, making addressable advertising possible — at least for those individuals who have somehow made themselves known, typically through a log-in on a publisher site.
In order to be vendor-agnostic, The Trade Desk recently handed future development of the Unified ID to Prebid.org, which created a privacy-compliant universal ID called SharedID for all publishers and vendors to conform to.
In light of the removal of the cookie in the future, Google's been working on a Privacy Sandbox initiative, which is a suite of experimental tools designed to ultimately replace all useful bits of cookie functionality, in a privacy-compliant way.
One of the more important aspects of cookie-based functionality is the ability to target users according to their browsing behavior, so that we can target them with relevant messaging. While Ad-Lib.io is not actually responsible for the targeting itself, it's important for us that the platforms that are responsible (DV360, etc) are able to do this.
As we near the end of this cookie-based mechanism for targeting digital advertising, we looked at campaigns that clients run with Ad-Lib.io. Here’s what we found:
In other words, while it is true that using cookies as a mechanism for 1:1 messaging is going away, there will continue to be more privacy-compliant solutions that will allow us to continue personalizing creative in a much more nuanced way than broadcast TV! The creases continue to be ironed out by the likes of Google and Facebook, but from an Ad-Lib.io perspective, we are confident that we are integrated with the right platforms to be able to capitalize on the best targeting in the industry.
Meanwhile, we await news on how the other aspects of the Google Privacy Sandbox (Turtledove, etc.) are shaping up. These are looking to solve other problems such as supporting third-party data and attribution.
If you want to learn more about how to produce and optimize your most relevant ad content in a post-cookie, contact us at https://www.ad-lib.io/contact-us.
In this episode of NDA Meets, Dean Weaving, Head of Display, Video & Social at Deliveroo, shares how his team used relevant creative to boost CTR 2870%.
Read how the purchase of Ad-Lib.io will help Smartly.io expand from paid social-media offerings into Google platforms.