The Shopify Thank You Page Deadline Has Passed: A Tracking Check to Run Before BFCM

The Shopify Thank you page deadline for non-Plus stores was 26 August 2026. If your conversion pixels or upsells lived in additional scripts, here is how to audit your tracking before BFCM.

The Shopify Thank you page deadline for stores on non-Plus plans was 26 August 2026, and it has now passed. According to Shopify's Help Center, that was the cut-off for stores on non-Plus plans to upgrade their Thank you and Order status pages to the new versions built on checkout extensibility. On the new pages, customisations made through the old additional scripts box no longer run, and they have to be rebuilt with blocks, web pixels, app pixels or built-in features. The practical consequence is simple and easy to miss: if a conversion pixel, an affiliate tag or a post-purchase upsell lived in additional scripts, it may have stopped working in late August, and nothing in Shopify will have told you.

Orders keep arriving when this happens. What changes is the data outside Shopify: an ad platform that stops seeing purchases, an analytics property that reports a sudden fall in conversion rate, an affiliate network that stops recording sales. With the festive season under way in India and Black Friday Cyber Monday on 27 to 30 November, the next few weeks are the last calm window to check. This post is a step-by-step tracking audit for that window.

What the Shopify Thank you page deadline changed

Here is what Shopify's Help Center says, stated no more strongly than Shopify states it.

• 26 August 2026 was the deadline for stores on non-Plus plans to upgrade their Thank you and Order status pages.
• Stores on the Pause and Build plan received automatic upgrades, and Shopify notes that pausing a store upgrades these pages automatically, a change that persists after the store is reactivated.
• Since 28 August 2025, the additional scripts section in checkout settings has been view-only; it can no longer be edited.
• Customisations need to be replaced using blocks and web pixels for design and functionality, app pixels for tracking customer events, or built-in Shopify features.
• Shopify generates a personalised upgrade guide for each store that identifies existing customisations and points to the replacement for each.

Shopify Plus stores went through the equivalent change on an earlier timeline in 2025. Separately, Shopify is retiring script tags, which some apps used to inject code into the Order status page, and we covered that timeline in our post on the script tag deprecation. The two changes overlap: both remove old ways of running arbitrary code on post-checkout pages, and both push stores towards app pixels, custom pixels and checkout UI extensions.

What typically lived in additional scripts

For years, the additional scripts box was where store owners and agencies pasted anything that needed to run after a purchase. When we audit stores, these are the items we most often find there:

• Ad platform purchase tags, sometimes duplicated alongside an official sales channel integration.
• Analytics purchase events, often an older version of Google Analytics code that predates the current integration.
• Affiliate and influencer network conversion tags, which pay commissions based on what they record.
• Post-purchase survey widgets, such as 'how did you hear about us', that fed marketing attribution.
• Upsell or cross-sell widgets on the Thank you page.
• Custom code for order tracking links, loyalty point messages, or WhatsApp opt-in prompts.
• Liquid conditions, such as first-time-accessed checks, written to stop a conversion firing twice when a customer reopened the Order status page.

Every one of these either needed a replacement before the deadline or stopped running after it. The ones most likely to have slipped through are the affiliate tags and the surveys, because nobody looks at them every day, and the duplicated tags, because their disappearance can look like a small dip rather than an outage.

Why a broken pixel is so hard to notice

A broken purchase pixel does not produce an error a merchant would see. The checkout works, the customer gets a confirmation, the order appears in Shopify. The failure shows up somewhere else, usually as one of these:

• An ad platform reporting fewer conversions and a worse cost per purchase, which leads to budgets being cut on campaigns that were working.
• Automated bidding strategies that learn from conversions receiving less data, and bidding worse as a result.
• Analytics showing a fall in conversion rate that does not match Shopify's own order count.
• Affiliates or influencers complaining that sales are not being credited.
• Attribution surveys returning far fewer answers.

In each case the natural reaction is to blame the market, the season or the ad platform. That is why a deliberate audit beats waiting for someone to notice.

How Shopify tracks purchases now: customer events and web pixels

The replacement for pasted scripts is Shopify's customer events system, built on the Web Pixels API. There are two kinds of pixel, both managed in the Shopify admin under Settings, Customer events.

• App pixels are installed by apps and sales channels, such as Google's and Meta's own Shopify channels or an analytics app. You connect them and the app maintains the code.
• Custom pixels are code you or a developer add yourselves. Shopify's Help Center says they run in a lax sandbox for security, that not all pixel functionality works in that sandbox, that they need JavaScript knowledge, and that the merchant is responsible for compliance, security, maintenance and obtaining any necessary consent. Shopify does not support custom pixel code.

