Server-side setup
Your analytics data routes through your own server first, then onward to Google. The scripts still use Google's usual filename, which some ad blockers match on.
Automated checks may occasionally misread timing or extensions. Verify in DevTools for the final word.
What server-side GTM does. The container loads from a subdomain you own (brand.fulcos.com) instead of Google's domain. Measurement requests also go to that subdomain, so Google never sees the visitor's raw IP.
This setup keeps Google's usual filename (gtm.js), which some ad blockers pattern-match on — so the container may load but the GA4 library gets blocked. To fully bypass that, you need disguised script names, which is what Addingwell adds on top. Both use the same container (GTM-T3X85M).

