On this page
What Tag Manager is, and what it is not
Tag Manager is a separate product from Google Analytics. It does not measure anything by itself. It is a delivery layer: it loads the tags that do the measuring, such as the Google tag for GA4 and Google Ads, the Meta pixel, or the LinkedIn Insight Tag.
So is it a tracker? Only in the sense that it fires the trackers you put in it. If you never add a tag, it collects nothing. The reason to use it is control: marketers can ship tracking changes in minutes without a developer release, and every change is versioned.
It earns its place once you have more than two or three tags, or when ad platforms keep asking for new events. For a site with one analytics tag and no ads, the plain snippet is fine.
A rule of thumb for deciding: if you have changed a tracking tag more than twice in a year, or you wait on a developer for each one, put it in Tag Manager. If you have not and will not, leave it alone.
Create the container and install the snippet
Sign in to Tag Manager with a Google account, create an account for your business, then create a container. Choose the Web target platform for a site. Name the container after the site it will live on, and use one container per site.
Tag Manager then shows two code blocks. The first goes as high in the head of every page as you can get it. The second goes right after the opening body tag, as a fallback for browsers with scripts off. WordPress, Shopify, Wix and most builders have a field or an official integration for this, which is safer than editing theme files by hand.
Put the snippet on every page, including the checkout and thank-you pages. A snippet that is missing on the page where the sale happens is the most common reason conversions go unreported. If you track across a payment page on another host, see server-side tracking for the cleaner setup.
Is your tracking counting every conversion?
Runs tracking health checks on your pixels and tags. Sends a weekly performance review.
Test in Preview, then publish
Click Preview, enter your site, and Tag Manager opens a debug session that lists every tag that fired and every tag that did not on each interaction. Click through the real path a customer takes. Submit the form. Go through checkout in a test mode if your store allows it.
Check three things: the tag fired on the right action, it fired once and not twice, and the values it carries are right. A purchase event with an empty value is worse than no event, because it trains the ad platform on a zero.
When it is clean, Submit, give the version a name and a one-line description, and Publish. If something breaks later, open the Versions list and publish the previous one.
Consent and privacy settings
Tag Manager does not decide whether a tag may run. That is a consent question, and where the law or your policy requires consent, tags must wait for it. Most sites handle this with a consent banner connected to Tag Manager, and Google’s consent mode lets tags adjust what they collect based on the visitor’s choice.
Set it up before you add many tags. For each tag, check its consent settings, and make sure the banner’s default state is the cautious one for the regions you serve. Test with consent denied and with consent granted, using Preview, and confirm the tags behave differently.
Also review who can see what. Variables can capture form field values, and a careless one can send an email address or a name to an analytics tool that should never receive it. Keep personal data out of tag payloads unless you have a clear need and a lawful basis.
Mistakes, access and removal
The usual failures are duplicate tags (the same event hard-coded on the site and again in Tag Manager), triggers that are too broad, no consent handling where the law requires it, and a container with ten people who have publish rights. Give most people Read or Edit and keep Publish to one or two.
To get into a container you do not own, ask the owner to add your Google account under the account’s user management. To remove Tag Manager, delete the two snippets from your site first, then delete the container in its settings. Doing it in the other order leaves a page calling a container that no longer exists.
Sprites reads your Google Ads and GA4 data and can run a tracking health check on a schedule, so you hear when a tag stops reporting. It proposes fixes as approval cards. You still own the container.
Questions
Is Google Tag Manager part of Google Analytics?
No. They are two separate products that work together. Tag Manager loads the tag, and Analytics receives and reports the data. You can use either without the other.
Is Google Tag Manager a tracker?
On its own it tracks nothing. It is a container that fires the tags you add. Whatever those tags collect is what gets tracked, so the privacy impact is the tags’ impact.
Is Google Tag Manager worth it?
Yes once you run several tags or ad platforms. You get versioning, a preview mode and no developer queue for each change. For one analytics tag on a small site, it adds little.
How do I get rid of Google Tag Manager?
Remove both snippets from your site and confirm the pages no longer load the container. Then delete the container from its settings. Remove the snippets first so no page is left calling a deleted container.
How do I stop Google Tag Manager from tracking me?
As a visitor, a browser with tracking protection or a content blocker will stop most tags from loading. As the site owner, use consent settings so tags fire only after a visitor agrees where that is required.