Both kinds subscribe to standard events that Shopify emits as a customer moves through the store, including page_viewed, collection_viewed, product_viewed, product_added_to_cart, checkout_started, payment_info_submitted and checkout_completed. The purchase event is checkout_completed.

The tracking audit, step by step

Set aside half a day. You need admin access to Shopify, access to each ad and analytics platform you use, and ideally the person who set up the original tracking. Work through these steps in order.

1. 1Find your record of the old scripts. Open Settings, Checkout and look for the additional scripts section. If your admin still shows the old content, copy it into a document. If it no longer does, look for the personalised upgrade guide Shopify generated, old agency handover notes, or theme backups.
2. 2List every destination. From that record, write down every platform that received purchase data: analytics, each ad platform, each affiliate or influencer network, survey tools, loyalty tools. That list is what the audit checks against.
3. 3Open Settings, Customer events. Note every app pixel and custom pixel, whether each is connected, and what it is for. Compare with your list from step 2.
4. 4Mark the gaps. Any destination from step 2 with no matching pixel in step 3 is probably not receiving purchases. Any destination with two pixels may be counting purchases twice.
5. 5Place a real test order. Use a low-priced product or a test payment method, and complete checkout as a customer would, on a phone.
6. 6Confirm the purchase in each platform's own debugging tool, such as the ad platform's test events view or the analytics debug view, and check that the order value and currency are correct.
7. 7Repeat the test with a post-purchase upsell if you use one, to confirm the purchase is still recorded when checkout_completed fires on the upsell page.
8. 8Write down what you found, what you fixed, and the date. You will need this when you read your BFCM reports.

Reading the data for the damage

Once you know what is connected, check whether anything broke between late August and now. The simplest method is to compare Shopify's own order count with each platform's reported conversions, week by week, from July to today.

• A sudden, lasting drop in a platform's reported purchases around late August, while Shopify orders hold steady, points to a broken tag.
• A sudden, lasting rise around the same date can point to double counting, for example an app pixel and a newly added custom pixel both sending purchases.
• A gradual change is more likely to be real performance, seasonality or a platform's own measurement changes.

No platform will ever match Shopify exactly. Ad platforms use their own attribution windows and models, consent choices limit what some pixels can send, and some orders come from channels no pixel sees. What you are looking for is a step change at a specific date, not a perfect match.

An illustrative audit of a typical setup

To make the steps concrete, here is how the audit might run on a common kind of store. This is an illustration built from patterns we see, not a specific client. Picture a D2C apparel brand on the Shopify plan, advertising on Google and Meta, working with a dozen Instagram creators through an affiliate network, and running a post-purchase survey.

• The record of old scripts shows five items: an older Google tag with a purchase event, a Meta purchase snippet, the affiliate network's conversion tag, the survey widget, and a block of Liquid that only fired on the first visit to the page.
• Customer events shows two app pixels connected, from Google's and Meta's own Shopify channels, and nothing else.
• So Google and Meta are covered by app pixels, and the old snippets for both are no longer running, which is fine. The affiliate tag and the survey have no replacement.
• A test order confirms purchases arrive in both ad platforms with the right value. The affiliate dashboard shows nothing for the test order.
• Week-by-week comparison shows affiliate-reported sales falling to almost zero from the last week of August, while Shopify orders from creator discount codes carry on as before.

The fix in that case is to install the affiliate network's Shopify app or get a customer events version of its tag, and to replace the survey with an app that adds a block to the new Thank you page. The harder conversation is with the creators, whose commissions were under-recorded for about five weeks. Shopify's own records of orders that used each creator's discount code are the evidence to settle that fairly.

Questions to ask your agency or developer

If someone else manages your tracking, these questions will tell you quickly whether the change was handled.

• Which items were in our additional scripts before the upgrade, and where is that record kept now?
• For each one, what replaced it: an app pixel, a custom pixel, a checkout UI extension, or nothing?
• When did you last place a test order and confirm each platform recorded it with the correct value?
• Have you checked for duplicates, where two pixels send the same purchase to the same platform?
• How do our pixels handle customers who decline consent?
• What happens to purchase tracking when a customer goes through our post-purchase upsell?
• Who will watch the numbers daily during the festive season and BFCM, and what will they do if a ratio changes suddenly?

Clear, specific answers mean the work was done. Vague answers, or 'it should be fine', mean the audit above is worth running yourself.

Fixing what broke

For each gap, there is usually one right replacement.

• Major ad and analytics platforms: use the platform's own Shopify app or sales channel, which installs an app pixel. Remove any old custom code for the same platform so purchases are not counted twice.
• Affiliate and influencer networks: ask the network for its Shopify app, or for code written for Shopify's customer events. A pasted snippet written for the old additional scripts box will not work as it was.
• Platforms with no app: a developer can write a custom pixel that subscribes to checkout_completed and sends the event on. Test it carefully, because Shopify does not support custom pixel code.
• Thank you page upsells and widgets: use apps built on checkout UI extensions, which place blocks on the new Thank you and Order status pages through the checkout and accounts editor.
• Surveys and messages: look for apps that add blocks to the Thank you page through extensions, or use Shopify's built-in options where they cover the need.

