Goodbye FLoC, hello Topics
Back in May, we looked at a Google proposal to replace third-party cookies with something called the "Federated Learning of Cohorts" (FLoC). Third-party cookies were once used to track users all over the web so that advertisers could, supposedly, target their ads better, but, of the major browsers, only Google's Chrome browser fails to block them today. Google took a fair amount of flak for FLoC, since it was not perceived to be much of a win for users' privacy—and was mostly a sop to the (Google-dominated) web-advertising industry. Now the company is back with a different proposal that could, eventually, replace third-party cookies in Chrome: Topics.
FLoC would effectively pigeonhole users into "opaque" categories (cohorts), so that a given cohort ID would reflect a common set of interests those users have based on their recent browsing history. But exactly what information was being communicated is unclear, and was only opaque to browser users. Advertisers would presumably have been given some information about what a given cohort ID represented (so that they can target their ads) and web-site owners could potentially correlate additional information (e.g. account information) as well as track cohort ID changes over time.
No one, other than Google and web advertisers apparently, was lamenting the loss of third-party cookies, nor really looking for another "more limited" mechanism to track users' browsing habits. But Google sits in the catbird seat with respect to the web; the company is the dominant web-advertising player while also developing and distributing the most popular browser. That has allowed it to dictate, at least to a certain extent, how user tracking will (or will not) be done.
Apparently, the uproar over FLoC succeeded in diverting that particular plan, so Topics was born. Overall, Topics is more privacy-friendly than FLoC, though it still "leaks" more information than many will be comfortable with—that is the point, after all. But it is less opaque than its predecessor, with more controls for the user, though it is still an opt-out feature, so it will be on by default unless users take action.
The GitHub Topics API repository has more technical details than the introductory blog post linked above. The basic idea is that the browser tracks the user's top interests (based on a set of categories) over the past three weeks, then shares them with participating sites. The blog post describes it this way:
With Topics, your browser determines a handful of topics, like "Fitness" or "Travel & Transportation," that represent your top interests for that week based on your browsing history. Topics are kept for only three weeks and old topics are deleted. Topics are selected entirely on your device without involving any external servers, including Google servers. When you visit a participating site, Topics picks just three topics, one topic from each of the past three weeks, to share with the site and its advertising partners. Topics enables browsers to give you meaningful transparency and control over this data, and in Chrome, we're building user controls that let you see the topics, remove any you don't like or disable the feature completely.
The Topics "are thoughtfully curated to exclude sensitive
categories, such as gender or race
". Meanwhile, the mapping of
sites to Topics will be done in the browser as the GitHub site describes:
The topics will be inferred by the browser. The browser will leverage a classifier model to map site hostnames to topics. The classifier weights will be public, perhaps built by an external partner, and will improve over time. It may make sense for sites to provide their own topics (e.g., via meta tags, headers, or JavaScript) but that remains an open question discussed later.
Advertisers (and others) can request information via a JavaScript call to
document.browsingTopics(), which will return zero to three Topic IDs,
one for each of the previous three weeks, in a random order. The top five
Topics for a given week are collected and one random Topic chosen from the
full list is added in; one of those six Topics will be chosen for the week.
In addition, Topics are tracked in a somewhat
complicated scheme to try to "prevent the direct
dissemination of user information to more parties than the technology that
the API is replacing (third-party cookies)
". Said scheme restricts
sending Topics to callers that have already called the Topics API for the user on another site
that shares a Topic ID with the site in question. So browsers can only
send a Topic ID if the advertiser has asked for Topics from a
related site (i.e. one that shares the Topic). The GitHub site has a
lengthy example to show how it all works.
The blog post shows a mockup of the interface for the browser that will allow users to view the Topics associated with them and to delete any that they do not wish to share. Users would need to do so regularly, though. The strategic use of Incognito Mode would also prevent those Topics from being added into the tracking, since browsing in that mode is not visible to the Chrome Topic-handling code.
Sites can opt-out of the Topic gathering by way of a HTTP header returned with their pages. Sites that do not want to participate can add the following header:
Permissions-Policy: browsing-topics=()
To its credit, Google will also be honoring the opt-out header value
(interest-cohort=()) that was available for FLoC, so sites that
have already made that change (e.g. LWN.net) do not need to do anything
further. The same complaints raised about this header for FLoC, with
regard to web frameworks and content-management
systems that do not provide ways to add this header, are still relevant, however.
Both FLoC and Topics are part of Google's Privacy Sandbox project. The FLoC experiment came to an end back in July; Topics is in the public discussion phase and has not been implemented in any browser at this point. While Google clearly hopes that other browser makers follow along, it is not clear that they will. Users do not seem to be clamoring for "relevant ads" (somehow defined); that feature is seen as somewhere between "creepy" and "annoying" (or both at once) by many. The Privacy Sandbox Topics site—another detailed, but less technical, description than the GitHub site—has a somewhat different take, naturally:
Interest-based advertising (IBA) is a form of personalized advertising in which an ad is selected for a user based on their interests, inferred from the sites they've recently visited. This is different from contextual advertising, which aims to match content on the page the user is visiting.IBA can help advertisers to reach potential customers and help fund websites that cannot otherwise easily monetize visits to their site purely via contextual advertising. IBA can also supplement contextual information for the current page to help find an appropriate advertisement for the visitor.
But one of the more annoying aspects of targeted ads, those based on Google searches, are not really impacted by this change, it would seem. There is no easy way for fleeting searches, or those that resulted in a purchase that is not likely to be repeated anytime soon—or ever—to be removed from the information that Google provides its advertisers. Incognito Mode can help there, too, but the user has to remember to switch. While it is sometimes comical to see Google ads recommending the book you just purchased, or the hotel/flight/rental car you already reserved, it hardly seems like it leads to increased sales for the advertisers.
Overall, Topics is thought-out quite a bit better than its predecessor, but it still suffers from privacy concerns. Part of the problem is that some users do not want to see ads for unrelated interests when they visit a site—or they don't really want to see ads at all. There is a balance to be struck, since running web sites that provide useful content is not free; it is not clear that Topics truly finds that (unattainable?) sweet spot, however. Meanwhile, privacy advocates and users who care about such things are unlikely to be mollified, even if the grounding of FLoC is welcome.
| Index entries for this article | |
|---|---|
| Security | Privacy |
| Security | Web browsers |