E-commerce · Shopify
Shopify After the Upgrade: Test the Thank You Page
The upgrade deadline has passed. Find the active page version and test purchase events, consent and post-purchase apps with one identifiable order.

In this article
Reviewed 4 November 2026. A successful purchase can leave two different records. The store issues an order number, but the advertising or analytics platform never receives a purchase event. The upgrade of the Thank you and Order status pages can obscure exactly this kind of fault.
Identify the configuration your customers see
The deadline was 26 August 2026 for non-Plus and 28 August 2025 for Plus stores. Open Settings › Checkout › Configurations. Shopify says that an upgrade notice on the active configuration indicates deprecated pages. It describes the automatic upgrade for Pause and Build stores as permanent. The dates alone tell you little about whether a particular customization works. Shopify’s non-Plus guide and original Plus deadline
If you see the notice, open the personalized upgrade guide. It separates compatible apps, incompatible apps and additional scripts. Even a compatible app may need setup. Write down the job of every old snippet. A delivery notice needs a visible block, measurement needs an appropriate pixel, and a loyalty award needs a workflow supported by its provider. If the guide is empty, Shopify lets you proceed to publishing the replacement. Inspect both published pages afterwards. Shopify’s upgrade and app inventory steps
What should a test order trigger?
Shopify’s standard checkout_completed event fires once per checkout, usually on the Thank you page. With a post-purchase offer, it fires on the first upsell offer page instead. If the relevant page never loads, the browser event may be absent even though the store has the order. Web pixels run in a browser sandbox. A server-side route needs an integration that supports it. Event definition and Shopify pixels
For a custom pixel, Shopify Pixel Helper shows whether its subscription receives the event. Then inspect diagnostics at the destination. Receiving an event from a direct test order need not produce an attributed ad conversion. Mark test orders and account for refunds in your reporting. Testing custom pixels
When the totals diverge
Compare paid orders with received purchases over matched periods, currencies, consent choices and sales channels. For an abrupt drop, investigate one identifiable order. If it is absent in Pixel Helper, inspect consent and subscribed events. If it arrives there, follow the trail to the recipient. If you see two purchases for one order, look for a legacy tag or a second integration. A correct redirect or a visible block tells you nothing about that data path. First-party data and Shopify app permissions