Simo Ahava

Simo Ahava is an absolute legend for anything google tag manager / google analytics related. No other site is even remotely close. https://www.simoahava.com/

Sure! :) But I think it's all just about few principles. Elaborated a bit more on them: 1. Tailwind CSS classes extracted with purge-css, all inlined. 2. Favicon inlined, small images (<4kb) inlined. Not sure what’s the best threshold. Here is all https://turboeshop.com/inlinedimages/ is all page in one requests. Meaning two big images that are https://turboeshop.com/fastestpageintheworld/ were inlined - results are way worse. So larger images - definitely excluded. 3. Gzip stuff(as one commenter below commented, not done in turboeshop.com/fastestpageintheworld/). 4. Everything from same domain and subdomain. If you want cloudinary or friends, I guess they are only allow subdomain. This is totally OKeish exemption. Or maybe there is a way to work around that cloudinary serves, Cloudflare caches. 5. JS - inlined. Cash.js maybe if you need jquery replacement, or just vanilla. Little content on vanilla js nowadays :), https://gomakethings.com/articles/ is something interesting. Don’t want to flame here, am not js expert, maybe someone can elaborate. 6. For compex components - svelte web components (or stencils or lithtml) - I’d prefer svelte but am not sure what’s best. 7. Google analytics a) - there is new google analytics (GA4) with measurement protocol2 and new server side google tag manager. Serve side gtm does two things a) serves gtag.js; b) accepts measurement protocol hits and sends to GA. Take a look how it’s done -…

> Is iCloud Private Relay theatre? https://fingerprint.com/blog/ios15-icloud-private-relay-vulnerability/ > 3rd party cookie blocking? It's very funny that you should ask this question in response to an article about fingerprinting without cookies. But yes, there are various workaround to use 1st party cookies or other storage to take the place of 3rd party cookies. Perhaps the worst is the Safari "Privacy Report", which has always been misleading: https://www.simoahava.com/privacy/intelligent-tracking-prevention-ios-…

> same requests sent to Google Analytics but with a different hostname There are instructions out there to also modify the path of the requests[1]. Consider this paragraph in the Summary section: > Cynics could say that this is an improved way to circumvent ad blockers. And they’d be right! This does make it easier to circumvent ad blockers, as their heuristics target not just the googletagmanager.com domain but also the gtm.js file and the GTM-... container ID. * * * [1] https://www.simoahava.com/analytics/custom-gtm-loader-server-side-tagg…

Btw, someone wrote up a guide on hosting this on AWS, which covers what it would take to run it yourself. https://www.simoahava.com/analytics/deploy-server-side-google-tag-mana… If I'm not mistaken, the key bit is that Google makes the docker image available at: gcr.io/cloud-tagging-10302018/gtm-cloud-image:stable Edit: oh, Google published a guide to self host maybe? https://developers.google.com/tag-platform/tag-manager/server-side/man…

you can also change the ressources names: https://www.simoahava.com/analytics/custom-gtm-loader-server-side-tagg… and you can host the container on your own infra: https://developers.google.com/tag-platform/tag-manager/server-side/man…

The thing is that you can host the server container also in AWS https://www.simoahava.com/analytics/deploy-server-side-google-tag-mana… or Azure https://www.simoahava.com/analytics/server-side-tagging-azure-app-serv…

You can actually sanity check how common it is for T.ly by triggering an analytics hit within a <noscript> tag. Looks like you're using GTM/GA on your site, so this[1] should put you on the right track. You'll still be blind to individuals that are blocking GTM/GA itself since you're not using the newer server-side GTM option, hence only a sanity check. But it's a fairly low-effort tweak to be able to get a read on how common it is for your site specifically. [1] https://www.simoahava.com/analytics/track-non-javascript-visits-google…

As someone who has wrestle with GA and GTM regularly, I think it's fair to say that the author (Simo Ahava[1]) is the preeminent authority on how they work, and his blog is generally more useful than the official documentation Google provides. 1: https://www.simoahava.com/about-simo-ahava/

Reposting my earlier comment from [0] This article is incorrect. There does not appear to be a change between Safari 13.1 and Safari 14 for how it handles GA. I have tested it myself. With Safari 13.1 Apple made a change [1] to their Intelligent Tracking Prevention that blocks all 3rd party cookies for cross site resources. The only change in Safari 14 appears to be that it reports which domains have had cookies blocked. The Google Analytics beacon is still sent by the browser. Benedict Evans (cited in article) since deleted his tweet, but this article seems not yet to have been updated. [0] https://news.ycombinator.com/item?id=23612140 [1] https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-mor… Edit: it seems the article has been updated since earlier today, and now references tweets from myself and Simo. The article title is still very misleading. Edit 2: Simo has now written up a post with more details: https://www.simoahava.com/analytics/no-safari-does-not-block-google-an…