Aimerce Blog

Few Days Until Shopify Deletes Your Thank You Page Tracking

11 August 2026

Few Days Until Shopify Deletes Your Thank You Page Tracking

First-Party Data 101Shopify

Quick Answer: Beyond losing Additional Scripts, Shopify's checkout upgrade changes the Thank You page URL from /thank_you to /thank-you, confirmed directly by Shopify's own engineering team, and complicates pixel tracking on the Order status page depending on your customer accounts domain setup. Neither is fixed by the standard "migrate to Web Pixels" advice alone.

Key Takeaways

The Thank You page URL is changing from /checkouts//thank_you to /checkouts//thank-you, confirmed directly by Shopify's own Director of Engineering. Any hardcoded tracking URL or redirect rule pointing at the old slug needs updating.
Pixels don't reliably fire on the new customer-account Order status page, a gap Shopify itself has described as still in development, not something automatically solved by moving your customer accounts to a subdomain.
App and custom pixels only track with customer consent, unlike the old Additional Scripts, which fired regardless. If your old setup was tracking every visitor regardless of consent, the "gap" you might see after migrating could be a correction of previous overcounting, not new data loss.
Server-side purchase capture from Shopify's order webhook doesn't depend on either the Thank You page URL format or the Order status page's pixel behavior, since it's triggered by the order being created, not by a script executing on either page.
Checking where you stand takes one click: Settings > Checkout > Configurations. A banner there means you're still on the legacy pages.

Shopify is forcing an upgrade on all non-Plus stores by August 26, 2026. After that date, the legacy Thank You and Order Status pages are gone for good, and whatever you've got sitting in the Additional Scripts box just stops running.

Good. It should stop running.

Plus stores already went through this. As of August 28, 2025, their Additional Scripts and checkout.liquid became view-only, and PII access on the legacy pages got locked down. Shopify started auto-upgrading the stragglers in batches starting January 2026, with each store getting 30 days' notice before its pages got force-replaced and every existing customization wiped for good.

Non-Plus stores get one deadline: August 26, 2026. Miss it, and Shopify upgrades you automatically with no extra warning beyond whatever's already sitting in your admin. For the full picture on incompatible apps, the revert window, and how Custom Pixels differ from app pixels, that's covered in depth separately. This piece focuses on two specific things that break and don't get much attention.

A screenshot of Shopify's August 26, 2026 announcement regarding the deadline for stores on a non-Plus Shopify subscription plan to upgrade their existing Thank you and Order status pages to the new version of those pages.

Update: what happened after August 26?

Two weeks after the upgrade reached non-Plus stores, the busiest merchant threads on Shopify's community forum were about the same thing: Meta reporting fewer purchases than Shopify, Google reporting a different number again, and merchants trying to work out whether sales had fallen or measurement had. In almost every case, the store hadn't stopped selling. The Thank You and Order status pages had stopped telling the ad platforms about it.

The four causes behind most gaps

Most affected stores have more than one of these at the same time.

Purchase events in Additional Scripts disappeared. If your Meta, Google, or affiliate purchase event lived in the Additional Scripts box on the Order status page, it stopped running on August 26. If nothing replaced it, those purchases simply stopped being reported.
Server-side setups that read from the old pages went quiet too. Some Conversions API integrations, including older setups from some tracking apps and custom scripts, took their data from the legacy pages. When those pages went away, the server side lost its feed as well.
Deduplication hid the gap at first. On some stores the browser pixel kept firing, and Meta's deduplication merged it with whatever was left, so the drop didn't show up clearly for a week or more.
Timezones made it look worse than it was. If your Shopify and Meta accounts use different timezones, day-by-day comparisons look wrong even when the events are fine.

The real cost is in bidding. Google's Smart Bidding and Meta's Advantage+ react to a drop in reported conversions faster than any person reviewing a dashboard, and conversions that were never sent don't come back later.

Two other things moved numbers in September

Not every change since August 26 is the upgrade's fault, so separate these before you fix anything.

Shopify changed how it counts sessions on September 21. Bots are now filtered out by default, sessions no longer split at midnight UTC, and some sessions without a pageview now count. That moved conversion rate and other session-based metrics inside Shopify, while orders and sales stayed exactly the same. The August 26 problem shows up as a gap between Shopify and your ad platforms. The September 21 change shows up inside Shopify's own reports.

Some orders now happen where no pixel can see them. Orders placed through Meta's direct checkout are attributed to Meta in your Shopify admin, but your browser pixels don't fire on them, because the checkout never runs on your store. We cover that in "Shopify Agentic Checkouts Don't Fire Your Tracking Pixel."

There's also a smaller trap. In one widely followed thread, Meta purchase events firing on homepage load were traced to a codeless rule in Meta's Event Setup Tool, not to Shopify.

Which problem do you have?

What you see	Most likely cause	Where to look
Meta and Google purchases dropped from August 26, Shopify orders didn't	Purchase events lived in Additional Scripts or read from the legacy pages	Events Manager and Google Ads conversions, compared with Shopify orders
The drop showed up a week or two late	Deduplication masked the missing server-side events	Browser vs. server split in Events Manager, compared with July
Daily numbers don't match, weekly ones roughly do	Timezone mismatch between Shopify and the ad account	Account timezone settings in Shopify, Meta, and Google Ads
Shopify conversion rate moved from September 21, orders didn't	Shopify's session counting change	Shopify Analytics, before and after September 21
Meta-attributed orders in Shopify with no matching pixel event	Meta direct checkout	Server-side purchase events in Events Manager
Purchase events with no actual purchase	A codeless rule in Meta's Event Setup Tool	Event Setup Tool rules in Events Manager

