Shopify customer events and custom pixels for checkout
How Shopify checkout tracking works after checkout.liquid and additional scripts: customer events, app vs custom pixels, the Web Pixels API and key dates.
By DATALYR · · 4 min read
Contents
How checkout tracking works now
Shopify checkout tracking now runs on customer events: Shopify publishes events such as checkout_started and checkout_completed, and pixels subscribe to them through the Web Pixels API. You manage those pixels in the Customer events section of the Shopify admin, not in theme code or checkout scripts.
Pixels load on the storefront, checkout, Thank you page and Order status page. That makes customer events the supported replacement for the old checkout.liquid edits and additional scripts.
The checkout.liquid and additional scripts dates
Shopify retired the old methods in stages. checkout.liquid stopped working for the information, shipping and payment pages on August 13, 2024. For Shopify Plus, checkout.liquid and additional scripts on the Thank you and Order status pages were sunset on August 28, 2025.
For stores on other plans, the additional scripts section became view-only on August 28, 2025, and August 26, 2026 was the deadline to upgrade the Thank you and Order status pages. Shopify upgraded stores that had not upgraded by then. Scripts that used to fire on those pages need to be rebuilt as pixels or app blocks.
- Search old additional scripts for purchase tags, conversion snippets and survey widgets.
- Replace each tag with an app pixel from the vendor's Shopify app, or with a custom pixel.
- Replace visual widgets, such as surveys, with Thank you page app blocks.
App pixels and custom pixels
App pixels come from apps you install. They are built with Shopify's web pixel extension, run in a strict sandbox and receive their settings from the app. Custom pixels are code you paste into Customer events. They run in a lax sandbox and are, in Shopify's words, unsupported by Shopify, so you own their maintenance.
Prefer an app pixel when the vendor offers one: it updates with the app and does not depend on code someone pasted years ago. Use a custom pixel for tools without a Shopify app, or for GTM.
Both kinds obey your customer privacy settings. In regions that require consent, pixels run only after the visitor grants the permissions the pixel needs. New pixels require marketing and analytics permission by default.
The events that matter for ads
Shopify lists the standard events. For ad measurement the useful ones are product_viewed, product_added_to_cart, checkout_started, checkout_contact_info_submitted, checkout_shipping_info_submitted, payment_info_submitted and checkout_completed. checkout_completed is the browser view of a purchase.
Illustrative example of a checkout funnel built from these events: 1,000 checkout_started, 620 payment_info_submitted and 540 checkout_completed. That is 54% of started checkouts completing, and 87.1% completion once payment details are in (540 ÷ 620). The big drop sits before payment, so shipping cost and form length are the first things to check.
Abandoned checkouts are visible this way too: a checkout_started with no checkout_completed. Shopify also sends checkout records to apps by webhook, which catches abandonment even when a browser pixel was blocked.
A checkout funnel from customer events (illustrative)
1. checkout_started
1,000
Every checkout opened.
2. payment_info_submitted
620
62% reach payment.
3. checkout_completed
540
54% of starts; 87.1% of payment submits.
Thank you page tracking without scripts
Tracking on the Thank you page used to mean an order status script. Now pixels load on the Thank you page, and Shopify publishes checkout_completed when the purchase completes, with the order details your tags need. Send the order ID with every purchase tag so destinations can deduplicate.
Browser purchase events still depend on the page loading and on consent. A buyer who closes the tab early, blocks scripts, or declines consent may complete an order that no pixel sees. That is why the order webhook, not the pixel, should own revenue.
Headless storefronts built on Hydrogen or a custom frontend add their own analytics layer and usually still hand off to Shopify checkout. Check that the storefront and checkout share the same visitor identity, or each order will look like a new visitor at checkout.
How DATALYR uses customer events
Connecting Shopify to DATALYR installs a DATALYR Web Pixel, an app pixel that records the checkout and product funnel. Shopify's order webhooks carry paid orders, refunds and transactions. The webhook owns revenue and the pixel owns the funnel, so the pixel's checkout_completed carries no value and cannot double-count a sale.
The theme App Embed links each order to the visit that preceded it by writing the visitor ID and Meta click IDs into the cart, which Shopify carries onto the order. If the Web Pixel install fails, reconnecting the store from Sources reinstalls it.
Related articles.
Commerce ·
Google Tag Manager on Shopify: custom pixel setup
How Google Tag Manager runs on Shopify today: as a custom pixel in Customer events, fed by Shopify events, with checkout coverage and no duplicate tags.
Commerce ·
Shopify conversion tracking: reconcile orders, refunds and ad delivery
Verify Shopify order capture, campaign identity, transaction revenue and destination delivery without counting the same purchase more than once.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
