|
|
|
|
|
|
by EMM_386
1836 days ago
|
|
|
> There is a caveat regarding FLoC blocking on Whole Foods pages, however. While other Amazon-owned domains mentioned here that block FLoC do so using Google’s recommended approach involving sending a response header from HTML pages, Whole Foods blocking employs a tactic that sends an opt-out header from Amazon analytics requests. What do they mean here, that the actual page request does not send the "no FLoC" HTTP header but the requests from Analytics do? What happens in this scenario? |
|
|
So they might be trialing it this way because of that, to help boost their ad platform and hinder floc , so that google cannot drop third party cookies that easily , as floc’s on browser processing makes google the defacto judge on what information do they add into floc identifiers and what they do not , meanwhile themselves getting all the unrestricted data from their browsers separately.
By hindering mass scale adoption of floc , they’re trying to delay dropping of third party cookies , to slow down google from getting an advantage over them.
Atleast that’s what I think , they might be testing it for other reasons, only an Amazon exec can answer it specifically.