8 ms·
It's a logical place to start given the X-Client-Data backdoor to DoubleClick and Google properties, which is fundamentally anti-competitive in the ad space by
by 0xy 6y ago
It's a logical place to start given the X-Client-Data backdoor to DoubleClick and Google properties, which is fundamentally anti-competitive in the ad space by giving DoubleClick access to data that other ad networks are unable to obtain and making it literally impossible for Chrome users to opt out of (and not disclosing the DoubleClick relationship).
Then there's the constant stream of new web APIs which are used almost exclusively for tracking purposes by ad networks including Google properties. For an example of that, look at the AudioContext APIs which leak audio latency information (regularly used to fingerprint users) and are available to websites with no opt-in, no notice and are accessible even if you never use audio on the page. Practically all of the modern web APIs spearheaded by Chrome offer yet another tracking data-point that is abused primarily by ad networks including their own.
- cpeterso 6y agoHere's more information about the X-Client-Data header Chrome includes in every HTTP request sent to Google domains: https://9to5google.com/2020/02/06/google-chrome-x-client-data-tracking/ https://9to5google.com/2020/02/06/google-chrome-x-client-dat... Your X-Client-Data ID is not reset when you clear your browsing data. You need to launch Chrome with a special command line parameter to reset it.