Hacker News new | past | comments | ask | show | jobs | submit login

How do you identify tracking proxies though? When everything is going through the same domain you don't even know if data is being sent to Google, it's all a server-side black box.



ublock origin has actually an experimental option for this: https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#...

only issue with blocking the proxies is that you can now decide to host the container on your own infra through docker, and it's documented by Google: https://developers.google.com/tag-platform/tag-manager/serve...

I guess this is very interesting for many people, especially in Europe with the "Google Analytics ban"


By using Cname uncloaking that uBlockOrigin can do on Firefox. It should see that the real domain is Google Tag Manager.


I think the article mentions that Google recommends against using Cname for this, and using A records instead.


> Google recommends against using Cname for this

So use Cname? :D


Sites want the ads to get through, right? So they’re going to do the thing that makes that happen: A records.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: