What the 404 means
The Tag Manager snippet loads gtm.js?id=GTM-XXXXXXX from googletagmanager.com. Google answers with a 404 when it has no published container under that ID. The three usual reasons:
- The container was deleted, often during a clean-up of an old account.
- The ID on the page is mistyped, or copied from a different site.
- The container exists but has never been published.
Whatever the reason, nothing inside the container runs: GA4, Google Ads, the Meta Pixel and every other tag you manage there.
How to fix it
1. Read the ID off the page
In the Network panel, filter for gtm.js and reload. Note the ID and the status code.
2. Compare it with your account
In Tag Manager, the container ID is shown next to each container's name. If none matches, the page has the wrong ID: replace the snippet with the one from the right container.
3. Publish
If the container exists but was never published, submit and publish a version.
4. Remove dead snippets
Sites often carry two containers, one live and one long gone. Remove the dead one rather than leaving it to fail on every page view.
How TagZ reports it
The scan lets gtm.js load from Google for real, so a deleted container shows its real 404. One container that cannot load is a serious finding. A dead copy next to a working one is reported as A Google Tag Manager script on the page fails to load. A container served from your own domain (server-side GTM) is noted, not flagged.
What the report says
This is the finding TagZ writes when it sees this fault, word for word.
Google Tag Manager cannot load
Nothing is reaching Google Tag Manager from this page. Whatever depends on it — reporting, audiences, conversion counts — has stopped receiving data.
Suggested fix
The library file itself is failing. A 404 usually means the container or account ID was deleted or mistyped; a blocked request usually means a Content-Security-Policy rule. Compare the ID on the page with the one in the platform account.
A scan is one look. Tags break later.
A theme update, a plugin, a new cookie banner, someone tidying up an old account: tracking rarely breaks loudly. TagZ monitoring runs this same check every six hours in a real browser and emails you when a tag that was working stops sending, after a second scan has confirmed it.
$7.99 a month for one website, billed yearly ($95.88 a year), or $2.63 a site per month on the Agency plan for 25 sites, billed yearly. See all plans.