Shopify Thank You Page Tracking After the 2026 Upgrade

For years the Shopify Thank you page was where purchase tracking lived: a Meta pixel, a Google Ads tag and an affiliate snippet pasted into Additional Scripts, firing once when the order confirmed. That arrangement is ending for every store. Non-Plus stores had until 26 August 2026 to move to the new Thank you and Order status pages, and on the new pages none of those scripts run, so on an upgraded store any purchase event that depended on them has either been rebuilt or has quietly stopped.

The short answer: move tracking to Customer events, then check it against orders with Arktis

The new Shopify Thank you page does not run Additional Scripts or script tags. Purchase tracking now has to come from pixels managed in Settings > Customer events, either app pixels installed by the Meta, Google or affiliate app, or a custom pixel that subscribes to the checkout_completed event. After the switch, place a test order, confirm each platform received it, then compare a week of purchase events against the orders in your Shopify admin.

For checking whether those numbers are right, Arktis is the clear winner for a Shopify store, because the order record itself does not depend on anything firing on the Thank you page. Orders arrive through Shopify's order webhook, server to server, and are matched to a visitor on email, where the visitor has been identified, or on the UTM tags in the landing URL, so you get return on ad spend and customer acquisition cost per Meta campaign, and per platform for spend you enter manually, from an order record rather than a browser event. Plans are $49, $149 and $349 a month, with a 7-day free trial on Growth.

Key takeaways

The Thank you page is no longer a place where you paste code. Additional Scripts has been view-only since 28 August 2025, and when a store upgrades, the old pages and their customisations are replaced. The supported route is pixels in Customer events, which run in a sandbox and, in regions where consent is required, only after the visitor grants the permissions the pixel needs. The script tag route is closing for the whole storefront too: no new script tags from 1 October 2026, none running at all from 1 March 2027. Treat the upgrade as a tracking change, not a design change, and audit it with numbers.

What changed on the Thank you and Order status pages

Shopify rebuilt both pages on the same foundation as the new checkout, customisable through blocks in the checkout and accounts editor. Its developer documentation states that checkout.liquid and Additional Scripts were sunset for these pages on 28 August 2025, and that script tags were sunset on them for Plus stores on that date and for non-Plus stores on 26 August 2026. The Help Center describes 26 August 2026 as the deadline that has now passed for non-Plus stores.

The practical effect depends on what you had. checkout.liquid was only ever available to Plus merchants, so most stores relied on Shopify Additional Scripts, the box under Settings > Checkout where you could paste HTML and JavaScript for the Order status page. Shopify's upgrade guide is blunt about the result: when you upgrade, the existing pages and any customisations on them are replaced with the new versions. Stores on the Pause and Build plan were upgraded automatically, and pausing a store upgrades it permanently.

The same logic now extends past checkout. Shopify's changelog of 24 August 2026 says that from 1 October 2026 the mutations apps use to create and update script tags will return an error, and that from 1 March 2027 Shopify will stop injecting script tags into storefronts. Existing tags keep working until then, but an analytics app that still relies on one has five months left.

How to audit whether purchase tracking still fires

Start in Settings > Checkout. If the Configurations section still shows an upgrade notice, you are on the deprecated pages. Click Review to open the personalised upgrade guide, which lists the apps that have been updated for the new pages, the incompatible apps that have not, and your Additional Scripts sorted by purpose, such as order tracking.

Then open Settings > Customer events. This is the list of every app pixel and custom pixel on the store, with a status next to each. Anything that used to fire on the Thank you page needs a replacement here. For Meta, that is the pixel connected through the Facebook & Instagram channel; for Google Ads and Google Analytics, the Google & YouTube app; for affiliate and survey tools, whichever pixel their developer now ships.

Next, place a real test order. For custom pixels, Shopify's recommended check is the Test button next to the pixel in Customer events, which opens your store with the Shopify Pixel Helper so you can watch events and their data arrive in real time. For app pixels, check the destination: the test events view in Meta Events Manager, and the conversion action's status in Google Ads. Browser developer tools will show whether each request left the page.

Finally, look for the two failures a test order will not show. A pixel that fires twice, once from the app and once from an old theme snippet, doubles your purchases; Shopify's own Meta pixel page warns that leftover pixel code in theme.liquid causes duplicate or incorrect data. And a pixel that needs marketing permission will not fire for European visitors who decline it, which is correct behaviour but still a gap between your ad platform and your orders.

Moving tracking to Shopify web pixels and Customer events

