A complete, current step-by-step guide to setting up Google Tag Manager in 2026, from account creation through installing your first tag and publishing your changes live.
If you've been pasting individual tracking snippets, GA4, the Meta Pixel, conversion tags, directly into your website's code, Google Tag Manager solves the problem of that growing pile of code. It centralizes every tracking tag into one dashboard, so you can add, edit, or remove tracking without touching your site's source code each time. This guide covers setting it up as it actually works right now, from account creation through your first working tag.
Ideally, your website should only have one third-party tracking script installed directly in its code: the Google Tag Manager container snippet itself. Every other tag, GA4, the Meta Pixel, conversion tracking, gets configured inside GTM's dashboard instead, and GTM handles firing each one according to rules you set, without requiring a new code deployment every time you want to add or adjust tracking.
Go to tagmanager.google.com and sign in with a Google account, ideally the same business account used for your other tracking tools. Click "Create Account" in the top right. Enter an account name, typically your business name, since this is the top-level organizational label you'll see every time you log in. Select your country.
Within the same setup flow, you'll create a container, the actual bucket that holds all your tags, triggers, and variables for a specific website. Enter a container name, using your website's top-level domain (for example, www.yoursite.com) is the standard convention, since it makes identifying the right container obvious later if you manage multiple sites. Under Target Platform, select Web unless you're specifically setting up tracking for a mobile app. Click Create and accept the Terms of Service.
You only need one container per website, not one per page. If your business manages more than one website, create an additional container from the Accounts tab rather than trying to combine tracking for separate sites into a single container.
After creating your container, GTM generates two separate code snippets. The first goes in your website's head section, as close to the top as possible. The second goes immediately after the opening body tag. Both snippets need to be installed for GTM to function correctly, they're not interchangeable or optional alternatives to each other.
On platforms with a native head-code field, Webflow, Shopify, WordPress page builders, paste the head snippet into that field. The body snippet typically needs to go into a custom code area specifically supporting body-level placement, or directly into your site's template if you have that level of access. If you're not comfortable editing this directly, this is a reasonable moment to hand the two snippets to whoever manages your website.
Before configuring any actual tags, confirm the container itself is installed correctly. In GTM, click Preview in the top right. This opens a new tab prompting you to enter your website's URL. Enter it and click Connect. You'll be redirected to your actual site, and a GTM debug console should appear at the bottom or side of the browser window, confirming the container is successfully connected and communicating with your site.
With the container confirmed working, add your first real tag, most commonly GA4 or the Meta Pixel, both of which were covered in earlier guides in this series. In the Workspace tab, click Tags, then New. Choose the appropriate tag type, select or create the trigger that determines when it fires (commonly "All Pages" for a base tracking tag), and save.
Use Preview mode again after adding a new tag to confirm it fires correctly before making it live. Once confirmed, click Submit in the top right of the GTM interface, add a version name and description describing what changed, and click Publish. Changes inside GTM don't go live on your actual website until this publish step is completed, previewing and testing happens in a safe, non-public state first.
Everything above describes a standard web container, which covers the vast majority of small business tracking needs. A more advanced option, a server-side container, routes tracking data through your own server rather than directly through the browser, which can improve data accuracy and help bypass ad blockers, but it requires additional cloud infrastructure setup and is worth considering only once your tracking needs have outgrown a standard web container's capabilities.
Yes, ideally. Running the same tag both directly in your site's code and through GTM causes duplicate tracking and inflates your numbers. Once a tag is confirmed working correctly through GTM, remove the original hardcoded version from your site.
Account creation, container setup, and installing the two code snippets typically takes 15 to 20 minutes and requires no coding experience. Configuring additional tags beyond the basics takes longer depending on how many tracking tools you're consolidating into the container.
Yes, the standard web container is free with no usage limits for typical small business tracking needs. Server-side containers may involve hosting costs for the cloud infrastructure required to run them, depending on your provider.
With your full tracking stack centralized in GTM, the next step for ecommerce brands is making sure your products are actually visible where customers shop, starting with TikTok Pixel setup. This connects to our earlier guides on the Meta Pixel and Facebook Conversions API. If you'd rather have your full tracking stack set up and verified by someone who does this daily, that's exactly what our paid media team handles as part of a free Growth Gap Analysis.
How We Work
