Get free audit →

Home / Blog / Checkout Extensibility Broke Conversion Tracking

Shopify · Checkout Extensibility · Customer Events

Shopify Checkout Extensibility Broke Conversion Tracking: What to Check

If GA4 purchases, Google Ads purchases, Meta purchases, or Elevar checkout events dropped after moving to Shopify Checkout Extensibility, the old checkout script probably did not survive the migration.

This is not a normal “pixel is missing” problem. A store can still track product views and add-to-carts while losing the most important event: purchase. Storefront tracking and checkout tracking are now different surfaces.

Short answer: Shopify Checkout Extensibility breaks conversion tracking when old checkout.liquid, Additional Scripts, or thank-you page scripts are not migrated to Shopify Customer Events / Web Pixels API. Confirm checkout_completed fires, migrate Elevar or other tracking apps, remove duplicates, and validate every destination with real checkout tests.

Key takeaways

What Checkout Extensibility changed for tracking

Shopify says pixels collect and pass behavioral customer data from the online store, customer accounts pages, or checkout. Pixels can be app pixels or custom pixels. Shopify pixels and customer events

Shopify’s migration guide says Thank you page tracking and analytics scripts should be replaced using pixels. Shopify additional scripts migration

Symptom table

SymptomLikely causeFirst place to check
GA4 purchase missing after upgradeOld GA4 checkout script was in Additional Scripts or checkout.liquidShopify Customer Events + GA4 DebugView
Google Ads purchases stoppedConversion tag did not migrate to Web Pixel/Customer EventsGoogle Ads diagnostics + test purchase
Meta purchase missing but product events workStorefront pixel works, checkout purchase path does notMeta Events Manager + Shopify Pixel Helper
Elevar purchase stoppedShopify Source still needs Checkout Extensibility upgradeElevar My Tracking / Shopify Source
Duplicate purchases after migrationOld and new tracking both activeCustomer Events, app pixels, GTM, destination logs
Purchase fires with wrong value/itemsCheckout payload mapping incompleteWeb Pixel payload + destination mapping

The core event: checkout_completed

Shopify says checkout_completed logs when a visitor completes a purchase. It is triggered once for each checkout, typically on the Thank you page. For upsells and post-purchase flows, it can trigger on the first upsell offer page, and it will not trigger if the page where it should trigger fails to load. Shopify checkout_completed event

Elevar-specific checks

Elevar says Shopify is phasing out checkout.liquid and Order Status Page code for loading checkout tracking, and checkout code should be migrated to Shopify’s Customer Events setting. Elevar Checkout Extensibility preparation

  1. Open Elevar My Tracking.
  2. Locate the Shopify Source.
  3. Check whether a Checkout Extensibility upgrade action exists.
  4. Confirm the new Customer Events pixel is installed and connected.
  5. Confirm Elevar receives purchase events.
  6. Validate GA4, Google Ads, Meta, TikTok, Klaviyo, or other destinations from the correct source.

Common causes

1. Additional Scripts were never migrated

Old thank-you page code no longer runs where purchase happens. Shopify’s pixel migration guide says old pixels from theme.liquid, checkout.liquid, or Additional Scripts should be migrated to app or custom pixels. Shopify pixel migration

2. A custom pixel exists but is not connected

A saved but disconnected pixel is a common trap.

3. GTM was copied into a sandbox without understanding sandbox limits

Shopify Web Pixels run in a secure sandbox with APIs for subscribing to events. Shopify web pixels

4. Consent/privacy settings changed counts

Shopify notes events can decrease after replacing Additional Scripts with pixels because app/custom pixels track behavior with consent.

5. Duplicate tracking was left behind

New pixels plus old app tracking can duplicate purchase events if there is no clear source of truth.

Diagnostic workflow

  1. List every tracking source.
  2. Identify which source owns purchase tracking per destination.
  3. Confirm Customer Events includes the required app/custom pixel.
  4. Confirm the pixel is connected.
  5. Use Shopify Pixel Helper to test event receipt.
  6. Confirm checkout_completed fires once per order.
  7. Verify transaction ID, value, currency, tax, shipping, discounts, and items.
  8. Check GA4 DebugView, Google Ads diagnostics, Meta Events Manager, and Elevar logs.
  9. Repeat for Shop Pay, PayPal, post-purchase upsell, and consent states.

Tool comparison

ToolCheckout Extensibility angleWhat to verify
ElevarMigrate Shopify Source to Customer EventsSource upgraded, Customer Events connected, server-side destinations receiving purchase
AnalyzifySupports Web Pixels and Checkout Extensibility for GA4/Google AdsApp embed active, custom pixel connected, one Google Ads method active
LittledataTracks Shopify checkout including Checkout Extensibility and accelerated checkoutsCheckout steps and purchase appear in GA4
StapeServer-side setups must account for Customer Events and sandbox behaviorsGTM receives checkout events and maps identifiers correctly
Shopify native appsApp pixels are preferred when availableDestination diagnostics, consent behavior, duplicate sources

What not to do

TrackingAudit validation checklist

Checkout Extensibility broke your purchase tracking?

TrackingAudit can audit your migration from Additional Scripts / checkout.liquid to Customer Events, validate Elevar’s Shopify Source, and confirm every purchase destination against real Shopify orders.

Get your free audit →

Frequently asked questions

Did Shopify Checkout Extensibility remove Additional Scripts?

Shopify deprecated checkout.liquid, Additional Scripts, and script tags for Thank you and Order status pages and requires tracking to move to pixels or supported app integrations.

What replaces old checkout tracking scripts?

Shopify Customer Events, Web Pixels API, app pixels, custom pixels, or tracking apps that support Checkout Extensibility.

Why does add-to-cart still work while purchase is missing?

Add-to-cart often runs on the storefront. Purchase runs in checkout or post-purchase surfaces.

What is the main purchase event?

The key completed purchase event is checkout_completed.

Does Elevar support Checkout Extensibility?

Elevar provides migration guidance and says stores with Elevar code in checkout.liquid or Order Status Page scripts should upgrade the Shopify Source and migrate to Customer Events.

Sources