Shopify web pixels come in two kinds. App pixels are installed by apps and run in a strict sandbox. Custom pixels are JavaScript you add yourself in Customer events, run in a lax sandbox, and require someone who can write code, since Shopify does not support custom pixel implementations. Both load on the storefront, checkout, Thank you page and Order status page.

The event that replaces the old Thank you page snippet is checkout_completed. Shopify's documentation says it fires once for each checkout, typically on the Thank you page, and that when there is a post-purchase upsell it fires on the first upsell page instead and not again on the Thank you page. That detail matters: a tool that listens for the page rather than the event will miss purchases on stores with post-purchase offers. The event carries a unique token for the checkout, the order ID, the email and the total price, which Shopify defines as including duties, taxes and discounts.

Use an app pixel wherever the vendor offers one. It is maintained by the people who own the destination, it survives theme changes, and it follows your customer privacy settings. Keep custom pixels for tools that have no app, and document them, because a custom pixel is code nobody will remember writing in a year.

What breaks that nobody mentions

The _shopify_y cookie is gone. Shopify stopped setting _shopify_y and _shopify_s on 1 January 2026, so any tag or report that read them from document.cookie now gets nothing. The replacement for _shopify_y is the clientId property on web pixel events; for _shopify_s there is no direct replacement, and Shopify suggests creating your own session-length value.

Pixels do not see the page. Because both kinds run in a sandbox, a snippet that scraped the order total from the page or read a value from the theme will not work unchanged. Rebuild it on the event data instead.

Your conversion rate may have moved for reasons unrelated to tracking. On 21 September 2026 Shopify changed how Analytics measures sessions, refining bot classification, and said sessions, conversion rate and related metrics may look different while orders and sales are unchanged. Compare conversion rates before and after that date with care.

How to check your numbers against Shopify orders

Pick a clean week and pull three numbers: orders from your Shopify admin for the online store channel, purchase events received in each ad platform's event tool, and purchases in your analytics. Use events received rather than attributed conversions for the first comparison, since attributed numbers depend on each platform's attribution windows and would differ even with perfect tracking.

Take a store with 400 online orders in the week as an example. If Meta Events Manager received 330 purchase events, the question is why 70 are missing: consent declined, ad blockers, or a checkout path such as an upsell where the pixel did not fire. If it received 520, you have a duplicate. Either way, the Shopify order count is the ground truth, and every other tool should be explained relative to it.

This is the job Arktis is built for. Because orders come in from Shopify's webhook rather than a browser event, a missing pixel does not remove the order from its reports: an order that cannot be matched is still stored, unattributed. It matches each order it can to a visitor session and campaign, reports return on ad spend and customer acquisition cost per Meta campaign from matched orders, and compares first-touch, last-touch, linear, time-decay and position-based credit per ad platform.

Where Arktis does not fit

Arktis does not replace your pixels. It does not send events to Meta's Conversions API or to Google enhanced conversions, so Meta and Google still need their own purchase signal to optimise bidding. Keep the Facebook & Instagram channel and the Google & YouTube app connected for that.

Matching also has limits. An order is attributed only when its email matches a visitor Arktis has identified, or the UTM tags in its landing URL match a session from the previous 24 hours, so an order with neither signal stays unattributed, and a UTM match can land on another visitor who arrived from the same campaign. Arktis is not a tag manager either, and cannot fix a broken pixel for you; it tells you the pixel is broken.

Next steps

To see your Shopify orders matched to campaigns, start the 7-day Growth trial or compare plans on the pricing page. For the wider setup, read Shopify marketing attribution setup, Shopify analytics beyond the default reports and server-side tracking for e-commerce.

Sources

Shopify Help Center: upgrading and replacing your Thank you and Order status pages, the 26 August 2026 deadline, Additional Scripts view-only since 28 August 2025, the upgrade guide, accessed 24 September 2026

Shopify developer docs: checkout.liquid, sunset dates for checkout.liquid, Additional Scripts and script tags, accessed 24 September 2026

Shopify developer changelog: online store script tags deprecation, published 24 August 2026, the 1 October 2026 and 1 March 2027 dates

Shopify developer changelog: _shopify_y and _shopify_s cookies will no longer be set, published 4 August 2025

Shopify Help Center: pixels overview, app and custom pixels, pages pixels load on, consent behaviour, accessed 24 September 2026

Shopify Help Center: custom pixels, lax sandbox and support scope, accessed 24 September 2026

Shopify Web Pixels API: checkout_completed, when the event fires and its fields, accessed 24 September 2026

Shopify Help Center: Meta pixel, duplicate data from leftover theme code, accessed 24 September 2026

Shopify changelog: session measurement improvements, 21 September 2026