What the check looks at
- The snippet. Every
GTM-…container ID on the page, from the script tag or the inline snippet. - The download. The
gtm.js?id=GTM-…request to googletagmanager.com and its HTTP status. The scan lets that file load from Google for real, so a deleted container shows its real 404. - Whether it ran. A 200 is not proof: a script can download and never run. The container counts as working only when it registers itself in the page (
window.google_tag_manager) or itsgtm.loadevent reaches the dataLayer. - The tags inside. GA4, Google Ads, Meta and the rest are each checked on their own, so you see which tags the container actually released.
What a 404 means
Google answers gtm.js with a 404 when it has no published container under that ID. In practice the container was deleted, the ID on the page is mistyped, or it was never published. The page looks fine; nothing in it is measured. Our GTM container 404 guide walks through the fix.
If one container fails while another on the same page works, the report says one install is dead: usually a leftover that should be removed.
A container served from your own domain (server-side GTM or a tag gateway) is not a fault. The report notes it ran without coming from googletagmanager.com.
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.