Google Tag Manager for Google Ads: what your container needs

Google Tag Manager (GTM) is the free tool that lets you steer your entire tracking from one interface, instead of touching your website’s code for every pixel and every conversion event. If you run Google Ads it’s more than convenience: your container decides whether Google optimises on real conversion data or guesses blind. This article covers both — what GTM is and why it’s worth it, and the six building blocks your container needs for Google Ads.

1. What is Google Tag Manager — and why is it worth it?

Google Tag Manager is a free tag management system from Google. You install one small container snippet in your website once; after that you manage every tracking code centrally in the GTM interface, without touching the site again.

Three terms are enough to understand the system:

Tags — the actual tracking codes: GA4, Google Ads conversion, Meta pixel, LinkedIn Insight Tag.
Triggers — the rule for when a tag fires: page view, click on a button, submitted form.
Variables — dynamic values a tag carries with it: conversion ID, clicked URL, order value.

Why GTM beats tags in the source code

Sure, you could paste every tracking code straight into the website. But GTM solves four problems that catch up with you sooner or later on that path:

An interface instead of code changes. New conversion event, new pixel, changed conversion ID — in GTM you click it together and publish. No developer, no deployment, no “we’ll do that next sprint”.
Version history. Every publish is stored as a version. You can see who changed what and when, so tracking changes stop being the black box nobody can explain three months later.
Rollback. If nothing fires after a change (or everything fires twice), one click restores the last working version. With tags in the source code, the same mistake means code archaeology under time pressure.
Workspaces. Several changes can be prepared and tested in parallel in separate workspaces without overwriting each other — relevant as soon as more than one person, or an agency, works on the container.

One thing to be clear about: GTM tracks nothing by itself. An empty container on the website is an empty toolbox on the building site. What belongs in it is what we’ll cover now.

2. The six building blocks every GTM container with Google Ads needs

If you’re running Google Ads, the container isn’t a place for creativity — the base is always the same. The first three points are mandatory for every account; the last three depend on your business model, budget and market.

Conversion Linker

The most inconspicuous tag in the container, and one of the most important. The Conversion Linker stores the click information from your ads (the GCLID parameter, among others) in first-party cookies on your own domain. Without it, Google Ads can no longer attribute a lot of conversions to the ad click — especially as browsers keep cutting back third-party cookies. Setup: one tag, trigger “all pages”, done. There’s no reason to leave it out.

An analytics tool — usually GA4

Google Ads shows you what a click costs. What happens on the website afterwards, it doesn’t show. That’s what an analytics tool in the container is for, in most cases GA4: which pages people visit, where they drop off, which campaigns bring visitors who stay. On top of that, GA4 is the foundation for audiences and a second data source you can sanity-check your Google Ads numbers against.

Your main conversion events

The core of the whole thing: events for the actions that turn a visitor into a lead. My standard trio for lead gen websites:

Lead form submitted — the obvious conversion, triggered cleanly on a successful submit, not on a mere button click.
Phone number copied — anyone who selects and copies your number intends to call.
Email address copied — same pattern: plenty of prospects never click a mailto link, they copy the address and write to you from their own mail client.

Those two copy events are the point almost every standard setup forgets. Measure form submits only and you make part of your real enquiries invisible — and Google then optimises on an incomplete picture.

Call tracking — when calls are a real channel

If a noticeable share of your enquiries come in by phone, “phone number copied” stops being enough as a signal at some point: you want to know which campaign triggered the call and whether it turned into a conversation. That’s what call tracking is for, from Google’s own call conversions through to dynamic number insertion. How to set it up and when it starts to pay off, in detail: call tracking: measuring calls as conversions in Google Ads.

Server-side tracking — from a certain budget upwards

In the classic setup every tag fires in the visitor’s browser, and that’s where ad blockers and browser protections block a share of the signals. Server-side tracking puts your own server in between: the data runs through your domain, more robustly and with more control. It costs setup and ongoing operation, so it’s not a day-one topic — it gets interesting from a certain ad budget upwards, when every percentage point of data quality is real money. The trade-off and the setup: server-side tracking: when it’s worth it and how it works.

If your audience sits in the EU, California or Brazil, there’s no way around Consent Mode v2: Google requires the consent signals as soon as you want to use features like remarketing and personalised advertising. GTM passes your cookie banner’s consent status to every Google tag — with consent it measures normally, without consent modelling takes over. Set up wrongly or not at all means remarketing lists don’t fill and conversion data goes missing. The step-by-step guide: setting up Consent Mode v2.

3. The fastest route to a clean container

You don’t have to build all of this tag by tag yourself. For the common setups I’ve documented ready-made container templates with instructions — import, enter your IDs, test:

GTM template: the lead gen container — the standard for service businesses: Conversion Linker, GA4, form and copy events in one import.
GTM template: WordPress + GA4 — the base for WordPress sites.
GTM template: Shopify conversion tracking — for the e-commerce setup with order values.
GTM template: Finsweet Consent Mode v2 for Webflow — cookie banner and Consent Mode v2 on Webflow sites.

Faster still is the GTM configurator: you click your container together — conversion IDs, events, consent settings — and get a finished JSON file to import straight into GTM. Free, no signup. The configurator lives on my German site: GTM container configurator (in German). The JSON it produces is language-neutral.

One honest note to close this step: importing isn’t the same as working. After every import, check in GTM preview mode that the tags really fire — and that the conversions arrive in Google Ads. For a quick outside check of your site there’s my free tracking check: Tracking-Check (in German).

The bottom line

Google Tag Manager is the control room of your tracking: install it once, then steer everything from the interface — with version history, rollback and workspaces instead of risky code changes. For Google Ads:

Mandatory in every container: Conversion Linker, GA4, your main conversion events — form submitted, phone number copied, email copied.
Depending on the business: call tracking when calls matter; server-side tracking from a certain budget upwards.
Audience in the EU, California or Brazil: Consent Mode v2 is a given, not an option.
Templates and the GTM configurator save you the manual build — you still have to test.

Not sure your GTM container is set up cleanly? Write to me and I’ll go through the container, the conversion events and the consent setup with you — honestly, no sales show.