What to do now

Compare two windows. Pull Meta, Google Ads, and Shopify purchase counts for August 12 to 26 and August 27 to September 10. If the gap widened after August 26, the upgrade is the cause.
Confirm a server-side purchase event exists in Meta Events Manager, and check the browser vs. server split against July.
Match your timezones before comparing day-level numbers.
Annotate September 21 in every report that uses Shopify sessions or conversion rate, and don't compare across that date.
Check your Event Setup Tool rules if Meta shows purchases that didn't happen.
Fix the purchase event before you touch bids. Changing budgets based on a measurement gap teaches the algorithms the wrong lesson twice.

One thing that didn't change: purchases sent server-side from Shopify's order data weren't affected by the upgrade at all, because they're triggered when the order is created, not by a script on either page. If your gap is still open six weeks later, that's the fix that closes it for good. Our guide to fixing the Shopify vs. Meta revenue discrepancy walks through the comparison in detail.

Why does the URL slug change matter?

Because any tracking setup, redirect rule, or reporting script that hardcodes the old Thank You page URL will silently stop matching once the new page goes live.

The Thank You page URL is changing from /checkouts//thank_you to /checkouts//thank-you, underscore to hyphen. That's confirmed directly by Shopify's own Director of Engineering in an official AMA, and independently corroborated by Shopify's own changelog, which references the old /thank_you page and the new /thank-you page as distinct, named things. If anything in your stack, a UTM capture script, a reporting dashboard filter, an analytics segment definition, matches against the literal old URL string, it needs updating to match the new one, or it quietly stops matching anything.

Why does the customer accounts domain matter for tracking on the Order status page?

Because the Order status page now lives on a different domain than checkout, your customer accounts domain, and pixel behavior there has been a genuine, acknowledged gap, not just a configuration detail to get right.

Shopify's help center documents the mechanism: you can connect a custom subdomain, like account.yourstore.com, for customer account pages, which is where the Order status page now lives. But the same engineering AMA that confirmed the URL slug change also confirmed something else worth knowing: pixels don't reliably fire on the new customer-account Order status page at all, described at the time as a gap still in development, not something the subdomain setup alone was confirmed to resolve. If you're relying on Order status page tracking specifically, verify it's actually firing rather than assuming the domain setup alone takes care of it.

Are you actually losing data, or were you overcounting before?

Worth checking before assuming the worst. App and custom pixels only track with customer consent, which is different from how Additional Scripts behaved.

Shopify says this can mean fewer recorded events than the old scripts, which fired regardless of what a visitor had actually consented to. If your Additional Scripts pixel was tracking every visitor no matter what they'd consented to, you were probably overcounting before, not undercounting now. A drop in raw event volume after migrating isn't automatically a tracking failure, it might be your numbers becoming more accurate for the first time.

Legacy Pages vs. New Checkout Extensibility

Aspect	Legacy (Additional Scripts)	New (Checkout Extensibility)
Thank You page URL	/checkouts/id/thank_you	/checkouts/id/thank-you
Tracking respects consent	Not necessarily, scripts fired regardless	Yes, app and custom pixels only track with consent
Order status page domain	Same as checkout	Customer accounts domain, can be a custom subdomain
Pixel reliability on Order status page	N/A, scripts ran directly	An acknowledged gap as of recent Shopify engineering commentary
Server-side purchase capture (order webhook)	Unaffected either way	Unaffected either way

How do you check where you stand?

Go to Settings > Checkout > Configurations. If there's a banner prompting you to upgrade, you're still on the legacy pages. Click it and Shopify hands you a personalized guide listing exactly which apps and scripts need replacing before you hit Upgrade.

If you pause your store before August 26, your pages upgrade immediately whether you're ready or not.

Common mistakes to avoid

Assuming "migrate to Web Pixels" covers everything. The URL slug change and the Order status page pixel gap are separate issues that survive a standard Web Pixel migration if nobody checks for them specifically.
Panicking at a drop in raw event volume without checking why. Consent-respecting pixels recording fewer events than consent-ignoring scripts isn't automatically a tracking failure.
Hardcoding the old thank_you URL anywhere in reporting or redirect logic. It'll quietly stop matching once the new page is live, with no error to flag it.
Assuming a customer-accounts subdomain automatically fixes Order status page tracking. Verify it's actually firing rather than assuming the domain setup alone resolves it.

FAQ

Is the Shopify Thank You page URL actually changing? Yes. It's changing from /checkouts/id/thank_you to /checkouts/id/thank-you, confirmed directly by Shopify's own Director of Engineering. Anything hardcoding the old URL needs updating.

Will my tracking numbers drop after this migration? Possibly, but not necessarily because of data loss. App and custom pixels only track with customer consent, unlike Additional Scripts, which fired regardless. A drop in raw volume can reflect more accurate, consent-respecting counting rather than a tracking failure.

Does moving my customer accounts to a subdomain fix pixel tracking on the Order status page? Not confirmed to on its own. Shopify's own engineering team has described pixels not firing reliably on the new customer-account Order status page as a gap still being worked on, separate from the domain setup itself.

Does server-side purchase tracking get affected by any of this? No. Purchase capture triggered from Shopify's order webhook doesn't depend on the Thank You page URL format or the Order status page's pixel behavior, since it's triggered by order creation, not a script running on either page.

How do I know if I'm still on the legacy Thank You and Order Status pages? Go to Settings > Checkout > Configurations in your Shopify admin. A banner prompting an upgrade means you're still on the legacy version.