This would require being to identify a user when they are on many different sites (cross-site tracking), which all the major browsers intend to prevent.
(Disclosure: I work at Google, speaking only for myself)
First, you have to understand that Google as a company has lost all credibility in much of the community. There have been too many issues like this one where Google gives you the impression they are turning off tracking... but doesn’t actually stop tracking you.
There was also the Do not Track setting, which Google ignored. So in my book (and I’m not alone here), anything coming from Google is taken with a huge grain of salt.
For some time, there has been a sort of cat and mouse game between advertisers and browser makers. Do you know Google isn’t using fingerprinting to identify us? Or just IP or some other means?
> Google as a company has lost all credibility in much of the community
What I'm saying is Safari [1], Firefox [2], and Chrome [3] are planning technical mitigations that would prevent anyone from implementing a cloud-based FLoC. Even if you don't believe Chrome, it wouldn't be possible in Safari or Firefox.
> Do you know Google isn’t using fingerprinting to identify us? Or just IP or some other means?
https://blog.google/products/ads-commerce/a-more-privacy-fir... has "once third-party cookies are phased out, we will not build alternate identifiers to track individuals as they browse across the web, nor will we use them in our products" and "our web products will be powered by privacy-preserving APIs which prevent individual tracking while still delivering results for advertisers and publishers" which seem pretty clear to me? Additionally, I work in client-side ads infra, and I'm pretty sure I would know if Google were fingerprinting users to target ads.
This would require being to identify a user when they are on many different sites (cross-site tracking), which all the major browsers intend to prevent.
(Disclosure: I work at Google, speaking only for myself)