Google Tag Manager, the new anti-adblock weapon (2020)

Re:Google Tag Manager, the new anti-adblock weapon (2020) by gigel82 on Sunday February 20, 2022 @10:24PM (#30411633)

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.

[ Parent | on HN ]

Re:Google Tag Manager, the new anti-adblock weapon (2020) by pixeldetracking on Monday February 21, 2022 @08:00AM (#30415423)

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"

[ Parent | on HN ]

Re:Google Tag Manager, the new anti-adblock weapon (2020) by aembleton on Monday February 21, 2022 @05:21AM (#30414023)

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

[ Parent | on HN ]

Re:Google Tag Manager, the new anti-adblock weapon (2020) by thejohnconway on Monday February 21, 2022 @07:52AM (#30415340)

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

[ Parent | on HN ]

Re:Google Tag Manager, the new anti-adblock weapon (2020) by tasha0663 on Monday February 21, 2022 @08:29AM (#30415645)

> Google recommends against using Cname for this

So use Cname? :D

[ Parent | on HN ]

Re:Google Tag Manager, the new anti-adblock weapon (2020) by thejohnconway on Monday February 21, 2022 @10:19AM (#30416777)

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

[ Parent | on HN ]