{"id":44984,"date":"2022-01-25T17:51:35","date_gmt":"2022-01-25T17:51:35","guid":{"rendered":"http:\/\/eef62882-1829-49f2-a2c0-41dd8dfa4c89"},"modified":"2022-01-25T17:51:35","modified_gmt":"2022-01-25T17:51:35","slug":"google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/","title":{"rendered":"Google reveals &#8216;Topics&#8217; cookie replacement, acknowledges FLoC was problematic"},"content":{"rendered":"<div><img decoding=\"async\" src=\"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\" class=\"ff-og-image-inserted\"><\/div>\n<p>Google has provided new information on the end of the troubled development process for the FLoC (Federated Learning of Cohorts) it had hoped to use as a replacement for cookies, and it has done so as part of its reveal of another proposed replacement: Topics.&nbsp;<\/p>\n<p>The search giant&#8217;s first attempt to replace the third-party cookie with its own technology was met with&nbsp;<a href=\"https:\/\/www.zdnet.com\/article\/floc-off-vivaldi-declares-as-it-says-no-to-googles-tracking-system\/\" target=\"_blank\" rel=\"noopener\">staunch opposition from some<\/a>, a <a href=\"https:\/\/www.zdnet.com\/article\/wordpress-could-treat-google-floc-as-a-security-issue\/\" target=\"_blank\" rel=\"noopener\">wary eye from others<\/a>, and very little positive feedback. It originally committed, <a href=\"https:\/\/www.zdnet.com\/article\/google-takes-next-steps-towards-privacy-first-web-devoid-of-third-party-cookies\/\">in early 2021<\/a>, to ending third-party cookie support within its Chrome browser in 2022. At that time, Google intended for FLoC to replace cookies with a new technology which it claimed was far more anonymized and still able to yield conversion rates of 95% for every ad dollar spent.&nbsp;<\/p>\n<p>Obviously, things didn&#8217;t work out quite as the company had hoped. It eventually ended the development of FLoC in July 2021, around the same time it announced that Chrome would continue supporting third party cookies <a href=\"https:\/\/www.zdnet.com\/article\/google-delays-chromes-cookie-blocking-changes\/\">until at least mid-2023<\/a>. The company had remained cagey on how it planned to move forward with its still-extant plans to replace the cookie until now.&nbsp;<\/p>\n<p>Dubbed simply &#8220;Topics,&#8221; the new technology aims to track users anonymously using a new API designed to fulfill Google&#8217;s four main privacy goals:&nbsp;<\/p>\n<ul readability=\"1.5\">\n<li readability=\"0\">\n<p>The technology must make it &#8220;difficult to reidentify significant numbers of users across sites using just the API.&#8221;<\/p>\n<\/li>\n<li readability=\"-1\">\n<p>It should offer a viable replacement for &#8220;a subset of the capabilities of third-party cookies.&#8221;<\/p>\n<\/li>\n<li readability=\"-1\">\n<p>Any recorded data must be &#8220;less personally sensitive&#8221; than what is being collected today.&nbsp;<\/p>\n<\/li>\n<li readability=\"-1\">\n<p>The API should be understandable to users and transparent in its intentions.&nbsp;<\/p>\n<\/li>\n<\/ul>\n<p>Google apparently feels its Topics API meets all of these criteria while still providing the data interest-based ads (IBAs) need to continue operating at a level similar to their current cookie-based endeavors.&nbsp;<\/p>\n<p>In addition to posting a <a href=\"https:\/\/github.com\/jkarlin\/topics\" target=\"_blank\" rel=\"noopener noreferrer nofollow\" data-component=\"externalLink\">GitHub entry<\/a> revealing the technical details of Topics, Google&#8217;s Privacy Sandbox lead Ben Galbraith also held a press briefing in which he revealed additional parameters to several news outlets. Among them was the fact that Topics will initially attempt to track the user&#8217;s behavior across up to 300-350 specific areas of interest. These areas are based on the <a href=\"https:\/\/iabtechlab.com\/standards\/audience-taxonomy\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\" data-component=\"externalLink\">IAB Audience Taxonomy<\/a>, which contains a much more comprehensive list of 1,500 or so trackable areas of interest. &nbsp;<\/p>\n<p>Google&#8217;s GitHub post noted that this is an initial design, hinting at the fact that those 350, or so, might expand further in the future. According to Galbraith, if they do, they will not be expanding into what Google called &#8220;sensitive topics,&#8221; which includes things like the user&#8217;s race and gender.&nbsp;<\/p>\n<section class=\"sharethrough-top placeholder\"> <\/section>\n<p>In practical operation, the Topics API lets the user&#8217;s browser share three of their detected areas of interest when the user visits a site using IBAs. The API will randomly select those three from among the top five it detected. One topic will be chosen from the top five for each of the previous three weeks to give a better but still anonymized picture of the user&#8217;s recent <a href=\"https:\/\/www.zdnet.com\/article\/mozilla-research-browsing-histories-are-unique-enough-to-reliably-identify-users\/\" target=\"_blank\" rel=\"noopener\">online browsing history<\/a>. Google intends for users to be able to get personally involved with their Topics as well, noting that they will be able to disable the tracking of specific areas of interest while also being able to review what Topics have been chosen for them at any given point.&nbsp;<\/p>\n<p>This level of transparency and user control addresses two of the biggest issues Google heard about in feedback surrounding the failed FLoC proposal: that it was too opaque and added too much personalized &#8220;digital fingerprinting&#8221; data to the system. The company&#8217;s aforementioned promise to avoid &#8220;sensitive&#8221; topics likewise addresses an unfortunate tendency that FLoC had for automatically creating ad cohorts around topics like gender and race.&nbsp;<\/p>\n<p>Google plans to begin testing Topics with external parties sometime later this quarter. It remains to be seen whether this technology will fare any better than FLoC or if Google will once again be forced to continue accepting <a href=\"https:\/\/www.zdnet.com\/article\/french-regulators-fine-google-and-facebook-combined-235-million-for-cookie-tracking\/\" target=\"_blank\" rel=\"noopener\">third-party cookies<\/a> within its Chrome browser for years to come.&nbsp;<\/p>\n<p> READ MORE <a href=\"https:\/\/www.zdnet.com\/article\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#ftag=RSSbaffb68\">HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The search company&#8217;s second attempt to replace third-party cookies relies on the user&#8217;s previous three weeks of browsing history to provide what it claims is a more anonymized, transparent way of service interest-based ads.<br \/>\nREAD MORE HERE&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[62],"tags":[],"class_list":["post-44984","post","type-post","status-publish","format-standard","hentry","category-zdnet-security"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Google reveals &#039;Topics&#039; cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Google reveals &#039;Topics&#039; cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2022-01-25T17:51:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\" \/>\n<meta name=\"author\" content=\"TH Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@threatshub\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"TH Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/\"},\"author\":{\"name\":\"TH Author\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\"},\"headline\":\"Google reveals &#8216;Topics&#8217; cookie replacement, acknowledges FLoC was problematic\",\"datePublished\":\"2022-01-25T17:51:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/\"},\"wordCount\":697,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\\\/2020\\\/12\\\/17\\\/ff2b70f6-b5e0-4148-914b-eac3f134b277\\\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\",\"articleSection\":[\"ZDNet | Security\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/\",\"name\":\"Google reveals 'Topics' cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\\\/2020\\\/12\\\/17\\\/ff2b70f6-b5e0-4148-914b-eac3f134b277\\\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\",\"datePublished\":\"2022-01-25T17:51:35+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\\\/2020\\\/12\\\/17\\\/ff2b70f6-b5e0-4148-914b-eac3f134b277\\\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\",\"contentUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\\\/2020\\\/12\\\/17\\\/ff2b70f6-b5e0-4148-914b-eac3f134b277\\\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Google reveals &#8216;Topics&#8217; cookie replacement, acknowledges FLoC was problematic\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\",\"name\":\"TH Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"caption\":\"TH Author\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Google reveals 'Topics' cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/","og_locale":"en_US","og_type":"article","og_title":"Google reveals 'Topics' cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2022-01-25T17:51:35+00:00","og_image":[{"url":"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp","type":"","width":"","height":""}],"author":"TH Author","twitter_card":"summary_large_image","twitter_creator":"@threatshub","twitter_site":"@threatshub","twitter_misc":{"Written by":"TH Author","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/"},"author":{"name":"TH Author","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476"},"headline":"Google reveals &#8216;Topics&#8217; cookie replacement, acknowledges FLoC was problematic","datePublished":"2022-01-25T17:51:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/"},"wordCount":697,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#primaryimage"},"thumbnailUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp","articleSection":["ZDNet | Security"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/","url":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/","name":"Google reveals 'Topics' cookie replacement, acknowledges FLoC was problematic 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#primaryimage"},"thumbnailUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp","datePublished":"2022-01-25T17:51:35+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#primaryimage","url":"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp","contentUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/1cbb17c7b2a7bafd51ea51d5e0b001d0183d515d\/2020\/12\/17\/ff2b70f6-b5e0-4148-914b-eac3f134b277\/cookies.jpg?width=770&amp;height=578&amp;fit=crop&amp;auto=webp"},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/google-reveals-topics-cookie-replacement-acknowledges-floc-was-problematic\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Google reveals &#8216;Topics&#8217; cookie replacement, acknowledges FLoC was problematic"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476","name":"TH Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","caption":"TH Author"}}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/44984","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=44984"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/44984\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=44984"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=44984"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=44984"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}