Google Tag Manager Setup Guide: From Zero to First Tag

Google Tag Manager lets you add, update, and manage tracking tags on your website without editing code every time. One snippet on your site unlocks the ability to deploy GA4, Google Ads, Meta Pixel, and dozens of other tags — all from a browser interface. This guide walks through the complete setup from a blank account to your first published tag.

What Google Tag Manager Actually Does

GTM acts as a container — a single JavaScript snippet you install once on your site. Inside the container, you define tags (code snippets that fire), triggers (conditions that cause tags to fire), and variables (dynamic values tags can reference). When a user visits your site, GTM loads, evaluates which triggers are active, and fires the appropriate tags — all without additional code changes to your site.

The benefit is speed and independence. Your marketing team can add a Meta Pixel via GTM or update a conversion tag without waiting for a developer. Changes publish in minutes rather than days.

Step 1: Create a GTM Account and Container

Go to tagmanager.google.com and sign in with your Google account.
Click Create Account.
Enter your Account Name (your company name).
Enter your Container Name (your website domain, e.g. yourstore.com).
Set the Target platform to Web.
Click Create and accept the Terms of Service.

GTM will display two code snippets. You need both installed on every page of your site.

Step 2: Install the GTM Snippet

GTM gives you two snippets:

Snippet 1 — a <script> tag that goes as high as possible in the <head> of every page.
Snippet 2 — a <noscript> fallback that goes immediately after the opening <body> tag.

On Shopify: Go to Online Store → Themes → Edit code → theme.liquid. Paste Snippet 1 inside the <head> section and Snippet 2 directly after the opening <body> tag.

On WordPress: Use a plugin like Insert Headers and Footers or paste directly into your theme’s header.php file. Snippet 1 goes in the header, Snippet 2 goes after <body>.

On WooCommerce: Same as WordPress — add to the theme’s header.php or use a header/footer injection plugin.

After installing the snippets, verify the installation using GTM’s Preview mode (covered in Step 5).

Step 3: Understand the Core Concepts

GTM has three building blocks:

Triggers

Triggers define when a tag fires. Common trigger types:

Page View — fires when any page loads. Used for GA4 Configuration, Meta Pixel base code.
DOM Ready — fires after the HTML is parsed but before images load. Useful for elements that need the DOM to be built.
Window Loaded — fires after everything on the page has finished loading.
Click — All Elements — fires on any click. You add conditions to limit it to specific elements.
Click — Just Links — fires when a link is clicked. Automatically provides the link URL as a variable.
Form Submission — fires when a form is submitted.
Custom Event — fires when a specific event is pushed to the dataLayer from your site code.

Variables

Variables are values that tags and triggers can reference. GTM has built-in variables (Page URL, Click Text, Click ID, Form ID) and lets you define custom ones. The most important custom variable type for ecommerce is the Data Layer Variable — it reads values pushed to the dataLayer by your site, such as order value, product ID, or transaction ID.

Step 4: Add Your First Tag — GA4 Configuration

The GA4 Configuration tag loads the GA4 tracking library and sends the initial page view event. Every other GA4 tag depends on this tag being present.

In GTM, go to Tags → New.
Click Tag Configuration → Google Analytics: GA4 Configuration.
Enter your Measurement ID (found in GA4 under Admin → Data Streams → your stream → Measurement ID, format: G-XXXXXXXXXX).
Leave Send a page view event when this configuration loads checked (this is how GA4 records page views).
Under Triggering, click the + icon and select Initialization — All Pages. This trigger type ensures the GA4 library loads before any other tags try to send events.
Name the tag something clear: GA4 — Configuration.
Click Save.

Step 5: Test with Preview Mode Before Publishing

Never publish a GTM container change without testing it first in Preview mode. A broken tag can fire on every page load and corrupt your data.

In GTM, click Preview in the top right.
Enter your website URL and click Connect. A new browser tab opens with your site, and the Tag Assistant panel appears.
Navigate between pages and perform actions (clicks, form submissions).
In the Tag Assistant panel, check that your tags appear under Tags Fired and not under Tags Not Fired.
Click on the tag to see what triggered it, which variables were read, and their values.

For the GA4 Configuration tag, you should see it fire on every page view. In GA4’s DebugView (Admin → DebugView), you should see page_view events appearing in real time as you navigate.

Step 6: Publish the Container

Once testing confirms everything works, click Submit in the top right of GTM.
Choose Publish and Create Version.
Add a Version Name and Description: “GA4 Configuration — initial setup”.
Click Publish.

GTM versions every publish. If a change breaks something, you can roll back to any previous version instantly from the Versions tab — a major advantage over editing code directly on your site.

Organising Your GTM Container

As you add more tags, organisation becomes important. Recommended practices:

Use consistent naming: [Platform] — [Type] — [Description]. For example: GA4 — Event — begin_checkout, Meta Pixel — Event — Purchase.
Use folders (GTM → Tags → Folders) to group tags by platform or function.
Add notes to tags explaining what they track and when they were added — this saves confusion six months later when someone else touches the container.
Write clear version descriptions every time you publish, so you can audit what changed and when.

Common GTM Mistakes to Avoid

Publishing without testing — always use Preview mode before every publish. A tag with the wrong trigger can fire on every page and inflate event counts dramatically.
Using All Pages trigger for conversion tags — conversion tags should fire on specific triggers (a custom event, a specific page URL), not all pages. An All Pages trigger on a Google Ads Conversion tag will report every visitor as a conversion.
Multiple GA4 Configuration tags — having two GA4 Configuration tags fires the page_view event twice and doubles every metric in GA4. Check your Tags list for duplicates.
Not using a Transaction ID on purchase events — without a unique order ID, a user refreshing the order confirmation page creates duplicate conversions in both GA4 and Google Ads.
Giving too many people publish access — treat GTM Publish permission like production server access. Publish rights should be limited; Edit rights can be broader.

What to Add Next

Once your GA4 Configuration tag is live and verified, the logical next tags to add are:

GA4 purchase event tag — fires on your order confirmation page, sends revenue and transaction data to GA4.
Google Ads Conversion Tracking tag — fires on the same purchase trigger, sends conversion data to Google Ads for Smart Bidding.
Meta Pixel base code — fires on all pages, enables remarketing and event tracking for Meta campaigns.

Each of these builds on the GTM foundation you have just set up. For a complete look at server-side tracking options that sit alongside GTM, that is a separate (and more advanced) setup worth considering once your client-side tracking is solid.

Want Your GTM Setup Reviewed by an Expert?

A misconfigured GTM container can corrupt months of data before anyone notices. We offer a free 20-minute tracking audit where we check your container live and flag anything that will cause problems.

Book your free tracking audit →

Not sure where your tracking is losing you money?