Consent and why some events will always be missing

Pixels on Shopify work alongside the store's customer privacy settings, and Shopify's Help Center makes the merchant responsible for obtaining any consent a custom pixel needs. Where a store asks for consent and a customer declines, a well-behaved pixel should not send marketing data for that customer. That is correct behaviour, not a bug, and it means some purchases will always be missing from ad platforms.

For Indian stores, consent is about to matter more. The DPDP Rules phase in obligations over the next year and a half, and we covered that timeline in a separate post. The practical point for this audit is to note, for each pixel, whether it depends on consent, so that a gap between platform conversions and Shopify orders is not mistaken for a broken tag.

The Order status page is a separate check

The Order status page is the page customers return to from their confirmation email to see order details and tracking. It was upgraded alongside the Thank you page, and some stores had customisations there too: tracking widgets, return links, loyalty messages and help prompts. Open a recent order's status page from a confirmation email and check that the things you expect to see are there.

Also check that no purchase tracking fires on repeat visits to this page. Old Liquid conditions used to prevent duplicates. On the new system, Shopify fires checkout_completed once per checkout, which removes most of that risk, but a hand-written custom pixel that listens to page views could still reintroduce it.

A timeline before BFCM

Black Friday falls on 27 November 2026 and Cyber Monday on 30 November. Diwali is on 8 November. Working back from those dates, here is a realistic plan.

1. 1This week: run the audit above and list every gap and duplicate.
2. 2Next week: fix gaps with official apps first, then custom pixels where needed. Remove duplicates.
3. 3By mid-October: place test orders again and confirm every destination records purchases correctly.
4. 4Late October: freeze tracking changes. Record a clean baseline of the ratio between platform conversions and Shopify orders.
5. 5During the peak: compare daily, and investigate any sudden change in the ratio immediately rather than after the weekend.

If you find a gap in the middle of the peak

Sometimes the audit happens late, or a gap appears after the freeze. If you discover in mid-November that a platform has not been receiving purchases, fix it, but fix it in the smallest way possible. Use the platform's official Shopify app rather than writing new custom code, test with a single order, and record the exact time the fix went live.

Then adjust how you read that platform's numbers. Campaign results before the fix are understated, so do not cut budgets based on them. Automated bidding may take some days to adjust once purchase data starts flowing again, so expect a period of uneven results. And tell anyone who reports on those numbers, such as an agency or a finance team, what happened and when, so the gap is explained in every report rather than rediscovered in January.

What not to do

• Do not paste old additional scripts code into a custom pixel unchanged. It was written for a different environment and may fail silently in the sandbox.
• Do not install several apps for the same platform. Choose one route per destination.
• Do not judge campaign performance from data covering late August without checking for a tracking break first.
• Do not change tracking during the peak unless something is clearly broken. A fix made on Black Friday is hard to test properly.
• Do not assume a platform's numbers are wrong because they differ from Shopify. Look for a step change at a date, not a perfect match.

Why this matters for merchandising too

Tracking is not only for advertising. Merchandising decisions, such as which products to feature, which collections to push and what order products appear in, are only as good as the numbers behind them. If your analytics lost purchase data in late August, any decision made since then from that analytics may rest on bad data.

That is one reason SellRank, our Shopify collection-sorting app, does not rely on a pasted script or on Google Analytics for its engagement data. It installs its own engagement pixel through Shopify's Web Pixels API the first time the app opens, and counts product views and add-to-carts per product per day as aggregates, with no customer data. Order and revenue figures come from Shopify. So when it ranks a collection by conversion rate or revenue, those numbers come from first-party sources that the Thank you page change did not touch. A Google Analytics backfill is optional on the Scale plan and up, for history before the pixel has data.

A short checklist to keep

• Every destination that should receive purchases has exactly one pixel sending them.
• Each pixel has been tested with a real order, including one through a post-purchase upsell if you use them.
• Order value and currency are correct in each platform.
• Affiliate and influencer networks have confirmed they are recording sales again.
• The Thank you and Order status pages show the blocks you expect.
• You have a dated note of every tracking change made since July.
• You have a baseline ratio of platform conversions to Shopify orders for the weeks before the peak.

Need a hand with the audit?

If you would rather have someone else run this audit, or you have found gaps and need custom pixels written and tested before the peak, tell us about your store on our contact page. We will check what is connected, fix what is missing and leave you with a written record. And if you want collection pages ordered by first-party performance data, SellRank has a free plan for one collection.