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?
11–20 of 249 posts
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?
If Firefox had larger market share, Chrome wouldn’t have been able to make this opt out for websites rather than opt in because it would have given them a bad public image. I don’t think it’s fair that some company gets to force every website maintainer (most aren’t extremely technical and just use Wordpress or something similar) on earth to muddle through documentation for their particular setups to 1) learn it exis…
We blocked FLoC at my company because we couldn’t see the benefit in allowing it. If, in the future, an obvious value shows itself, then we’ll re-evaluate. But at the moment there’s only a business and reputational cost to allowing Google to harvest our users’ data.
We blocked FLoC at my company because we couldn’t see the benefit in allowing it. If, in the future, an obvious value shows itself, then we’ll re-evaluate. But at the moment there’s only a business and reputational cost to allowing Google to harvest our users’ data.
How do you block it?
We blocked FLoC at my company because we couldn’t see the benefit in allowing it. If, in the future, an obvious value shows itself, then we’ll re-evaluate. But at the moment there’s only a business and reputational cost to allowing Google to harvest our users’ data.
How do you block it?
https://paramdeo.com/blog/opting-your-website-out-of-googles...
We blocked FLoC at my company because we couldn’t see the benefit in allowing it. If, in the future, an obvious value shows itself, then we’ll re-evaluate. But at the moment there’s only a business and reputational cost to allowing Google to harvest our users’ data.
How do you block it?
Personally I don't see depersonalized targeting as a bad thing. Better than advertising dish washers to people who just bought a dish washer or some such nonsense.
We blocked FLoC at my company because we couldn’t see the benefit in allowing it. If, in the future, an obvious value shows itself, then we’ll re-evaluate. But at the moment there’s only a business and reputational cost to allowing Google to harvest our users’ data.
How do you block it?
Permissions-Policy: interest-cohort=()
Source: https://www.drupal.org/project/drupal/issues/3209628
I'm curious, with third-party cookies being fased out, and alternatives like FLoC being met with resistance, could this drastically cut the size of Google's revenue's down? If the ads can no longer be accurately targeted, I imagine that would mean the main value of AdWords is no more, and that's the foundation that entire company is built on.
Products that target based on actual user intent benefit from cookie blocks, as that cannot be meaningfully blocked ever. (i.e., when you search for "brunch" ads relating to brunch show up)
Products that target based on behavior away from the product will suffer - but morally I'm ok with that.
Google happens to own one of the most intentful products out there - you directly tell the product what you want to see! The main pain for them will be loss of targeting ability in their network ads displayed on 3rd party sites - but their first-party products I suspect will see a boost in the new world.