Google Tag Manager: tracking without touching your code

Google Tag Manager (GTM) is a free Google tool that lets you manage tracking codes and scripts on your website without editing your site's code every time. Think GA4, the Meta pixel, the LinkedIn Insight Tag, Microsoft Clarity or Google Ads conversion tracking. You add one snippet to your site once, and from then on you manage everything in GTM: adding, adjusting or switching off measurements without needing a developer each time.

What Google Tag Manager does

GTM works with three building blocks you'll keep running into, however complex the setup gets:

A tag without a trigger does nothing, and a trigger without a tag doesn't either: they belong together. Variables are set up separately and reused across multiple tags and triggers, so you don't reinvent the wheel for every measurement.

Everything you set up lives in a container: one per website (or app). Changes only go live once you click Submit and Publish, and every version is saved automatically with a version number. If something breaks after publishing, you roll back to a previous version in one click. That makes GTM relatively safe to experiment in: you can tinker in the test environment without visitors noticing anything.

How GTM gets onto your site

You get two code snippets: one for the <head> of your site and one right after the opening <body> tag. Most CMS platforms make this simple:

• WordPress: a plugin such as "GTM4WP" or manually in the theme files, often also via a header/footer plugin.
• Shopify: via the theme.liquid files, or with a ready-made app from the Shopify App Store.
• WooCommerce: usually the same WordPress route as above.
• Webflow: a dedicated field in project settings for custom code in head and body.
• Custom-built sites: your developer pastes the snippets into the templates loaded on every page.

Important: place the code on every page, including thank-you pages after a form submission or order. Miss those and you miss your conversion tracking too.

What to measure (the essentials)

The question isn't "what can I measure", but "which actions tell me something about my business". In practice that usually comes down to:

1. Enquiries and forms: submitted, not just viewed. A visitor scrolling to your contact page hasn't done anything yet; someone clicking "submit" has.
2. Clicks on phone, email and WhatsApp. For local businesses and service providers especially, this is often the most important conversion, and it usually isn't measured without GTM.
3. Purchases with order value for web shops. This requires a data layer: a piece of information your website sends along (for example the contents of a shopping cart) so GTM knows which amount and products belong to a purchase. Shopify and WooCommerce have ready-made apps and plugins for this, so you don't need to write code yourself.
4. Key clicks: quote button, pricing page, whitepaper or brochure download.
5. Scroll and video, but only if you actually act on the data. Scroll tracking looks nice but rarely leads to a decision.

Web shop example: a clothing store uses GTM to measure not just "purchase completed" but also "product added to cart" and "checkout started". Placing those three steps side by side in GA4 shows exactly where people drop off: adding items, filling in details, or paying.

B2B service provider example: a consultancy measures form submissions per enquiry type (quote, information, call-back request) as separate events, so sales knows what kind of lead just came in before picking up the phone.

Local business example: an installation company measures phone clicks separately per page (service page versus homepage), making it visible which pages actually generate callers, not just visitors.

Don't measure everything you can. Five measurements you check every month beat fifty nobody opens. See also vanity metrics: numbers that look nice but lead nowhere.

Client-side and server-side

By default GTM runs in your visitor's browser (client-side): tags are loaded and fired by code running on their screen. That's the most common and simplest setup, and fine for most SME sites.

There's also server-side tagging: data first goes to a server you control (for example via Google Cloud or a specialised service like Stape), and from there to Google, Meta and other platforms. Your visitor's browser then only talks to your own domain, not directly to dozens of external servers.

Server-side advantages:

