This guide is for small business owners, bloggers and WordPress site managers who keep hearing that they “should be using Google Tag Manager” and want a clear, ordered walkthrough. It covers creating the account and container, installing the container code, adding the Google tag for Google Analytics 4 (GA4), testing in Preview mode, and publishing. It also covers the question many guides skip: whether you need Tag Manager at all.
What Tag Manager does, and what it does not
Google Tag Manager (GTM) is a container for your tracking tags. You put one snippet of code on the site, and from then on you add, change and remove tags inside the Tag Manager interface instead of editing your theme or pasting code into plugins. Tags only go live when you publish a version, so there is a built-in step for testing and a history you can roll back.
GTM does not collect analytics data by itself. It delivers tags, such as the Google tag that sends data to GA4. That is why the two products are often confused: GA4 is where you read reports, GTM is how you deploy the code that feeds it.
Step 1: Create the account and container
According to the Tag Manager Help Center, the setup runs like this:
- Go to tagmanager.google.com and sign in with your Google Account.
- Open the Accounts tab and select Create Account.
- Under Account Setup, enter an account name and choose the country. Sharing data anonymously for benchmarking is optional.
- Under Container Setup, enter a container name. For a website, Google suggests using the top-most URL, such as www.example.com. You do not need a container for each page.
- Choose the container type. Web is the one for a website or web app; the other types are iOS, Android, AMP and Server.
- Click Create and agree to the Terms of Service.
Think of the account as the top level for your business and each website as its own container. An agency managing several clients would normally keep each client’s site in a separate container.
Step 2: Install the container snippet
To find the code, open your container, go to the Workspace tab and select the container ID (it starts with “GTM”). The Install Google Tag Manager dialog shows two code blocks:
- Head snippet: placed as high in the
<head>as possible, directly after the opening tag. - Body snippet: placed immediately after the opening
<body>tag. It holds a<noscript>fallback.
Both need to appear on every page. Google’s install page also notes that sites built on platforms such as WordPress, Shopify or Wix can set up the Google tag through an integration instead of editing each page, but it gives no WordPress-specific steps for the container itself. On WordPress, that usually means one of two routes: a Tag Manager plugin that has fields for the head and body snippets, or a small addition to a child theme. Which plugin to use is your call; the official page does not recommend one, so check any plugin’s reviews and update history first, and keep a backup (see our guide to automatic off-site WordPress backups) before touching theme files.
Back in the dialog, enter your site’s URL and click Test, then OK. Do not paste the same snippet twice, for example once in a plugin and once in the theme, because that would load the container twice.
Step 3: Add the Google tag for GA4
First, get your Tag ID. In GA4, the Google Analytics help page says to go to Admin, then Data streams, click your web stream and copy the Measurement ID from the stream details (it starts with “G-“).
Then, in Tag Manager, create a tag in your workspace. The Tag Manager Help Center describes two options: the recommended route of Tag Configuration > Google Analytics > Google Analytics, or an alternative where you choose Google Tag as the tag type. Enter the ID in the Tag ID field. In the Triggering section, the page tells you to select either “Initialization – All Initialization Events” or “Some Initialization Events”, then click Save. For a normal site that wants data from every page, the all-events option is the straightforward choice.
The same page says to create a separate Google tag for each website, and that you need access to the container plus at least the Editor role on the Google Analytics account.
Be careful not to double-count. If a theme, an SEO plugin or an analytics plugin already prints a GA4 snippet, adding the tag in GTM as well can send every page view twice. Google’s GA4 help states that you should not add more than one Google tag to a page when installing it directly; the same principle applies when you move the job to Tag Manager. Remove the old snippet after the GTM version is verified.
Once the tag is working, the next job is deciding which actions count as conversions. That is covered in How to Set Up GA4 Key Events for a Small Business Site, so this guide stops at the tag itself.
Step 4: Test in Preview mode
Preview mode lets you browse your site as if the current draft were already published. Nothing changes for real visitors. The steps from the Help Center:
- Open your container and, in the Workspace tab, click Preview at the top right. Tag Assistant opens in a new tab.
- Enter your site’s URL. If the site breaks, uncheck Include debug signal in the URL.
- Click Connect. Your site opens in a new window and shows “Connected” at the bottom right.
- Return to the Tag Assistant tab and click Continue.
As you click through the site, the debug interface shows which tags fired, what triggered or blocked them and what data they sent. Check that your Google tag fired on the first page and on a second page you navigate to. To leave, click the X at the upper left of the debug interface or click Stop debugging on the Tag Assistant activation page.
For a second check on the GA4 side, the Google Analytics help notes you can browse your site and look at the Realtime report, and that data can take up to 30 minutes to appear in a new property.
Step 5: Publish a version
Tags, triggers and variables you add in a workspace stay inactive until published. To make them live:
- Click Submit at the top right.
- Choose Publish and Create Version and review the Workspace Changes section.
- Enter a version name and description that say what changed, for example which tag launched and where.
- Click Publish.
If you only want to save your work, choose Create Version instead; that records a version without making it live. To undo a bad release, open Versions, choose the earlier version’s actions menu and either publish it or use Set as Latest Version, which replaces the current draft with that version so you can edit and publish again.
Do you actually need Tag Manager?
The following is editorial judgment, not a Google requirement. Google documents installing the Google tag directly: copy the snippet that begins with the “Google tag (gtag.js)” comment and paste it right after the opening head element of each page, or use a custom HTML field if your CMS requires one. For many sites that is enough.
| Situation | Likely fit |
|---|---|
| One brochure site or blog, page views and basic events only | Google tag directly |
| Several tools to deploy (analytics, ads, other pixels) | Tag Manager |
| Marketing team needs to change tags without a developer | Tag Manager |
| Nobody will maintain a container or review its versions | Google tag directly |
A container nobody understands can be worse than no container, because stale tags keep firing. If you run paid campaigns, compare the options in Google Ads Conversion Tracking: Tag vs GA4 Import before adding more tags.
Key takeaways
- Tag Manager deploys tags; GA4 reports on the data. You need both only if you want that extra layer.
- One Web container per site, with the head and body snippets on every page.
- Add the Google tag with your G- Tag ID and an initialization trigger, then test with Preview.
- Nothing goes live until you click Submit and publish; name every version clearly.
- A simple site that only needs basic GA4 can reasonably use the Google tag alone.
FAQ
Is Google Tag Manager free?
Google’s setup help pages do not cover pricing, so check the Tag Manager product page for current terms. The help pages do mention a separate enterprise tier, Tag Manager 360, in the context of approval workflows.
Can I use Tag Manager and a GA4 plugin together?
Only if they do not both send the same page views. Pick one method for the GA4 tag and remove the other to avoid duplicate data.
Why does my site break when I use Preview?
The Help Center advises unchecking Include debug signal in the URL in Tag Assistant if the site breaks while connecting.
Can I undo a published change?
Yes. From the Versions screen you can publish an earlier version or set it as the latest version to replace the current draft.
Sources
- Tag Manager Help: Create an account and container
- Tag Manager Help: Install a web container
- Tag Manager Help: Set up the Google tag in Tag Manager
- Tag Manager Help: Preview and debug containers
- Tag Manager Help: Publish a container version
- Google Analytics Help: Set up the Google tag
- Google Analytics Help: Set up your web data stream