Why aren't my Google Tag Manager changes live on my site?
The Google Tag Manager help pages give 4 common reasons. The first to rule out: Saving a change is not enough. It only reaches your site once it is published.
Is it broken, or just quiet?
A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Google Tag Manager help pages give, and how to check each one yourself.
What causes it?
Saving a change is not enough. It only reaches your site once it is published.
In the Google Tag Manager help:
you will need to publish those changes to make those changes operational on your website or mobile app.
Publishing, versions, and approvals, read 2026-11-12.If you published to a test or staging environment, your live site still runs the old setup.
In the Google Tag Manager help:
When you publish a custom environment, you will not send those changes to the live version of your container.
Environments, read 2026-11-12.On some paid accounts a change needs approval before it can go live, so it may be waiting on someone.
In the Google Tag Manager help:
Containers owned by Tag Manager 360 accounts can add approvals to their workflow.
Publishing, versions, and approvals, read 2026-11-12.Work in a workspace stays apart from what is live until that workspace is published.
In the Google Tag Manager help:
develop and test tag configurations separately from your main production tag configurations
Workspaces, read 2026-11-12.
How do I check it myself?
Compare the live version with the one holding your change, to see whether the change was ever published.
In the Google Tag Manager help:
A version is a snapshot of a container configuration at a particular time.
Publishing, versions, and approvals, read 2026-11-12.Make sure the live site has the live container's snippet, not a test environment's.
In the Google Tag Manager help:
Install the relevant container snippet for each environment on their respective sites.
Environments, read 2026-11-12.Use preview to test a draft, but remember visitors do not see it until it is published.
In the Google Tag Manager help:
allows you to browse a site on which your container code is implemented as if the current container draft was deployed
Preview and debug containers, read 2026-11-12.If a workspace is out of date, someone else published since you started, so update it before publishing your change.
In the Google Tag Manager help:
each workspace will display a notification that the workspace is out of date
Workspaces, read 2026-11-12.
How would I know the day it starts?
- Feder reads the tags published in your live Tag Manager container.
- Feder reads only the live version, so a change still waiting to be published is not part of what it reads.
- If a measurement tag drops out of the live version, Feder tells you.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See what Feder reads from Google Tag Manager, which feeds Roots. Feder only reads. It never changes anything in Google Tag Manager.
What else goes wrong with these numbers?
- Why did a tag disappear from my live Google Tag Manager container?Google Tag Manager
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
- Why is yesterday's data missing in Google Analytics?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Google Tag Manager help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.