Skip to content

TroubleshootingShopify

Shopify Checkout Tracking Broken: Diagnosis

Purchase tracking stopped after a theme or checkout change? Diagnose the cause, including legacy Additional Scripts tracking.

Published
Reviewed

Diagnosis

  1. Platform Shopify
  2. Usual cause Additional Scripts retired, or a custom pixel was never migrated.
  3. Causes, ranked 4
  4. How to diagnose it 6
Go to the checks

First answer free, within one working day. Describe your case

Sounds familiar?

The symptom

Symptom report Shopify

Tracking was working. Then, at some point, it wasn’t — and nothing on the store’s front end announced it. No error message, no broken checkout, no visible sign anything changed. The first clue is usually a conversion count that quietly drops to near zero in GA4 or an ad platform’s dashboard, days or weeks after the actual break happened.

A checkout flow with a break where an older mechanism has been switched off
Tick what you see

Tick the lines that match your store.

Describe my case

The short version

Direct answer

Purchase tracking that lives on Shopify’s checkout or thank-you page is uniquely fragile, because that code is controlled by Shopify, not by you, and can change without a notification reaching the store owner.

The common causes are a theme update touching tracking in theme files, an edited or cleared Additional Scripts box, a conflicting app, or a legacy implementation affected by Shopify’s sunset of Additional Scripts on Thank you and Order status pages on August 28, 2025. The August 26, 2026 deadline applied separately to order-status script tags on non-Plus stores. See Shopify’s checkout sunset dates, order-status script-tag guidance, and checkout extensibility documentation to identify the relevant migration path.

A real test order run through GA4 DebugView and Meta Test Events simultaneously tells you which of these you’re actually dealing with.

Where to look

Causes, ranked

Tracking went quiet4 causes

  1. Theme update removed the tracking code

    If tracking lived in theme files rather than the checkout itself, a theme publish or update can overwrite or drop it — this is avoidable going forward by moving tracking off theme pages entirely.

  2. Additional Scripts box edited or cleared

    Someone (a developer, an app, a well-meaning teammate) changed the code in Settings → Checkout → Order status page → Additional scripts, or an app that used to write to it was uninstalled.

  3. App conflicts

    A newly installed app added its own Customer Events pixel that overlaps with or breaks an existing one, or an uninstalled app took its tracking code with it.

  4. Shopify’s platform deprecation

    A legacy Additional Scripts or order-status script-tag implementation may be affected by different sunset dates. Check the store’s actual setup and the date its purchase events changed.

6 steps

How to diagnose it

Work through them in this order.

  1. In Shopify Admin → Settings → Checkout, inspect any legacy Order status page → Additional scripts setup and note what it was intended to send. The old code’s presence does not establish whether a live purchase event still arrives through another integration.
  2. In Settings → Customer events, check whether a Customer Events pixel is present and shows as Connected — this is the modern, supported location for checkout and thank-you-page tracking.
  3. Check Apps for recent installs or uninstalls, and your theme’s publish history, around the date tracking stopped working.
  4. Place a real test order and open GA4 DebugView and Meta Events Manager → Test Events at the same time, watching for the purchase event on both.
  5. View the actual Thank you page for a completed order (not a preview) and check network requests and GA4 DebugView for the purchase event. Also check Customer Events pixel activity, which runs in a separate sandboxed context.
  6. Confirm your store’s plan — Plus or non-Plus — since checkout customization capability differs between them, and a Plus store has typically already been through an earlier phase of this same migration with checkout.liquid.

Signal and fix

Decision table

CauseSignal you’ll seeFix
Theme update removed trackingBreak date lines up with a theme publish; the code lived in theme files, not checkoutMove tracking into a Customer Events pixel so future theme changes can’t touch it
Additional Scripts edited or clearedThe code box is empty or different from what it used to containCheck the live purchase path; Additional Scripts was sunset on Thank you and Order status pages in August 2025, so migrate a missing event to a supported Customer Events pixel
App conflictBreak date lines up with an app install or uninstall; overlapping Customer Events pixels presentAudit all Customer Events pixels for duplication or gaps; keep one authoritative pixel per platform
Shopify’s platform deprecationNo merchant-side change happened around the break date; a legacy purchase path may have stopped executingIdentify whether the store used Additional Scripts or an order-status script tag, then migrate a missing event to a supported pixel

