What we know about Google’s announcement and what you should start doing now
Google’s recent announcement regarding the Topics API is the next step in the evolution to a cookieless world. If you weren’t keeping up with all the relevant proposals, here is a summary of what’s happening and why it’s relevant.
The Topics API is replacing Google’s FLoC proposal, which assigned users to certain audience groups by web behavior, tracked by the browser. Users were still being monitored by Google, much in the same way cookies track users across sites. The main difference was that site visitation was not broadcast under FLoC, but was confined to the browser.
While this improved user privacy in some ways, FLoC was not tested in Europe due to GDPR issues, including:
- Lack of user consent. Users were automatically assigned to FLoCs, which is clearly not compatible with GDPR
- Ability to fingerprint. With the large number of FLoCs being discussed, there was continued risk of bad actors trying to match FLoCs to specific users
For Google’s solution to work, it needs to function in Europe – so Topics attempts to solve FLoC’s shortcomings. The key elements of the Topics proposal are:
- When a user visits a site, up to three “Topics” will be returned to an ad request. There will be a Topic from each of the three past weeks (i.e. one Topic per week for three weeks)
- The Topics will be drawn from a taxonomy of roughly 350 different segments and modeled from the IAB content taxonomy.
- For a given week, there will be six possible assigned Topics – five based on the content the user most often consumed in that week and then a sixth, “random” Topic assigned. One to three of those top six (counting the randomly assigned one) Topics will be picked and will persist as the response to that user on that site for 3 weeks.
To simplify it – for each of the past three weeks, Google will look at what content you consumed. Based on this consumption, Google will generate five Topics for each week and add a random one. Of those, only one will be sent in response to an ad request. Since this is done for the last three weeks, each ad request gets three Topics.
Topics Looks a Lot Like Contextual Targeting
The Topic determination is interesting – it will be based on the domains and subdomains that a user visits. Google specifically says it will not parse article text to determine the content being consumed by the user and will not look at the page URL. While this is still a form of behavioral targeting, it looks quite a bit like contextual targeting – but lacking specificity such as keywords, sentiment, or more specific page level understanding.
How Topics Affects Users
Users will also have significantly more control and insight versus FLoC. Consumers will have the ability to see what Topics they are assigned and also the ability to opt out from Topics entirely. This is an important point, as Google must find a way to satisfy GDPR informed consent requirements. We would not be surprised to see an upfront “Topic banner” asking consumers for approval to be included in this targeting. Depending on how Google implements it, we could see minimal opt in, similar to what we’ve seen with Apple and IDFA.
The bottom line is that privacy seems to have driven the transition from FLoC to Topics. The targeting available via the Topics API is broad by design and seems to be somewhat analogous to legacy contextual strategies. As a result, more sophisticated and nuanced cookieless segmentation and understanding is only growing in value.
What to Do Now in Response to Uncertainty Around Topics
This move creates more clarity around what signals will be universally used and now sharpens that lens to contextual. Armed with a clearer picture on the future, advertisers and buyers will be well served to develop contextual learnings about their current audience work. We are actively investing and engaging with the digital media community in this area helping brands and their partners to prepare.
Reach out to email@example.com to get started.