Website monitoring · No. 05
Google Tag Manager check
In short
Google Tag Manager (GTM) is a Google tool for adding analytics and ad tags to your website — GA4, Google Ads conversions, Meta and TikTok pixels — plus conversion tracking and custom JavaScript. All of it runs through one snippet on the page: the container. If an update removes it, every tag inside stops at once, while the website looks fine.
Contents
What are Google Tag Manager and a GTM container?
Google Tag Manager (GTM) is a tool that lets marketers manage a website’s tags through a web interface instead of editing the page code every time. A tag is a snippet of code that sends visit data to another service: Google Analytics, Google Ads, Meta, TikTok, a chat widget or a CRM.
Besides ready-made tags, GTM is where you set up conversion tracking — for example, Google Ads conversion tags (Tag Manager Help) — and add your own JavaScript when you need something the built-in templates don’t offer. That’s what Custom HTML tags and Custom JavaScript variables are for (Tag Manager Help):
“The Custom HTML Tag type allows you to deploy a tag that isn’t yet supported via Tag Manager.”
All of your website’s tags live in a container. Here’s how Google defines it:
“A collection of tags, triggers, variables, and related configurations installed on a given website or mobile app is called a container.”
On the website itself, the only trace of the container is the installation code with an ID like GTM-XXXXXXX. Every time a page loads, it fetches the gtm.js file with the current container version from Google’s servers, and that file fires the right tags.
| Component | Where it lives | What it does |
|---|---|---|
| Main container code | The <head> of every page | Loads gtm.js and fires tags |
<noscript> block | Right after the opening <body> tag | A fallback for browsers with JavaScript turned off |
| Tags | Inside the container, in the GTM interface | Code for GA4, Google Ads, pixels and other services |
| Triggers | Inside the container | Conditions that fire a tag: a page view, a click, a form submission |
| Variables | Inside the container | Values that tags pass along: the page URL, the order total and so on |
Why monitor your Google Tag Manager container?
Because the container is a single point that every tag inside it depends on. Google says outright that GTM is designed to replace individual hand-coded tags:
“A Tag Manager container can replace all other manually-coded tags on a site or app, including tags from Google Ads, Google Analytics, Floodlight, and 3rd party tags.”
The flip side of that convenience: if the container code disappears, everything set up in it switches off at the same time. In practice, that means:
- Google Analytics 4 stops receiving data. Your reports show a traffic crash even though real visitors haven’t gone anywhere. The data for those days will never show up: a tag that didn’t fire didn’t send anything.
- Google Ads loses conversions. Google recommends using Google Ads conversions based on GA4 key events to optimize bids with Smart Bidding (Google Ads Help). Without conversion data, automated bid strategies are optimizing blind.
- Meta and TikTok pixels go silent. Retargeting audiences stop growing, and your ad accounts no longer see purchases or leads.
- Secondary tools break. Chat widgets, heatmaps, affiliate tracking codes — anything you connected through GTM.
Meanwhile, the website itself keeps working as usual, and visitors won’t notice a thing. The problem usually comes to light days or weeks later, when someone opens a report and sees a zero.
Why does the Google Tag Manager code disappear from pages?
Most often, it happens after website work that had nothing to do with analytics:
- A theme update or replacement. The container code was pasted by hand into a template file, and the new theme version overwrote that file.
- A disabled plugin. GTM was added through a CMS plugin, which was switched off while troubleshooting a conflict or running an update — and never switched back on.
- A redesign or a move to a new CMS. The new templates were built from scratch, and nobody remembered the container code.
- New pages outside the main template. Landing pages built in a page builder, or a cart or checkout on a separate template or subdomain.
- Speed optimization. A caching or script-combining plugin changes or defers the code, and the container stops firing.
- The wrong ID. After moving from a staging site, the website is left with the staging container instead of the live one.
How to spot a Google Tag Manager problem
You won’t see a missing container on the website — you’ll see it in the reports of the services that depend on it:
| What you see | Likely cause | What to do |
|---|---|---|
| Users in GA4 dropped sharply across the whole website, and Realtime is empty | The container code is missing from your pages | Search the page source for GTM-; if it’s not there, put the code back in the template or re-enable the plugin |
| Data disappeared from only some pages, such as the cart | Those pages use a different template | Add the container code to that template |
| Google Ads shows zero conversions while clicks are steady | The container or the conversion tag isn’t firing | Check the thank-you page in GTM Preview mode |
The page has a different GTM- ID than your account | A staging or old container was left behind | Replace the ID with the live one |
| Page views in GA4 are doubled | The GA4 tag is installed both in the code and in the container | Keep just one installation method |
The last row is the opposite problem: Google warns that installing the GA4 tag both ways at once leads to overcounted data (Google Analytics Help).
How to check Google Tag Manager yourself
First, make sure the container code is where Google recommends putting it:
“Copy the first block of code and paste it as high in the <head> tag as possible. […] Copy the second block of code and paste it immediately after the opening <body> tag.”
- Open the page and press
Ctrl+U(Cmd+Option+Uon a Mac). UseCtrl+Fto findgoogletagmanager.com/gtm.jsandGTM-. The ID should match the one shown in the GTM interface. - Open developer tools (
F12), go to the Network tab, reload the page and filter requests bygtm.js. The request should return a 200 status. - In GTM, click Preview and enter your website URL. Preview mode connects your website to Tag Assistant, where you can see which tags fired and in what order (Tag Manager Help).
- Install Google’s official Tag Assistant extension for Chrome. It helps you verify that Google tags, including the GTM container, are installed on the page and find setup errors.
- Repeat the check on your key pages: a product page, the cart, and the thank-you page after an order or lead.
- In the Versions section of GTM, make sure the published version actually contains the tags you need: the container can be on the website while a tag inside it has been deleted.
- Or use the FullCheckApp “Google Tag Manager check” and get the results in a clear visual format.
If you chose the last option, you’ve already made the right call: the check runs automatically, and you’ll be the first to know about any warning or critical issue.
What FullCheckApp checks
Every day, FullCheckApp checks whether the Google Tag Manager container is on your pages and shows its ID. It looks at your website from the outside, like a regular visitor, so there’s nothing to install.
- When. Once a day, at a time you choose, in your time zone.
- Where. The home page and up to 10 inner pages per website; the report shows exactly which page has the problem.
- What counts as a problem. A container that used to be on the page has disappeared or changed — that’s critical. You can change the severity of each check separately for every website.
- How you find out. You get an email report after every check, and critical issues are also sent to Telegram.
The first check records a baseline, and from then on the service compares the current state with it every day. If you removed GTM or swapped the container on purpose, you can accept the new state with one click, and it becomes the new normal. Individual tags are covered by the GA4 tag, Facebook Pixel and TikTok Pixel checks — both on the page itself and inside the GTM container.
FAQ
What’s the difference between Google Tag Manager and Google Analytics?
Google Analytics collects and reports visit statistics. Google Tag Manager doesn’t analyze anything: it’s the tool you use to install tags on your website, including the GA4 tag, Google Ads conversions and social media pixels. That’s why GTM often sits on a website alongside Analytics, but one doesn’t replace the other.
Why does the GTM code have a second noscript snippet?
The main container code runs on JavaScript. The noscript block, which Google recommends placing right after the opening body tag, is a fallback for browsers with JavaScript turned off. The first snippet in the head does the heavy lifting: if it disappears, tags stop working for almost all of your visitors.
Can a website have two GTM containers?
Technically, yes — for example, a separate container for an agency. But every extra container makes things harder to control: it’s easy to install the same tag twice, and then your analytics data doubles. If you have several containers, check after every update that the pages still carry exactly the IDs they should.
The container is on the website, but GA4 isn’t getting data. Why?
Having the container code on the page doesn’t mean the right tag is inside it. The tag may have been deleted or paused in GTM and a new version published, or its trigger may have stopped firing. Open GTM Preview mode and check in Tag Assistant which tags actually fire on the page.
Does Google Tag Manager slow down my website?
The container itself loads asynchronously, so it doesn’t block the page from rendering. But every tag inside it adds its own scripts and requests, so an overloaded container can slow your website down. Review the container from time to time, remove tags for services you no longer use, and test page speed, for example in PageSpeed Insights.
Sources
- Tag Manager Help — Introduction to Tag Managersupport.google.com/tagmanager/answer/6102821
- Tag Manager Help — Install a web containersupport.google.com/tagmanager/answer/14847097
- Tag Manager Help — Preview and debug containerssupport.google.com/tagmanager/answer/6107056
- Google for Developers — About Google Tag Managerdevelopers.google.com/tag-platform/tag-manager
- Tag Manager Help — Custom tagssupport.google.com/tagmanager/answer/6107167?hl=en
- Tag Manager Help — User-defined variable types for websupport.google.com/tagmanager/answer/7683362?hl=en
- Tag Manager Help — Google Ads conversionssupport.google.com/tagmanager/answer/6105160?hl=en
- Chrome Web Store — Tag Assistantchromewebstore.google.com/detail/tag-assistant/kejbdjndbnbjgmefkgdddjlbokphdefk
- Analytics Help — Troubleshoot tag setup on your websitesupport.google.com/analytics/answer/9311124
- Google Ads Help — Create Google Ads conversions based on Google Analytics key eventssupport.google.com/google-ads/answer/10632359
Check your website
Add your website address — the first check runs right away, and you’ll see the status of every item in this article.
Check for free