Customer Impact

Data & Tracking

What is Google Tag Manager? How to install it and set it up properly

Copy for AI

Google Tag Manager (GTM) is a free Google tool for managing measurement codes.

Those codes are called tags. GTM lets you place them on your website without editing your site’s code every time.

The verdict: GTM is the backbone of your measurement. Set it up once with a clear plan, and every new conversion takes minutes instead of a developer sprint.

You install a container once. From then on, you add GA4, Google Ads conversions, the Meta pixel or the LinkedIn Insight Tag through a web interface.

For each tag, you decide when it fires and which data it sends.

Almost every tracking audit we run starts in the GTM container. Almost every measurement problem lives there too, such as duplicate conversions, missing leads or tags firing without consent.

This guide belongs with our overview of what website tracking is.

What exactly is Google Tag Manager?

GTM is a tag management system: one script on your site that loads all the others.

Instead of pasting ten scripts from ten platforms into your website, you place one script: the container. Everything after that, you manage in the Tag Manager interface.

How Google describes it

Google puts it this way: to use Tag Manager, you add two snippets of code to each page of your website.

After that, you set up and manage your tags through the Tag Manager website.

Three benefits

The benefit comes down to three things:

  • Speed. Measuring a new conversion or adding a pixel no longer costs a developer sprint.
  • Control. Every change gets a version. If something breaks, you roll back.
  • Consent in one place. Your cookie banner and consent signals steer all tags centrally.

Without GTM, each script would need its own consent logic. With it, one setup covers them all.

GTM versus Google Analytics: what’s the difference?

It’s the question we get most often.

GA4 is an analytics platform: it receives data, stores it and shows reports. GTM is the courier: it decides which data goes to GA4, Google Ads, Meta or LinkedIn, and when.

GTM doesn’t have reports of its own.

So you can install GA4 without GTM, with the Google tag directly in your code. And you can use GTM without GA4, for example for Google Ads conversions only.

In practice you use them together, because GTM becomes the one place where your measurement logic lives.

Google Tag ManagerGoogle Analytics 4
RoleManages and fires tagsCollects and reports data
ReportsNoneYes, plus explorations and BigQuery export
Who works in itTracking specialist, developerMarketer, analyst, management
PriceFree (360 version for enterprise)Free (360 version for enterprise)

Here’s where the data ends up. GTM sends the events, and GA4 shows them in a report like this one:

GA4 traffic acquisition report for customerimpact.be filtered on one source, the kind of report Google Tag Manager feeds with events GA4 Traffic acquisition in our own property, last 90 days, October 2026: 58 sessions from chatgpt.com. GTM delivers the data; GA4 does the reporting.

The three building blocks: tags, triggers and variables

Understand these three concepts, and you can read any container.

What each one does

  1. Tags are the actions: “send a GA4 event”, “report a Google Ads conversion”, “load the Meta pixel”.
  2. Triggers decide when a tag fires: on a page view, a button click, a form submission, or a data layer event.
  3. Variables supply the data: the URL, the text of a button, an order value or the lead type.

Rule of thumb: a tag says what, a trigger says when, a variable says with which data.

The data layer underneath

The data layer is a JavaScript object in which your website prepares structured information for GTM.

For example, event: 'generate_lead' with the form type and the value.

A setup built on the data layer is sturdier than one that’s tied to CSS classes and button labels. Those change with every redesign.

Our explanation of event tracking covers the events you really need in B2B.

Here’s the whole chain in one picture:

HOW GTM WORKS From an action on your site to data in your tools 01 Visitor acts form, click → 02 Data layer event + details → 03 Trigger + consent may the tag fire? → 04 Tags fire GA4, Ads, Meta

Installing Google Tag Manager in five steps

Create a container, place two snippets, set consent first, add your events, then test and publish.

Step 1: Create an account and a container

Go to tagmanager.google.com and create an account in your company’s name. Choose “Web” as the target platform.

Watch out: don’t create it in the name of a freelancer or agency. You’ll want to own your measurement.

Step 2: Place the two snippets

Google asks you to paste the first code block as high in the <head> as possible.

The second goes immediately after the opening <body> tag, on every page.

On WordPress, Shopify or Webflow, use the theme or an official integration. Avoid a random plugin that adds scripts of its own.

Put your cookie banner’s tag on the “Consent Initialization - All Pages” trigger. Set the default consent to denied.

How that works with Cookiebot is in our guide to Cookiebot pricing, GTM setup and Consent Mode v2. The signals themselves are explained in Consent Mode v2.

Step 4: Add the Google tag and your first events

Start with the Google tag for GA4. Then add the events that actually drive your business, the ones you’d call a lead:

  • lead form
  • demo request
  • quote request
  • phone click

Our guide to setting up GA4 conversions shows how to mark them as key events.

Step 5: Test in Preview and publish with a version name

Give every version a name that says what changed, such as “GA4 generate_lead on contact form”.

That way, you know later what you’re rolling back.

How do you set up a container that’s still readable a year from now?

With a naming convention, folders and one source of truth for conversions.

A container grows fast. After two campaigns and a redesign, it can hold 60 tags, and nobody knows which ones are still needed.

Five agreements that keep it clean

These agreements prevent that:

  • A fixed naming convention, such as GA4 - event - generate_lead, Ads - conversion - demo, Meta - Lead.
  • Folders per platform: GA4, Google Ads, Meta, LinkedIn, Consent, Utilities.
  • One source of truth for conversions. Fire Google Ads conversions from the same data layer events as GA4.
  • No hard-coded scripts next to GTM. If the Google tag also sits in your theme, you count everything twice.
  • Workspaces and a simple approval. Nobody publishes a change without a second pair of eyes.

