3 ms·
Current GTM, configured (via the server UI) to inject tracker X: gtm javascript loads, pulls down the config, injects tracker X javascript into the browser ne
by x0x0 5y ago
Current GTM, configured (via the server UI) to inject tracker X:
gtm javascript loads, pulls down the config, injects tracker X javascript into the browser
new gtm:
gtm javascript loads, pulls down config, streams events to google servers to fan out to tracker X as configured
So blocking gtm.js off tagmanager.google.com / www.googletagmanager.com / the various other domains still blocks all gtm injected tags.
The tl;dr is they're become much closer to segment -- which does the data fanout internally to segment. But they should still be straightforward to block.
- volderette 5y agoThis is not how GTM server side works. There is not a single call to Google domains from the client, when GTM server side is set up to its fullest. The config (gtm.js) will be loaded from my subdomain and not googletagmanager.com. Also gtm.js can be renamed.
- xigoi 5y agoCouldn't you still recognize the script by its content?
- ComodoHacker 5y agoNot with dynamic obfuscation.
- shafyy 5y agoExactly, this is already done for tracking scripts, since it's commong to use proxies to load tracking scripts.
- freedomben 5y agoNo because the script contents can change from site to site. Maintaining an index for every site would get you closer, but individual sites can trivially tweak things to break fingerprinting as often as they want. Even on every request.
- x0x0 5y agoPer the docs here [1], that is not true. You continue to load gtag.js off the googletagmanager.com domain; subsequent events can flow to a custom domain. [1] https://developers.google.com/tag-platform/tag-manager/server-side/intro https://developers.google.com/tag-platform/tag-manager/serve...