Table of Contents
Google FLoC (Federated Learning of Cohorts)
Google FLoC, or Federated Learning of Cohorts, was a controversial advertising technology developed by Google to replace third-party cookies. The idea behind FLoC was to group users into “cohorts” based on similar browsing behavior, enabling interest-based ad targeting without tracking individuals across the web.
However, FLoC has since been scrapped due to widespread criticism. It was replaced by the Topics API, part of Google’s broader Privacy Sandbox initiative.
What is Google FLoC?
Google FLoC was designed to preserve interest-based advertising without exposing individual user data. Instead of assigning each user a unique identifier, FLoC placed users into groups—called cohorts—based on their web activity.
Each cohort represented a group of users with similar browsing patterns, such as people who frequently visit fitness or cooking sites. Advertisers would then target cohorts, not individuals.
It was Google’s answer to increasing privacy concerns and cookie deprecation, offering an alternative tracking model that ran directly in the browser.
How Did FLoC Work?
Rather than sending browsing data to external servers, FLoC processed user history locally in the browser. The algorithm used machine learning to assign users to a cohort with similar interests. Advertisers only saw the cohort ID, not the full browsing history.
Key Elements:
- Federated Learning: This refers to training algorithms across many decentralized devices without transferring raw data to a central server.
- Cohorts: Groups of thousands of users with similar behavior.
- Cohort ID: A numeric label representing a user’s interest group, shared with advertisers.
- No Cross-Site Tracking: FLoC aimed to reduce fingerprinting risks and improve privacy.
Why Was FLoC Controversial?
Although FLoC tried to improve user privacy, it sparked backlash from multiple corners of the internet.
Major Concerns:
- Fingerprinting Risks: Even though FLoC didn’t track individuals, combining a cohort ID with other browser attributes made fingerprinting easier.
- Lack of Consent: Many users were enrolled in FLoC trials without clear consent or understanding.
- Discrimination & Profiling: Critics worried that grouping users based on behavior could lead to discriminatory targeting—similar to how credit scores or health profiles are misused.
- Pushback from Browsers and Platforms: Browsers like Firefox, Brave, Vivaldi, and Safari refused to adopt FLoC. WordPress even suggested blocking it by default.
FLoC vs Topics API
FLoC was ultimately abandoned in January 2022, replaced by the Topics API, which became the primary solution under the Privacy Sandbox umbrella.
Feature | FLoC | Topics API |
User grouping | Based on cohorts | Based on interest categories |
Browser processing | Yes | Yes |
Fingerprinting risk | High (due to cohort ID) | Lower |
Industry reception | Mostly negative | Mixed but more collaborative |
Data sharing | Cohort ID | Interest topics (e.g. “fitness”) |
Key Takeaway
Google FLoC was an ambitious yet flawed attempt to create a more privacy-conscious advertising framework. Although it moved tracking to the browser, it still exposed users to fingerprinting and lacked industry-wide adoption. Its short-lived presence reminds us that privacy solutions must prioritize consent, transparency, and control.
While the Topics API attempts to fix FLoC’s weaknesses, the bigger takeaway is this: browser-based privacy solutions are still controlled by major players like Google, leaving businesses and users to navigate trade-offs between privacy and performance.
If you want to manage browser identities, spoof behaviors, or protect session data without relying on Google’s evolving ad tech, there’s a smarter way…
👉 Try Multilogin for €1.99
Control your own browser fingerprint, manage multiple profiles, and stay stealthy with no dependency on Google’s APIs.
Your privacy. Your browser. Your rules.
People Also Ask
FLoC was designed to enable interest-based advertising without third-party cookies. It grouped users into cohorts based on browsing habits for ad targeting.
FLoC was discontinued due to privacy concerns, lack of industry support, and the risk of browser fingerprinting. It was replaced by the Topics API.
FLoC aimed to improve privacy over third-party cookies, but experts argued it still exposed users to profiling, fingerprinting, and lacked transparency.
No. Only Google Chrome supported FLoC, and most other browsers publicly rejected it.
The Topics API now replaces FLoC as a more transparent and privacy-friendly way to support interest-based advertising under the Privacy Sandbox initiative.
Related Topics
Fingerprint Spoofing
A peer-to-peer network is a distributed network structure in which peers communicate directly with each other to exchange information, resources, or services. Read more here.
Browser Isolation
Browser isolation refers to the process of executing browser code in a separate environment to protect the endpoint from threats
Canvas Graphics
Canvas graphics involve drawing and manipulating graphics within an HTML5 element. Read more.
Hardware Fingerprinting
Hardware fingerprinting is a technique used to uniquely identify a device based on its physical and software characteristics. Read more here.