The goal of Google's “FLoC” is to reduce organizations' ability to access audience membership across different publishers.
Google's FloC proposal collects and processes web client behavior across various web sites to assign each web client to a cohort cluster. A cohort identifier, which Google calls “flock,” is short enough string (e.g., “43A7”) such that it cannot – even with other data – be used to uniquely identify a particular device. On each request the web client will send the cohort ID Google has assigned to this web client using the "Sec-CH-Flock" header.
The minimum number of people in a cohort is likely in the thousands. To ensure that a minimum number of web clients is in each cohort, the web client identifier is sent to a Google controlled server to enable distinct counting.
Marketers could measure which cohorts interact with their content, but would not know distinct reach or frequency. Marketers would also presumably be prohibited from associating particular outcomes on their web property with the cohort associated with the user's web client.
The exact information that will be accounting of this budget remains unknown.
By removing audience segmentation, marketers would be unable to perform retargeting and frequency capping. Another potential impact of removing this information is a degraded end user experience.
- How frequently does a user's cohort membership change?