Audit tracking signals on your Shopify store

Shopify makes tracking feel handled: you add the GA4 tag or the Meta Pixel to the theme, load a product page, and a scan sees the pixel — so tracking looks done. But on Shopify the storefront and the checkout are two different worlds. Your theme controls home, collection, product, and cart pages; the checkout and the thank-you page are hosted by Shopify on a separate, sandboxed surface your theme code never touches. A pixel sitting in the theme can appear present on every product page while the purchase event — the one that fires at checkout — never happens.

That gap is exactly where campaign data goes quiet. The pixel loads on the storefront, so Events Manager and GA4 show pageview and view-content activity, and everything looks alive. But the purchase and conversion events ad platforms optimize against fire on the checkout and thank-you pages, and a theme-level tag has no reach there. Ad spend keeps running against a pixel that appears healthy while the revenue event it needs is missing.

The free check works at the visible layer: it looks for whether tracking signals appear on the public storefront pages it can crawl and flags the commerce-intent paths — product links, add-to-cart, checkout buttons — that usually depend on them. It does not complete a checkout or prove the purchase event fires; that still needs GA4 realtime or Events Manager on a real order. It tells you what appears present on the storefront and where the checkout-side events are worth confirming.

For years, Shopify stores added conversion scripts through checkout.liquid or the Additional Scripts box in checkout settings. Shopify has been retiring those in favor of Checkout Extensibility and the Web Pixels API, and a store that relied on the old method can lose its checkout tracking the moment the old checkout is turned off — with no error and no visible change to the storefront.

Even on a current setup, Shopify tracking is fragile in ordinary ways. A theme update or a switch to a new theme can drop a hard-coded tag. A marketing app that injected a pixel gets uninstalled and takes its events with it. Two apps install the same pixel and it fires twice, double-counting orders. A consent banner blocks tags until the shopper accepts. None of these leave a mark on the storefront a shopper — or a quick glance — would notice.

The free check reads the public storefront and flags whether the expected tracking signals still appear and which lead and commerce paths are visible. It cannot see inside your checkout settings, your apps, or your consent tool, so it points you to where to look rather than declaring a setup fixed. On a store where money moves through the checkout, that first outside read is a fast way to catch a signal that has quietly gone missing.

The thorough way to verify Shopify tracking is from inside: open the admin, check the GA4 and Meta channel connections, place a test order, and watch the purchase event land in GA4 realtime or Events Manager. That is the right tool for confirming a specific event fires — but it needs admin access to the store and a test order to reach the checkout side.

TrackCanary takes the opposite approach for the first look. Paste a public store URL — no admin login, no app install — and the check reviews whether tracking signals appear on the storefront alongside the product, cart, and checkout-intent paths that usually run through them, in one pass. It is the preflight you can run on any store, including a client's, before more ad budget goes through it — a way to see whether the storefront even appears to carry the tags before anyone opens the admin.

It does not replace a test order in GA4 or Events Manager — those still confirm the purchase event. TrackCanary is the step before that, and the step that keeps watching: a quick outside read of what appears visible on the storefront, and a way to be told when a signal that used to be there is no longer visible after a theme change or an app update.