News for hackers. Stuff that matters.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by losteric on Sunday February 20, 2022 @09:06PM (#30411171)
Citing adblock feels like clickbait. Google Tag Manager can't run ads so I don't follow the comparison. Marketing analytics could always side-step anti-adblocking tools through server-side tracking.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by coffeefirst on Sunday February 20, 2022 @09:57PM (#30411474)
Right. Everything in the article is wrong.

GTM is still GTM and can be trivially blocked; the container itself isn't moving server-side.

It's just gained the ability to proxy data to third parties instead of needing to load scripts for every tracker. This is better for performance, and should be explicitly in control of exactly what data is passed on to where.

All you really lose is the ability to block a subset of analytics scripts selectively.

Re:Google Tag Manager, the new anti-adblock weapon (2020) by probotect0r on Sunday February 20, 2022 @11:32PM (#30412002)
How are you going to block it "trivially" if you don't know which script to block? They recommend changing the name of the GTM script, and paired with changing the content slightly, you won't be able to tell which script is GTM and which is actually important to the functioning of the site.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by c0balt on Monday February 21, 2022 @04:39AM (#30413707)
+It's gonna be very hard to detect once they actually bundle up (which I suspect only a few will do) the tag manager and obfuscate
Re:Google Tag Manager, the new anti-adblock weapon (2020) by dlubarov on Monday February 21, 2022 @04:17PM (#30420735)
Where does Google recommend changing the name of the script? The author claims that they do, but their link just recommends self-hosting the script. In Google's recommended JS, the path is exactly the same, only the hostname is different ("www.googletagmanager.com" replaced with "<DOMAIN NAME>").

Self-hosting by itself might make blocking marginally more difficult, but there are other reasons to do it:

- Browsers these days segment caches by origin, so there's no caching benefit to using Google as a CDN.

- With HTTP2, a first-party request is likely to immediately go through an existing (multiplexed) connection, saving a handshake.

- It's arguably better for privacy, as users and legislators seem to be concerned about links to Google leaking IPs (https://news.ycombinator.com/item?id=30135264).

Re:Google Tag Manager, the new anti-adblock weapon (2020) by gizzlon on Monday February 21, 2022 @02:48AM (#30412994)
If it's 99.99% the same I think we will manage :)
Re:Google Tag Manager, the new anti-adblock weapon (2020) by coffeefirst on Monday February 21, 2022 @12:35PM (#30418376)
This was my exact thought when I wrote that comment. Then I remembered Manifest v3.

ITP, ETP, and plugins that can block requests based on heuristics will make pretty short work of this. In Chrome, come Manifest v3, plugins won't be allowed to.

So... this is all uglier and more complicated than I thought.

Re:Google Tag Manager, the new anti-adblock weapon (2020) by jacquesm on Monday February 21, 2022 @02:26AM (#30412851)
You'll know that after loading the first couple of bytes though.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by _flux on Monday February 21, 2022 @04:57AM (#30413835)
So they need to change the first couple bytes then, automatically.

Essentially I don't understand how possibly could free adblocking lists defeat advertisers or trackers if they truly cared about them: simply have a system running with the latest adblock lists against their test site, and if it is able to filter them, have an engineer make a modification—or have the system automatically pull up a pre-made modification or even generate a new one. In addition, the content-driving JS and the site JS could be bundled in one and obfuscated.

Best functioning filters are secret ones and thus only the technically minded minority has access to them.

Re:Google Tag Manager, the new anti-adblock weapon (2020) by iamacyborg on Monday February 21, 2022 @02:19AM (#30412797)
> GTM is still GTM and can be trivially blocked; the container itself isn't moving server-side.

Not when the script sending data to the server side GTM is a first party one.

Re:Google Tag Manager, the new anti-adblock weapon (2020) by matt_heimer on Sunday February 20, 2022 @11:17PM (#30411935)
Adblockers block ads and tracking, if the new gtag manager makes easier to defeat the tracking protections of an ad blocker then it seems accurate.

I think the key thing here is that ad/tracking blockers often rely on domains or requests being 3rd party. In the past it was more work to hide the 3rd party trackers as 1st party, this makes it easy so its more likely to happen now.

Re:Google Tag Manager, the new anti-adblock weapon (2020) by fay59 on Sunday February 20, 2022 @11:13PM (#30411915)
Saying that Adblock users want it 100% to block ads and 0% to protect their privacy is a misleadingly narrow analysis, even this use isn’t completely effective.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by sodality2 on Sunday February 20, 2022 @09:41PM (#30411385)
Server side tracking based on what, server access logs? That's not particularly helpful compared to the info you get with clientside analytics libraries.
Re:Google Tag Manager, the new anti-adblock weapon (2020) by matt_heimer on Sunday February 20, 2022 @11:03PM (#30411854)
No, the gtag in the browser sends all the data to the server-side proxy. Then on the server-side config you can pick which parts of the data to share with 3rd parties. So there is still client side data capture, its just reduced to one component capturing the data.