Guide

Google Tag Manager container not working? Check these four things

Updated 8 November 2026 · by Matt Klette

The Tag Manager snippet is in your theme, but GA4 shows nothing, Meta Events Manager is quiet, or Tag Assistant says no tags fired. Before debugging individual tags, check the container itself.

1. Has the container ever been published?

Changes in Tag Manager only reach your site after you click Submit → Publish. A container that was set up but never published loads on your site with nothing in it. In Tag Manager, open Versions: there should be a version marked Live. If not, nothing you've built is running.

2. Is it the right container ID?

Your theme loads a container by its ID (GTM-XXXXXXX). Compare the ID in your theme code with the one at the top of the Tag Manager workspace you're editing. Agencies often create a new container, configure it, and forget to swap the ID in the theme, or the old container was deleted.

Google serves a deleted or unknown container ID as an empty file, without an error. So the site looks fine while nothing runs.

3. Are two containers loading?

Stores that changed agencies often load two containers: the old one and the new one. If both have a GA4 or Meta tag, events fire twice. If the old one has a broken tag, it can throw errors that make debugging confusing. Remove the container you no longer manage.

4. Is consent blocking everything?

If your consent banner defaults to "denied" and your tags require consent, nothing fires until a visitor accepts. That's correct in Europe but often misconfigured for US traffic. In Tag Manager preview, check the Consent tab for the first event on the page.

Check all four at once

A free Pixel Check scan opens every Tag Manager container your site loads, tells you which version is live, flags empty or missing containers, and warns when more than one container loads. With daily monitoring you also get an email when a container is published, emptied or removed, so you know when an agency change lands on your live site.