makseongmakseong
StudioJuly 20, 20265 min readBy Maksym Burkhan

Shopify removes Additional scripts on 26 August 2026: what breaks and how to move it

On 26 August 2026 Shopify removes the Additional scripts field, along with the script boxes on the Thank you and Order status pages, for the Basic, Shopify and Advanced plans. Plus stores went through the same change on 28 August 2025. Anything still sitting in those fields stops running that day, and stores that have not migrated are upgraded automatically with the legacy customisations removed. Orders keep coming in as usual, which is precisely what makes this dangerous: the tracking goes quiet without anything looking broken.

What actually stops working

The Additional scripts field is where years of small additions tend to accumulate: a conversion tag added when the ad account was set up, an affiliate postback the network asked for, a survey widget somebody trialled once. All of it runs on the order confirmation page today, and none of it runs after the cutoff. The parts that cost real money are the ones reporting purchases back to advertising platforms, because those platforms then optimise campaigns against incomplete data.

  • Google Ads conversion tags and Google Analytics purchase events.
  • Meta, TikTok, Pinterest and Snap purchase pixels.
  • Tag Manager containers, and every tag that fired inside them.
  • Affiliate network postbacks, which is how partners get paid.
  • Review invitations, post-purchase surveys, chat and session-recording widgets.

Shopify does flag this for you. Settings, then Checkout, shows a warning banner and a review screen that lists what you have and sometimes suggests a matching app. What it does not tell you is which replacement fits each individual tag, or how to confirm the replacement actually reports orders once it is in place.

Why copying the code into a web pixel is not enough

This is the part that catches out even experienced developers. Additional scripts run Liquid on the server, so a variable like checkout.total_price is printed into the page before it ever loads. A web pixel works differently: it subscribes to a checkout_completed event and reads values from the event payload. The same numbers exist, but under different names and, critically, in different units.

  • checkout.total_price gives cents in Liquid; event.data.checkout.totalPrice.amount is already a decimal amount.
  • checkout.currency becomes event.data.checkout.currencyCode.
  • checkout.line_items becomes event.data.checkout.lineItems, with different field names inside.
  • Liquid conditionals such as if and for have no equivalent and must be rewritten in JavaScript.

The classic failure is dividing by 100 twice. The old snippet divided cents into currency units, the code gets pasted into a pixel where the value is already decimal, and every order is suddenly reported at one hundredth of its real value. Nothing errors. The campaign data just quietly becomes wrong, and by the time somebody notices, the ad platform has been optimising on it for weeks.

Customer fields are restricted now

If your tracking identified customers, there is a second trap. Email, phone, customer id and addresses count as protected customer data. Since 10 December 2025 these fields are nulled for pixels that do not have approved access, so a script expecting an email address receives an empty value instead of an error. Anything built on hashed-email matching, cross-device identity or customer-level attribution needs a decision here rather than a copy-paste: either request approved access, or move that logic to a server-side integration provided by the vendor.

How to migrate, in order

Work through it script by script rather than trying to move the whole field at once. Most tags belong to a platform that now ships its own Shopify channel app, and installing that app is both faster and more reliable than rebuilding the tag by hand.

  • Inventory what is in the field and identify what each script does, including the ones nobody remembers adding.
  • Replace platform tags with the official channel app: Google & YouTube, Facebook & Instagram, TikTok, Pinterest, Microsoft Advertising.
  • Ask affiliate networks for their app or a server-side postback, and get the answer in writing.
  • Rebuild genuinely custom tracking as a custom web pixel, remapping Liquid variables to the event payload.
  • Accept that anything which changed the appearance of the page needs a checkout UI extension, and that DOM manipulation inside checkout is no longer possible.
  • Remove the old script only after the replacement is confirmed working, not before.

How to confirm it actually worked

Do not trust the fact that an app is installed. The only reliable check is a real test order followed by confirmation in the destination system, because that is the place where a silent failure becomes visible.

  • Google Ads: the conversion appears with the correct value and currency, allowing up to three hours.
  • Meta Events Manager: exactly one Purchase per order, with no deduplication warning.
  • Affiliate network: the sale is recorded after ordering through a real tracking link.
  • GA4 Realtime: one purchase event, not two, which is the usual sign the old tag still fires somewhere.

Note that browser debugging tools that used to work on the Thank you page cannot attach to checkout any more, because it runs in a sandbox. Tag Manager preview mode in particular will not help you here, which is why verification has to happen in the destination platform rather than in the browser.

What happens if you do nothing

The store keeps selling. Shopify upgrades the pages for you and removes the legacy customisations in the process, so nothing looks broken from the outside. What changes is that ad platforms stop hearing about purchases, attribution reporting empties out, affiliate partners stop being credited for sales they generated, and review requests quietly stop going out. The cost is invisible for a while and then shows up as campaigns performing worse for reasons nobody can trace, which is a far more expensive way to discover the deadline than checking the field today.

By Maksym Burkhan · Founder, makseong

Maksym builds focused Shopify apps at makseong and writes about Google Merchant Center, product feeds, and the compliance problems merchants actually run into.

Related guides

See it on your own store

Check my checkout scripts