Triggers and variables follow the same naming pattern as tags.

One source of truth means you don’t end up with two definitions of “lead”. Why the numbers still differ is in the difference between Google Ads and GA4 conversions.

Building ad platforms on the same events

For ad platforms, you build on top of the same events:

In Google Ads, the lead event becomes a conversion action. In our own account, the contact form is set as the primary one:

Google Ads conversion action settings for the GA4 contact form on customerimpact.be, set as Contacts, Primary action, fed by the same Google Tag Manager lead event as GA4 The contact form conversion action in our own Google Ads account, October 2026. It’s primary, so campaigns optimise on real enquiries.

That’s why one clean lead event in GTM matters so much: your bids depend on it. More on that in our guide to conversion tracking.

Going server-side

Want measurement that holds up against ad blockers and browser restrictions? Then a server-side container comes on top.

That’s the subject of our guide to server-side tagging. The practical side of hosting is in Stape.

The mistakes we come across most often

In containers we take over, we see the same five problems again and again.

Duplicate conversions

A form tag fires on “Form Submission” and again on the thank-you page. Google Ads sees two leads; your CRM sees one.

This is also the classic cause of “an unrealistic number of conversions” in Google Ads.

The cookie banner sits on a regular All Pages trigger instead of Consent Initialization. So the first page view goes out without a consent state.

Under the rules of the Belgian Data Protection Authority, analytics cookies aren’t strictly necessary. They therefore require prior consent.

Our free cookie scanner shows which cookies your site sets before anyone clicks.

Three smaller ones

  • Triggers on button labels. “Send” becomes “Submit” in a translation, and lead measurement goes silent.
  • Old Universal Analytics tags. They send nothing, but they slow the page and clutter the container.
  • No owner. Nobody knows who published what. Version names and a changelog solve that.

How do you check that Google Tag Manager works?

Test every change in Preview before you publish.

Click Preview in your workspace. Tag Manager then opens Google Tag Assistant in a new tab.

There you see which tags fired, on which trigger and with which data. It updates as you click through the site.

This is the debug view you’ll work in:

The checklist

Then run through this checklist:

CheckWhereWhat you want to see
Container loads on every pageTag AssistantContainer ID on home, blog, thank-you page
Consent state before the first tagTag Assistant, Consent tabDefault denied, update after a click on the banner
Lead event fires onceTag Assistant + GA4 DebugViewOne generate_lead per submission
Google Ads conversion arrivesGoogle Ads, conversion diagnosticsStatus active, no duplicate actions
Meta event arrivesMeta Events Manager, Test EventsLead event with the right parameters

Compare with your CRM after a week

If it checks out in Preview, compare the leads in GA4 and Google Ads with your CRM after a week.

Normal: a difference of a few percent, from consent and ad blockers.

Setup error: a difference of half.

Our list of common Google Analytics tracking errors helps you find the cause. To connect leads to deals, see how to set up lead tracking.

When should a specialist set up GTM?

As soon as several platforms, consent and CRM data meet in one container.

A marketer with some patience can build a basic container with GA4 and one conversion.

Where it becomes specialist work

It becomes specialist work as soon as these come into play:

  • multiple ad platforms
  • Consent Mode v2
  • a data layer with ecommerce or lead data
  • offline conversions from your CRM
  • a server-side container

That’s where small mistakes start costing money, because your bids are steered by them.

How we’ve approached it

At Kaizo: one GTM container as the central layer for GA4, Google Ads and Meta, fed by the same lead events. Read the setup in Kaizo: Google Ads conversion tracking.

At Tryve: we built conversion tracking around real enquiries.

At Suivo: lead tracking all the way into the CRM.

Not sure whether your current container’s right? With a tracking audit, we go through your GTM, consent and conversions. You get a prioritised list.

Want it built or cleaned up straight away? Our tracking specialist does it end to end. Pricing is on request, depending on your stack.

Frequently asked questions

Is Google Tag Manager free?

Yes. The standard version of Google Tag Manager is free, with no limit on the number of tags. There’s a paid 360 version within Google Marketing Platform for large organisations, with extra approval flows and support. For a server-side container you do pay for hosting, for example through Google Cloud or Stape.

Do I need GA4 if I use Google Tag Manager?

Not mandatory, but almost always advisable. GTM only sends data; it stores and reports nothing. If you want to know what happens on your site, you need an analytics tool such as GA4 or a privacy-friendly alternative such as Matomo.

Does Google Tag Manager slow down my website?

The container itself isn’t heavy. What slows things down are the tags you load into it: every chat widget, heatmap and pixel adds weight. A tidy container with only the tags you need is often faster than a site with the same scripts hard-coded.

Can I remove or block Google Tag Manager?

You can remove GTM by taking the two snippets out of your code, but then all the measurement that runs on it disappears. Visitors can block GTM with an ad blocker. That’s exactly why some companies add a server-side container on their own subdomain, as explained in our guide to Google Ads server-side tracking.

What is the difference between the Google tag (gtag.js) and GTM?

The Google tag is a single script for Google products, placed directly in your code. GTM is a management layer that loads the Google tag and tags from other platforms. Use one of the two for the same measurement, not both, or you’ll count twice.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.