• More stable measurement, because ad blockers and browser restrictions (such as Safari's Intelligent Tracking Prevention) have less grip on traffic that runs through your own domain.
• A slightly faster site, since fewer external scripts need to load in the browser.
• More control over exactly which data you send to which platform.

Downsides:

• It costs money: you pay for server space or a service like Stape.
• It requires more technical knowledge to set up and maintain than standard GTM.

Important to remember: server-side tagging is not a way around consent. GDPR applies to data running through your server just as much as to data going straight from the browser. Consider server-side only once you have a well-working client-side setup and are running into concrete problems such as ad blockers significantly lowering your reported conversions.

GTM and Consent Mode

With GDPR enforcement tightening and Google Consent Mode v2 required for anyone measuring Google Ads conversions, GTM plays a central role here. Your cookie banner sends a signal to GTM about what a visitor does and doesn't allow (analytics cookies, advertising cookies), and GTM makes sure tags respect that: some only fire after consent, others (like basic cookieless measurement) may sometimes fire regardless.

Most cookie banner providers (such as Complianz or CookieYes) have ready-made integrations with GTM via Consent Mode. Building it yourself is also possible, but requires precision: a misconfigured trigger can make tags fire without consent, or never fire even though consent was given.

Common mistakes

• Double tracking. GA4 loads via both the CMS and GTM, doubling every visit. Always check this with Tag Assistant.
• Tags that always fire, even on test or staging environments, polluting your data with your own visits and test submissions.
• No naming convention. A container full of tags called "Tag 7" and "Tag 12" becomes unmanageable within months, especially with several people working in it.
• Publishing without testing. Preview mode takes two minutes and prevents a broken measurement running for a week.
• Forgetting consent. Tags firing before consent is given are a legal risk and also produce unreliable data.
• Nobody manages access. A former employee or agency still has publishing rights on your container.

What it works together with

GTM rarely operates on its own. Typical combinations:

• GA4 to analyse what you measure with GTM.
• Looker Studio to report those measurements clearly.
• Google Ads and Meta Ads to pass conversions along so the ad algorithms can optimise more effectively.
• Cookie banners (Complianz, CookieYes, Cookiebot) for consent.
• CRM systems such as HubSpot, where form data ends up after a GTM connection.

What to watch

• One container per site, and no double tracking. Loading GA4 via your CMS and via GTM doubles your numbers.
• Limit permissions. Who can publish? Give agencies and freelancers access via their own account, not your password.
• Naming. "GA4 – Event – Enquiry submitted" instead of "Tag 14". You'll thank yourself in a year.
• Consent first. Without a correct Consent Mode setup you either measure too much (legal risk) or too little (bad data).
• Speed. Every tag costs load time. Regularly remove old pixels from campaigns that ended long ago.
• Document what you measure and why, for example in a simple measurement plan a new colleague can also follow.

When you don't need GTM (yet)

If you run a simple brochure site without forms, a web shop or ads, your CMS's built-in GA4 integration may be enough. GTM adds the most value once you have more than one tracking code, make changes regularly, or want to capture specific events (clicks, purchases, scrolling) that aren't measured by default. If you're just starting out and don't yet know what you want to measure, write down which actions matter for your business first, before building a container full of tags.

How to get started

1. Create an account and container at tagmanager.google.com.
2. Add the two snippets to every page (or use your CMS integration).
3. Set up your cookie banner and Consent Mode.
4. Add your GA4 tag and test in Preview.
5. Build your first conversions: enquiry, phone click, purchase.
6. Publish, and check a day later in GA4 and Google Ads that the numbers make sense.

Alternatives

Within the Google ecosystem, GTM is the standard. Alternatives include Tealium and Adobe Launch (mainly for large organisations with more complex data needs) and the built-in tracking integrations of platforms like Shopify. For most SME sites GTM is the logical choice: free, well documented and every specialist knows it, so you're never tied to one person or agency.

Frequently asked questions about Google Tag Manager

Is Google Tag Manager free?

Yes, the standard version is free. You only pay for the server with server-side tagging, and large organisations can opt for paid Tag Manager 360.

What's the difference between Google Tag Manager and Google Analytics?

Google Analytics (GA4) collects and shows your data. Tag Manager is the tool that decides which data goes to GA4 and other tools, and when.

Do I need a developer for GTM?

For the basics usually not. For a proper data layer in a web shop, server-side tagging or complex forms, often yes.

Does Google Tag Manager slow down my site?

GTM itself is light. The tags you put in it cost load time. Keep it tidy and clean up regularly.

Can I use GTM under GDPR?

Yes, as long as tags only fire after consent where required. Use a cookie banner with Consent Mode v2.

Can GTM also measure A/B tests or experiments?

Yes, GTM can link variables and triggers to experimentation tools, but for genuine A/B testing you'd usually use a dedicated tool for that, with GTM measuring the results.

What happens if I remove GTM from my site?

All tags running through GTM stop immediately, including GA4, ad pixels and conversion tracking. If you're building something new, test it in parallel first before removing the old setup.

How long before new measurements show data?

As soon as you publish, GTM measures immediately. GA4 often shows the first data within a few hours, but allow a day for reliable numbers in reports.

Further reading

Want to know more about measurement? Read measuring online marketing, KPIs and Looker Studio for reporting. Want someone to look at your tracking with you? Book a free strategy session.