3 ms·
Interesting trick. But I think adBlockers block requests to entire tracking domains. So even css calls would be blocked?
by asadlionpk 9y ago
Interesting trick. But I think adBlockers block requests to entire tracking domains. So even css calls would be blocked?
- oneeyedpigeon 9y agoThat's a good point, if you're only concerned with tracking from a specific set of domains.
- AntonyGarand 9y agoNot if you're hosting your own tracking information, on your own domain
- ppeetteerr 9y agoMost trackers are built by third parties. This is true for analytics tracking and for ad tracking. Few companies ought to track their own impressions for many, many reasons.
- beckler 9y agohonestly, I don't care if you use your own tracking solution on your own domain, as long as it's not passing the data to a third-party. I get that some of that data is genuinely useful in determining what parts of an app are popular and what is not. Even though I don't like being tracked for dumb shit like ads, it does have valid uses.
- cheschire 9y agoIt’s pretty trivial to make server side calls to google analytics [0] passing lots of different data using async commands so the user doesn’t even feel the hit. Additionally you could queue these stats messages and send in bulk when your server load falls below a certain threshold. I’m not talking hours, just seconds. Like a workflow engine. 0: https://developers.google.com/analytics/solutions/experiments-server-side https://developers.google.com/analytics/solutions/experiment...
- flukus 9y agoWhy do you think it's mostly advertisers building CDN's? It's not because they really wanted to make the web faster. These are typically let through by ad blockers.