Guide

Tracking broke after a theme update

The script is still in the theme. One template no longer calls it. How to find the silent page type, and why a homepage-only check will miss it.

Last reviewed September 2026.

The script is still in the theme

That is what makes this failure quiet. The tag snippet is still in theme.liquidor a global section. One template no longer calls the helper that pushes the event. Nothing errors. The homepage still sends page views.

1. Load the page types the update touched

Product JSON templates, collection section groups, and the cart drawer are the usual casualties. A homepage-only check after a deploy is how this stays hidden.GTM loads but no tags fire is the same shape when the container is global and the trigger is not.

2. Library versus event on each type

If gtag/js or the pixel library returns 200 on product and collect does not leave, the install survived and the event call did not. If the library is missing only on that type, the template dropped the snippet or the section that contained it.

3. App embeds and the customizer

A theme update can disable an app embed without deleting the app. Check the theme editor’s app embeds list, not only the code. A disabled embed looks like “we didn’t change tracking”.

4. Date it

You will be asked when it started. A deploy log is a guess about the theme, not about the tag. A dated reading with page types is the record.Trace keeps that change log so the next update does not become a three-week hole.

Confirm it with a scan

Four page types, a real browser, no account. A scan will not fix the tag. It will tell you whether it is firing now.

Scan a store

All guides · How the scanner works · Watch the store