Definition · Tracking
What is Google Tag Manager?
Google Tag Manager (GTM) is a free orchestration layer for every tracking tag on your site. This page covers what it actually does, the difference between the web container and the server-side container, and when each is the right call for an Australian operator doing $2M to $20M.
In one paragraph
GTM is a tag-management system. You install one container snippet on your site, and from then on every new tracking tag is added, edited, or removed inside the GTM dashboard without touching site code.
The two flavours
Web container
Browser-side
Tags fire from the user's browser. Easy to set up. Subject to ad-blockers, Safari ITP, and slow-connection drops.
Server-side container
Your domain
Tags fire from a server you control (tag.yourdomain.com). Bypasses ad-blockers, attaches first-party data, full control over what each platform receives.
Setup, in sequence
How we get Google Tag Manager into a defensible state.
Six steps we work in order on every engagement that touches GTM. Each one is non-optional. Skipping any of them is what creates the misconfigured GTM containers we audit later.
Step 01
Audit what you currently have
Inventory every existing tag in your GTM container, every event in GA4, and every conversion in Meta and Google Ads. Most operators we audit have 30 to 80 tags, of which 20 to 40 percent are stale, broken, or duplicated.
Step 02
Define the events that matter for the business
Not 'add to cart, view product, scroll 50 percent.' Just the events that map to revenue: lead created, qualified lead, purchase, refund. The other events are noise unless someone is actually using them in a model.
Step 03
Standardise event IDs and parameters
Every conversion event needs a stable event ID generated server-side and passed to both the browser pixel and the server-side platform. This is the foundation of deduplication and the first thing that breaks without it.
Step 04
Configure consent classification
Marketing consent vs analytics consent vs necessary. Server-side calls need to be classified correctly; most banners get this wrong out of the box. A two-week consent audit usually lifts opt-in rate by 5 to 15 percentage points by removing dark patterns and adding transparency.
Step 05
Move high-value tags server-side
Meta CAPI, Google Ads enhanced conversions, GA4 measurement, offline conversion uploads. Each one runs through the server container, gets first-party data attached, and is deduplicated via the event ID. Browser-only versions stay in place during cutover.
Step 06
Reconcile against the CRM monthly
Build a Looker Studio (or equivalent) view that ties platform-reported revenue to bank-anchored CRM revenue. The monthly gap is what tells you whether the tracking is holding. If it widens by more than five percentage points in a month, something has broken silently and is worth investigating before the next campaign decision.
Frequently asked
Seven questions about Google Tag Manager.
What is Google Tag Manager (GTM)?
Google Tag Manager is a free tool from Google for adding, editing, and removing tracking tags on your website without changing the site's code each time. A 'tag' is a snippet that fires when something happens (page view, form submit, button click) and reports the event to a destination like GA4, Meta, Google Ads, or your own database.
Is Google Tag Manager free?
Yes. The web container (the standard GTM most operators use) is free with no usage limits that affect typical businesses. The server-side container is also free as a piece of software, but you pay for the cloud hosting it runs on (Stape from $7 per month, Google Cloud Run usage-based, typically $50 to $200 per month for $2M to $20M-band traffic).
What is the difference between GTM web container and server-side GTM?
The web container fires tags from the browser. The server-side container fires tags from your own server (a subdomain you control like tag.yourdomain.com). Server-side bypasses ad-blockers and Safari ITP, lets you attach first-party data, and gives you full control over what data each platform receives. It is the modern replacement for browser-only tracking.
Do I need GTM if I have GA4 already?
Almost always yes. GA4 can be installed directly without GTM, but the moment you want to fire any other tag (Meta CAPI, Google Ads conversions, LinkedIn Insight Tag, TikTok Pixel, custom events) GTM is the orchestration layer that keeps it manageable. Without GTM, every new tag is a code deploy.
When should I move from browser-side GTM to server-side GTM?
When monthly ad spend crosses roughly $40K AUD and your reports have stopped reconciling with the CRM. Below that, the rebuild cost outweighs the recovery; above $80K it is an obvious yes. We have written a full piece on this question: see the server-side GTM guide.
Is Google Tag Manager safe and compliant under Australian privacy law?
GTM itself is compliant. The compliance question is what you do with it. Properly configured with a current privacy policy, classified consent rules, and disclosed third-party transfers, GTM (web or server-side) meets the Privacy Act 1988 and the Australian Privacy Principles. The OAIC has been pushing harder on consent and breach notification since 2023, so the privacy-policy review is part of any rebuild we do.
What does GTM not do?
GTM is not a CDP, not an analytics platform, and not an attribution model. It is the plumbing that gets event data to the platforms that do those things. People sometimes try to use GTM as a substitute for proper data warehousing or for an ad-platform itself; both are mistakes.
Related
Continue the thread.
Long-form
Server-side GTM in Australia: when it is worth it
The economics of moving to server-side at $40K+ monthly spend.
Read in full
Reference
Attribution glossary
20 plain-language definitions of the tracking vocabulary.
Service
Tracking audit
Two weeks. Read-only access. Written report. Prioritised fix list.