New ask Hacker News story: Ask HN: Why do sites do tracking on the client side?
Ask HN: Why do sites do tracking on the client side?
3 by aabbcc1241 | 1 comments on Hacker News.
It is a common pattern to send user behavior data from the client (web/app) to the 3rd party trackers. This attempt can be blocked by the client, e.g. by browser extension or DNS filtering (like pihole or nextdns). Why don't the websites track users from the server instead? Because it's "eaasier" for the site owner to just drop-in the google analytic/whatever 3rd tracker script in the head, then setting up the server to proxy the submission? I may understand why the sites don't do analytics on their own (because it's easier to just hand to the 3rd party provider, and the site owner may not be programmer at all). However I don't see why they prefer to do the tracking from the client side.
3 by aabbcc1241 | 1 comments on Hacker News.
It is a common pattern to send user behavior data from the client (web/app) to the 3rd party trackers. This attempt can be blocked by the client, e.g. by browser extension or DNS filtering (like pihole or nextdns). Why don't the websites track users from the server instead? Because it's "eaasier" for the site owner to just drop-in the google analytic/whatever 3rd tracker script in the head, then setting up the server to proxy the submission? I may understand why the sites don't do analytics on their own (because it's easier to just hand to the 3rd party provider, and the site owner may not be programmer at all). However I don't see why they prefer to do the tracking from the client side.
Comments
Post a Comment