{"id":21752,"date":"2023-10-06T19:15:14","date_gmt":"2023-10-06T15:15:14","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/21752\/"},"modified":"2023-10-06T19:15:16","modified_gmt":"2023-10-06T15:15:16","slug":"google-privacy-sandbox-and-ad-topics-explained","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/21752\/","title":{"rendered":"What Google Ad Topics is, and how to disable it"},"content":{"rendered":"<p>Within a year, Google plans to stop supporting so-called <em><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-block-cookies-in-chrome-safari-firefox-edge\/43505\/\" target=\"_blank\" rel=\"noopener nofollow\">third-party cookies<\/a><\/em>, a technology that advertisers have used for decades to track users, in its Chrome browser.<\/p>\n<p>But this doesn\u2019t mean such tracking will simply stop. It would be odd if the tech giant, whose revenue comes mostly from online advertising, voluntarily gave up the ability to collect user data. Instead, third-party cookies will be replaced by a new technology \u2014 Google Ad Topics. In fact, Google Ad Topics is already here: the company <a href=\"https:\/\/www.theverge.com\/23860050\/chrome-ads-topics-sandbox\" target=\"_blank\" rel=\"nofollow noopener\">integrated it into the Chrome browser<\/a> this summer and recently started to <a href=\"https:\/\/9to5google.com\/2023\/08\/01\/android-ads-privacy\/\" target=\"_blank\" rel=\"nofollow noopener\">roll it out to the Android operating system<\/a>.<\/p>\n<p>In this post, we explore how Ad Topics works, where to disable it in the Chrome and Android settings, and <a href=\"https:\/\/www.kaspersky.com\/blog\/web-beacons-explained-and-how-to-stop-them\/47281\/\" target=\"_blank\" rel=\"noopener nofollow\">what else you can do to avoid being tracked<\/a> by online advertisers.\n<\/p>\n<h2>A little history: Google Privacy Sandbox and FLoC<\/h2>\n<p>\nLet\u2019s first go back a bit to Google Privacy Sandbox. This is what Google calls the entire initiative to abandon third-party cookies and replace them with different technologies for targeted advertising. Google first started <a href=\"https:\/\/blog.google\/products\/chrome\/building-a-more-private-web\/\" target=\"_blank\" rel=\"nofollow noopener\">talking<\/a> about this initiative back in August 2019. As you can see, it\u2019s taken them four years to develop specific solutions for phasing out cookies.<\/p>\n<p>The purpose of this initiative is, on the one hand, to get rid of technology that\u2019s widely perceived as a violation of privacy. On the other hand, Google wants to find a way to continue showing personalized ads to users \u2014 maintaining the competitive advantage that made it an internet giant.<\/p>\n<p>If you look at the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Privacy_Sandbox\" target=\"_blank\" rel=\"nofollow noopener\">Wikipedia article on Privacy Sandbox<\/a>, you\u2019ll find a long list of candidate technologies that Google planned to use to move away from third-party cookies. However, in 2021, a technology called Google FLoC emerged as the primary candidate. Let\u2019s discuss it in more detail.\n<\/p>\n<h2>What is Google FLoC?<\/h2>\n<p>\nFLoC (Federated Learning of Cohorts) was a technology proposed by Google aimed at changing the approach to targeted online advertising \u2014 making it more private. Instead of using individual user behavior data to personalize ads, FLoC grouped users with similar interests \u2014 meaning similar browsing histories \u2014 into \u201ccohorts\u201d. These cohorts were then assigned a unique identifier, which advertisers can use to target their ads.<\/p>\n<p>One of the key advantages in terms of user privacy was that FLoC didn\u2019t send user activity information to Google servers, but processed the data locally \u2014 directly on the user\u2019s device.<\/p>\n<p>It\u2019s worth noting that, despite the name, FLoC didn\u2019t actually use <em>federated learning<\/em>. <a href=\"https:\/\/github.com\/patcg-individual-drafts\/topics#evolution-from-floc\" target=\"_blank\" rel=\"nofollow noopener\">Its use was initially planned<\/a>, but it turned out that local computing was good enough.\n<\/p>\n<blockquote><p>What is federated learning? It\u2019s a variant of machine learning \u2014 an alternative to the centralized learning approach. In centralized learning, data from all devices is uploaded to a central server where the AI model is trained. In federated learning, data isn\u2019t sent to a central server; instead, local models are trained on local data directly on the devices. These devices then exchange the training results, rather than the user data itself, with the server. Based on the results of this local training, a global AI model is built \u2014 thus, the local AI models and the global AI model mutually train each other. This is all done to eliminate the need for centralized storage of user data.<\/p><\/blockquote>\n<p>\nAs is often the case with attempts to have one\u2019s cake and eat it too, the technology was criticized from both sides. Despite Google\u2019s claims that FLoC is 95% as effective as third-party cookies, advertisers <a href=\"https:\/\/www.adexchanger.com\/online-advertising\/the-industry-reacts-to-googles-bold-claim-that-flocs-are-95-as-effective-as-cookies\/\" target=\"_blank\" rel=\"nofollow noopener\">weren\u2019t satisfied<\/a> with the technology\u2019s performance.<\/p>\n<p>Privacy advocates, in turn, were <a href=\"https:\/\/www.eff.org\/deeplinks\/2021\/03\/google-testing-its-controversial-new-ad-targeting-tech-millions-browsers-heres\" target=\"_blank\" rel=\"nofollow noopener\">extremely unhappy<\/a> that FLoC didn\u2019t adequately address user privacy concerns \u2014 and also that millions of Chrome users were included in the testing of FLoC without their consent. However, the main privacy concern regarding Google FLoC was its highly precise methods for categorizing users \u2014 the possible number of cohorts exceeded 30,000 \u2014 which allowed too much scope for user tracking.<\/p>\n<p>A significant portion of the internet industry quickly took up arms against Google FLoC, including all Chromium-based browser developers \u2014 which refused to include FLoC in their products, and Amazon \u2014 which disabled FLoC on all its websites. Consequently, just a few months after the testing of FLoC began, Google decided to freeze the project. Already by early 2022, they officially announced the abandonment of FLoC in favor of another technology \u2014 Topics API.\n<\/p>\n<h2>What is Google Ad Topics (Topics API)<\/h2>\n<p>\nGoogle Ad Topics (also known as Topics API) is a technology that Google is currently planning to use to replace third-party cookies for targeted advertising. Ad Topics functions somewhat similarly to FLoC: it also relies on browser history (in the case of Chrome) or app usage (in the case of Android), through which a locally operating algorithm tries to identify user interests.<\/p>\n<p>However, there are significant differences: while FLoC grouped users with similar interests into cohorts with unique identifiers, Topics API only compiles a list of things that interest the user \u2014 that is, \u201ctopics\u201d.<\/p>\n<p>At the time of writing this article, there were 629 such topics, but this <a href=\"https:\/\/github.com\/patcg-individual-drafts\/topics\/blob\/main\/taxonomy_v2.md\" target=\"_blank\" rel=\"nofollow noopener\">list<\/a> is constantly being updated, so the number will continue to grow. In Google Ad Topics, each webpage on the internet is associated with a certain topic. The algorithm <a href=\"https:\/\/blog.google\/products\/chrome\/get-know-new-topics-api-privacy-sandbox\/\" target=\"_blank\" rel=\"nofollow noopener\">constantly updates<\/a> the list of Google topics <em>assigned to the user<\/em> based on what they\u2019ve visited recently. Here\u2019s how it works:\n<\/p>\n<ul>\n<li>Every week, the user is assigned five topics based on the sites they visited the most that week.<\/li>\n<li>Three lists of five topics each are created for the last three weeks.<\/li>\n<li>A site that wants to show ads to the user requests the topics assigned to that user from Topics API. The algorithm randomly selects one topic from each of the three lists and provides the site with these three topics for displaying targeted ads.<\/li>\n<li>The topics assigned to the user are stored for only three weeks. Older topics are deleted, and a list of five new topics is generated every week.<\/li>\n<\/ul>\n<p>\nSince there is an element of randomness in the selection of topics, it seems that identifying a specific user or even a narrow group of users from such information is not so easy. Nevertheless, even soft and gentle tracking is still tracking, and targeted advertising is not to everyone\u2019s taste. The good news is that Google allows you to not only manually configure Ad Topics but also to disable them altogether. For the sake of your privacy, we recommend doing this.\n<\/p>\n<h2>How to disable Google Ad Topics in the Chrome Browser<\/h2>\n<p>\nTo disable Google Ad Topics data collection <a href=\"https:\/\/support.google.com\/chrome\/answer\/13355898\" target=\"_blank\" rel=\"nofollow noopener\">in the Chrome settings<\/a>, go to <em>Settings \u2192 Privacy and security \u2192 Ad privacy<\/em>. The main point of interest on this tab is the first option, <em>Ad topics<\/em>. Click on this option and turn off the switch in the window that opens.<\/p>\n<div id=\"attachment_49162\" style=\"width: 1930px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191419\/google-ad-topics-explainer-1-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-49162\" class=\"size-full wp-image-49162\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191419\/google-ad-topics-explainer-1-EN.jpg\" alt=\"How to disable Google Ad Topics in the Chrome browser\" width=\"1920\" height=\"1120\"><\/a><p id=\"caption-attachment-49162\" class=\"wp-caption-text\">Where to disable Google Ad Topics in the Android settings<\/p><\/div>\n<p>Alternatively, you can go directly to the Google Ad Topics settings by entering the following path in the Chrome address bar:<\/p>\n<p><code>chrome:\/\/settings\/adPrivacy\/interests<\/code><\/p>\n<p>While you\u2019re in this part of the browser settings, it doesn\u2019t hurt to disable two other options on the <em>Ad privacy<\/em> tab: <em>Site-suggested ads<\/em> and <em>Ad measurement<\/em>. That\u2019s it! You\u2019ve successfully disabled Google Ad Topics in the Chrome browser.\n<\/p>\n<blockquote><p>\n<strong>Note!<\/strong> Chrome settings are specific to each user profile. So, if you use Chrome with multiple Google accounts on the same computer, you\u2019ll need to disable Ad Topics for each account separately. Go through all your Chrome profiles and repeat the steps above.<\/p><\/blockquote>\n<h2>How to disable Google Ad Topics in the Android operating system<\/h2>\n<p>\nDisabling Google Ad Topics in the Android operating system must be done directly in your smartphone\u2019s settings. To do this, go to <em>Settings \u2192 Google \u2192 Ads \u2192 Ads privacy \u2192 Ad topics<\/em> and turn off the switch in the window that appears.<\/p>\n<div id=\"attachment_49163\" style=\"width: 1930px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191433\/google-ad-topics-explainer-2-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-49163\" class=\"size-full wp-image-49163\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191433\/google-ad-topics-explainer-2-EN.jpg\" alt=\"How to disable Google Ad Topics in the Android settings\" width=\"1920\" height=\"977\"><\/a><p id=\"caption-attachment-49163\" class=\"wp-caption-text\">Where to disable Google Ad Topics in the Android settings<\/p><\/div>\n<p>Again, since you\u2019re already adjusting the privacy settings, go back to <em>Settings \u2192 Google \u2192 Ads \u2192 Ads privacy<\/em> and also disable <em>App-suggested ads<\/em> and <em>Ad measurement<\/em>. Now, go one step back to <em>Settings \u2192 Google \u2192 Ads<\/em> and click on <em>Delete advertising ID<\/em>.<\/p>\n<p>Please note that this guide is for the standard version of Android. Depending on the manufacturer, smartphone model, and firmware version, the names of settings and paths might vary slightly. If you can\u2019t find them following these instructions, try using the search in the Android settings.\n<\/p>\n<blockquote><p>\n<strong>Note! <\/strong>If you disable Google Ad Topics on Android and then receive a notification about \u201cnew ad privacy features\u201d, Google Ad Topics might be re-enabled automatically. If that happens, it\u2019s best to go to your smartphone settings and make sure it\u2019s turned off.<\/p><\/blockquote>\n<h2>How to opt out of personalized ads in the Google Account settings<\/h2>\n<p>\nStill with adjusting your privacy and ad settings, there\u2019s one more thing worth doing: disable personalized ads for your Google account.<\/p>\n<p>To do this, go to the Google\u2019s <a href=\"https:\/\/myadcenter.google.com\/\" target=\"_blank\" rel=\"nofollow noopener\">My Ad Center<\/a> page. If you haven\u2019t disabled personalized Google ads yet, this page will be covered with colorful category and brand tiles. You can hang around here for a long time, choosing what kind of advertising you want to see.<\/p>\n<div id=\"attachment_49164\" style=\"width: 1930px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191452\/google-ad-topics-explainer-3-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-49164\" class=\"size-full wp-image-49164\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191452\/google-ad-topics-explainer-3-EN.jpg\" alt=\"Google My Ad Centre, where you can manage ad personalization\" width=\"1920\" height=\"1200\"><\/a><p id=\"caption-attachment-49164\" class=\"wp-caption-text\">Google My Ad Center, where you can manage ad personalization<\/p><\/div>\n<p>But don\u2019t let the pretty advertising distract you \u2014 rather than choosing anything here, it\u2019s best to just turn it all off. What you\u2019re looking for here is a shy little switch at the top right of the page labeled <em>Personalized ads<\/em> \u2014 switch it to <em>Off<\/em>.<\/p>\n<div id=\"attachment_49165\" style=\"width: 1930px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191506\/google-ad-topics-explainer-4-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-49165\" class=\"size-full wp-image-49165\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2023\/10\/06191506\/google-ad-topics-explainer-4-EN.jpg\" alt=\"How to disable personalized ads in Google My Ad Centre\" width=\"1920\" height=\"1200\"><\/a><p id=\"caption-attachment-49165\" class=\"wp-caption-text\">How to disable personalized ads in Google My Ad Center<\/p><\/div>\n<blockquote><p>\n<strong>Note!<\/strong> This setting is also specific to each Google account. Therefore, if you use multiple accounts, you need to disable personalized ads separately for each of them.<\/p><\/blockquote>\n<p>\nAll set? Congratulations! You\u2019ve now used all the available settings that help you avoid unnecessary attention from both Google and advertisers.\n<\/p>\n<h2>More privacy<\/h2>\n<p>\nBut why limit yourself to the anti-tracking options Google provides in the settings of its products and services? It\u2019s a good idea to use additional methods of combating data collection. In particular, we recommend the <em>Private Browsing<\/em> feature available in all our paid subscriptions \u2014 <a href=\"https:\/\/me-en.kaspersky.com\/standard?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kstand___\" target=\"_blank\" rel=\"noopener\">Kaspersky Standard<\/a>, <a href=\"https:\/\/me-en.kaspersky.com\/plus?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kplus___\" target=\"_blank\" rel=\"noopener\">Kaspersky Plus<\/a>, and <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a>.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>We explore what Google Ad Topics is, how it functions, and how to disable it. Along the way, we discuss the related topics of Google FLoC, Privacy Sandbox, and the demise of third-party cookies.<\/p>\n","protected":false},"author":2726,"featured_media":21754,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1225,9],"tags":[2088,1172,105,1636,16,404,22,43,783],"class_list":{"0":"post-21752","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-tips","9":"tag-tips","10":"tag-advertising","11":"tag-android","12":"tag-browsers","13":"tag-chrome","14":"tag-cookies","15":"tag-google","16":"tag-privacy","17":"tag-tracking"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/21752\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/google-privacy-sandbox-and-ad-topics-explained\/26319\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/28996\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/google-privacy-sandbox-and-ad-topics-explained\/26602\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/26742\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/google-privacy-sandbox-and-ad-topics-explained\/29237\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/google-privacy-sandbox-and-ad-topics-explained\/28089\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/google-privacy-sandbox-and-ad-topics-explained\/36216\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/google-privacy-sandbox-and-ad-topics-explained\/11777\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/google-privacy-sandbox-and-ad-topics-explained\/49154\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/google-privacy-sandbox-and-ad-topics-explained\/21076\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/google-privacy-sandbox-and-ad-topics-explained\/21860\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/google-privacy-sandbox-and-ad-topics-explained\/30592\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/google-privacy-sandbox-and-ad-topics-explained\/34923\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/google-privacy-sandbox-and-ad-topics-explained\/26896\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/google-privacy-sandbox-and-ad-topics-explained\/32605\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/google-privacy-sandbox-and-ad-topics-explained\/32260\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/google\/","name":"google"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=21752"}],"version-history":[{"count":1,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21752\/revisions"}],"predecessor-version":[{"id":21753,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21752\/revisions\/21753"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/21754"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=21752"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=21752"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=21752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}