I’m a webmaster that refuses to use third-party assets, cookies, and tracking of any kind. When Instagram got caught inserting JavaScript in its webviews I added HTML to shoot it down. When FLoC was introduced I added HTTP headers effectively disabling it on my websites.
Does the new Topics API have a similar solution for us web developers? I’d hate to simply block the entire Chrome User-Agent because I know many of my visitors are using Chrome.
I don’t know what type of website you manage where you would even consider blocking chrome, that’s unfortunately roughly 65% of traffic, 70% if you include edge.
Maybe your site is for a niche group of people who mostly Firefox users? I’m just very surprised that’s an option for you as unfortunately chrome is what most people use.
—-
Anyway It looks like you can add headers in your server response to opt out of the calculation.
https://developer.chrome.com/docs/privacy-sandbox/topics/#site-opt-out
I realistically can’t block Chrome users unfortunately. It’s a small business so it’s nothing super fancy.
Looks a lot like the FLoC stuff, easy enough to add. Thanks!