Category: GTM

Google Tag Manager — implementation, tag management, triggers, templates, security and troubleshooting. Hands-on guides and technical deep dives.

  • GTM Performance Audit: 33 KB Container vs. 95 KB Facebook Pixel

    ,

    GTM gets blamed for slow sites. But GTM is just the messenger — the real culprits are the scripts you load through it. Here’s which ones cause the damage, and how to measure it with Chrome DevTools. Website speed = business Site speed stopped being a technical concern the moment Google built it into ranking.…

    GTM page speed impact — small container vs. large third-party scripts in a lab
  • GTM vs. CSP — How to Make Tracking and Security Coexist

    , ,

    A developer deploys Content Security Policy on the company website — and tracking silently breaks. Or the reverse: an analyst adds a tag to Google Tag Manager (GTM) and pushes through a CSP exception — measurement works, but the site is wide open. GTM is inherently a script injector — it loads third-party scripts into…

    GTM vs. Content Security Policy — schéma konfliktu mezi trackingem a bezpečností
  • How to Break a Website Using Google Tag Manager

    , ,

    Google Tag Manager runs on over 30 million websites. It’s one of the most widely used tools for managing tracking and marketing scripts. Marketers love it — you can add a tag in 2 minutes, no developer needed, no deploy required. But GTM is essentially a script injector with a graphical interface. What does that…

  • dataLayer and recursive merge

    ,

    dataLayer is a simple JavaScript array. Push an object, read it in a Google Tag Manager (GTM) variable, done. Nothing complicated about that. Right. If you’re designing dataLayer structures and haven’t heard of recursive merge yet, consider whether you want to keep reading. You’ll sleep worse. dataLayer vs. GTM data model — not the same…

    dataLayer recursive merge — vizualizace přepisování dat
  • Who reads the forms on your website? (And do you know about it?)

    , , , ,

    Imagine the following situation. A visitor comes to your website, fills out an order form—name, email, phone number—and submits it. The data goes to your CRM or database. But it’s quite possible that the same data — hashed, but still identifiable — is also being sent to the servers of Google, Meta, TikTok, Pinterest, and…

    Reklamní pixely čtou formuláře na webu — ilustrace