A note from Daniilbefore you decide

Should you fix it yourself or bring in help?

Checking whether tracking lives in Additional Scripts or Customer Events, correlating the break date with a theme or app change, and running a DebugView test are within reach for a merchant comfortable in the Shopify admin.

Building or migrating a full Customer Events pixel with complete parameter parity — items array, values, transaction IDs, matched across GA4, Meta, and any other ad platform — is development work, and doing it under deadline pressure across multiple platforms at once is where most migrations go wrong.

A sound approach is to verify the new Customer Events pixel against daily Shopify order reconciliation for several days. If another live purchase path exists, check for duplicate events before cutting over.

If you’re not confident scoping that yourself, a tracking audit will map exactly what’s on Additional Scripts today versus what needs to move.

— Daniil

Next

If the self-check does not settle it.

The checks above find the cause in most stores. When two or more overlap, an order-level reconciliation is faster than another afternoon spent comparing dashboards.

Tracking Health Check

Price
USD 395
Access
Read-only
Timeline
verdict two working days after the kickoff

What the reconciliation shows for this symptom.

A Health Check reconciles this symptom order by order against your Shopify orders, so the cause is a fact from your own data, not a guess from a dashboard. Real numbers for this symptom are not published yet — ask for the sample report.

Request a Health Check · USD 395

Follow the order. Then compare the evidence.

  1. Real orderOrder ID, amount, currency
  2. Browser / server eventsConsent, event ID, delivery
  3. GA4 / advertising platformsReceived events and reporting
  4. Reconcile the recordsMatch IDs, time windows and definitions
A completed order and a reported conversion are different records. Check the path and compare like-for-like before treating a difference as missing data.

Questions

Questions this symptom raises

Is my store affected if I'm not on Shopify Plus?

Yes, non-Plus stores can be affected. Shopify sunset Additional Scripts and checkout.liquid on the Thank you and Order status pages on August 28, 2025. Its August 26, 2026 deadline applied separately to order-status script tags on non-Plus stores. Check which mechanism your store used and whether the purchase still reaches GA4 before migrating a missing event to a Customer Events pixel.

What exactly is checkout extensibility?

It's Shopify's framework for customizing and extending checkout using apps and app blocks instead of directly editing checkout code. For tracking specifically, the relevant piece is Customer Events (the Web Pixels API), which is the supported way to add analytics pixels to checkout and the thank-you/order-status page going forward.

Will Shopify tell me when my store's tracking breaks?

No. Shopify will notify you about platform-level changes like the Additional Scripts deprecation in its own changelog and admin notices, but it won't tell you that your specific tracking setup stopped working — there's no error state for a pixel that silently stops firing. That's why a break can run for weeks before anyone notices in the ad account or GA4.

My purchase tag lived in Additional Scripts — is that why it stopped?

Possibly. Additional Scripts on Thank you and Order status pages was sunset in 2025, but the presence of old code alone does not prove when your purchase tracking stopped or whether another integration replaced it. Check a live test order, then migrate any missing purchase event to a supported Customer Events pixel and verify it with next-day reconciliation.

Read more, or check a neighbouring symptom.

All symptoms

For the GA4-specific version of this diagnosis, see GA4 not tracking purchases. If Meta conversions are also affected, see Meta CAPI deduplication to check whether a migration introduced a duplicate-firing pixel rather than a missing one.

Daniil Maximkin

Hi, I’m Daniil.

I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian.

My story My work

Tried it and still stuck?

Describe your task

The first answer is free, within one working day. Or write directly: next@taskfordaniel.com