Reason 1: Ad blockers

[kexej28769@nongnue]

Two of these additional implementations — one in Google Tag Manager and one on the page — run locally hosted copies of the Google Analytics JavaScript file (e.g. www.distilled.net/static/js/au3.js ) to make it harder for ad blockers to detect. I renamed the JavaScript functions ("tcap" and "Buffoon" instead of the standard "ga") and renamed the trackers ("FredTheUnblockable" and "AlbertTheImmutable") to avoid duplicate trackers (which can often cause problems).

This was originally inspired by a 2016-era best practice on how to get your Google Analytics setup past ad blockers. I can't find the original article right now, but you 2017 سے بہت ملتا جلتا مضمون دیکھ سکتے ہیں۔here .

Finally, we have ("DianaTheIndefatigable"), which has benin number data one renamed tracker, but uses the standard code in a different way and is applied to the page. This completes the set of all combinations of modified and unmodified GTM and trackers on the page.


I tested their functionality in different browser/adblock environments by looking at the page view displayed in the browser developer tools:




Ad blockers, primarily as browser extensions, have been growing in popularity for some time. This is primarily due to users seeking better performance and UX on ad-laden sites, but in recent years there has also been a greater emphasis on privacy, so analytics blocking is likely to be a possibility.