Skip to main content
FHAVI

Research · Platform

Checkout extensibility changed what your tracking can see

Verified November 2026. What moved out of reach when Shopify replaced checkout.liquid, what the new surfaces allow, and how to tell whether a purchase event is still yours to fire.

2 min read

In brief

  • Checkout customisation moved from a template you edit to sandboxed extensions, which changes where a purchase event can live.
  • Stores that fired the purchase from checkout.liquid lost that placement and often kept the code in a place that no longer runs.
  • The durable answer is to fire the purchase from order creation on the server, with the browser copy as a secondary signal.

What changed

In the older model, checkout was a template you could edit. Scripts added there ran in the checkout page and could see the order in the browser at the moment of completion. That made it a natural place to fire analytics.

In the extension model, checkout customisation happens in constrained surfaces: UI extensions that render components, and web pixels that subscribe to events the platform emits. You no longer control arbitrary script execution in the checkout. Anything that depended on being there has to move.

Verified on

November 2026. Shopify changes these surfaces over time; confirm the current mechanism in the platform's own documentation before building. The architectural point — checkout is no longer a place for arbitrary scripts — has held for some time.

The symptoms, if this happened to you

  • Purchase counts fell while orders did not, usually at the point a store upgraded its checkout.
  • A script tag still exists in theme files or an app but is never executed, because the checkout no longer loads it.
  • Browser purchase events fire on the thank-you page but lose the identifiers that were only available in checkout.
  • Refund and cancellation events were never reimplemented because nobody owned them.

The configuration that survives platform changes

  1. 1

    Purchase from the server, at order creation

    This is the only point guaranteed to exist regardless of how the checkout is rendered. It also has the full order data and a stable id.

  2. 2

    Browser purchase from whatever surface exists today

    Use the web pixel or the thank-you page, with the same event id as the server copy so the two merge.

  3. 3

    Treat checkout as rented ground

    Any tracking that only exists because of a checkout implementation detail should be on a list of things to re-verify after every platform update.

  4. 4

    Test after every upgrade

    One real order, traced through the event log. Upgrades are the moment these breaks happen, and they are announced in advance.

Checkout is no longer a place where your script runs. Move the purchase to order creation, keep a browser copy with the same id, and re-test every time the platform announces a change.

Questions

Asked about this directly

Did my tracking break when checkout changed?
If purchase events were fired from a checkout template, very likely. Compare purchase counts before and after the upgrade date rather than looking for an error message — there will not be one.
Can I still customise the checkout?
Yes, through the supported extension surfaces. What you cannot do is run arbitrary scripts inside it, which is the part that used to carry analytics.
Is the web pixel enough on its own?
It is a good browser signal, but it depends on the browser completing. The server copy is what makes the count reliable; run both.

Keep reading

Other pieces in the library

All research

Numbers first, promises second

Send your store and we will tell you which of these failure modes is already happening — before you pay for a fix.

Prefer email? Write to md@fhavi.com