3 ms·
That's a pretty bold claim to make. If third-party scripts or images are still being requested, then what prevents a site- and/or page-specific identifier from
by Pacabel 13y ago
That's a pretty bold claim to make.
If third-party scripts or images are still being requested, then what prevents a site- and/or page-specific identifier from being included in the URLs of those assets? And what then prevents those site IDs, page IDs, the IP address you used to make the requests, your user agent's User-Agent string, the Referer header values, and other identifying information from being collected and stored? What prevents them from them from then tying this information together in a way that tracks you and your browsing behavior?
Keep in mind that cookies of any type are not at all necessary for such tracking to occur. The only way to truly avoid that kind of tracking is to not make any such requests in the first place.
- lmkg 13y agoI work in web analytics. Recently, one of our clients decided that they wanted to track visitors across multiple domains. After much hemming and hawing, and research proposals, and industry comparisons, the ultimate solution that was decided upon was... third-party cookies. The change is extremely simple, and the data loss from people who block third-party cookies is like 5%. So what prevents sites from deploying these technologies? Economics. To your point, there are no insolvable technical barriers. But right now the marginal return return on these technologies in no way stacks up to the marginal effort required to deploy them. Considering the fraction of the population that even knows what a cookie even is, I do not anticipate this changing in the near future. If everyone starts blocking third-party cookies, then yes we'll see an uptick in use, but I don't see that happening this decade.