Shopify Additional Scripts Removed: Fix GA4 & Meta Tracking

This was the last step of a change Shopify had been rolling out for a while. Its upgrade guide explains that when the pages upgrade, the existing Thank you and Order status pages and their customizations are replaced by the new versions. Customizations have to be rebuilt with blocks and web pixels, and tracking moves to app pixels.

For many stores, the Additional Scripts box held the purchase tags for GA4, Google Ads and Meta, plus affiliate postbacks and survey scripts. On the new pages that code doesn't run, so anything that wasn't rebuilt simply stopped reporting. Stores on the Pause and Build plan were upgraded automatically, and Shopify notes that this upgrade stays in place after the store is unpaused.

You can see what used to run: the Additional Scripts section in Settings > Checkout has been view-only since August 28, 2025. Copy it into a document before doing anything else. It's your inventory of what needs a new home.

Broken tracking rarely announces itself. Orders keep arriving in Shopify while the ad platforms and analytics quietly drift. These are the signs we see most often after a checkout change.

Work through the places below and write down, for GA4 and for Meta separately, where page views, add-to-cart and purchase events come from today. You want exactly one source per event per platform.

Shopify's pixel documentation recommends app pixels whenever possible, because they're more secure and update automatically, and custom pixels only when no app pixel meets your needs. For GA4 and Meta, the official channels cover the standard ecommerce events.

Google: in your admin, open Sales channels > Google & YouTube, connect your Google account and select your GA4 property. Shopify says certain ecommerce events are then tracked automatically. Its Google Tag Manager help page also recommends the built-in integration for Google Analytics because it already contains the logic for ecommerce data, and warns that running it alongside a GA implementation in Tag Manager can double-count.

Meta: the Facebook & Instagram channel offers three data-sharing levels. According to Shopify's help center, Standard uses the Meta pixel only, which browser ad blockers can stop. Enhanced and Maximum add Meta's Conversions API, which sends events server to server where browser ad blockers can't block them.

Meta deduplicates browser and server events only when they share the same event name and event ID, and only within 48 hours, according to Meta's deduplication documentation. A pixel you add by hand next to the channel app won't share event IDs with the app's server events, so you'll count purchases twice. Pick one setup per platform.

Custom pixels run in what Shopify calls a lax sandbox, designed to give you control over what you send to third parties. Shopify notes that not all pixel functionality works in the sandbox, that adding and using custom pixels is unsupported by Shopify, and that compliance, consent, code security and updates are your responsibility.

The event you care about most is checkout_completed. Shopify's developer documentation says it fires once per checkout, typically on the Thank you page. If you use a post-purchase upsell, it fires on the first upsell page instead and not again on the Thank you page. If the page it should fire on fails to load, it doesn't fire at all.

For GA4, map checkout_completed to a purchase event and send the Shopify order ID as the transaction_id. Google's ecommerce documentation says transaction_id is required for purchases, and that currency must be set when you send a value. Old Additional Scripts snippets often wrapped tags in a first_time_accessed check to avoid counting revisits; the pixel event's once-per-checkout behavior takes care of that.

Shopify also supports Google Tag Manager through a custom pixel if you need tags the channel apps don't cover, such as a niche ad platform. Keep GA4 itself in the Google & YouTube channel to avoid the double-counting Shopify warns about.

Go back to your copy of the old Additional Scripts and handle each non-analytics block. Shopify's upgrade guide says customizations can be replaced with built-in Shopify features, apps from the Shopify App Store or custom apps.

Affiliate and partner tracking: check whether the network has a Shopify app with an app pixel. If not, a custom pixel on checkout_completed can pass the order ID and value the network needs.

Post-purchase surveys and custom thank-you content: these need visible interface, so they move to blocks on the new Thank you page, usually provided by the survey app or a custom app. A pixel can't draw anything on the page.

Cash-on-delivery verification and order messaging: anything that confirms or flags an order is safer running on the server when an order is created than as a script on the thank-you page, because the page may never load. An app or automation that listens for new orders keeps working whether or not the customer sees the confirmation screen.

If your theme still has tracking code or app snippets from tools you've replaced, clean them out on a duplicate theme; our guide to removing leftover Shopify app code covers the safe way to do it. Klaviyo's order events come from its own Shopify integration, but if your email flows went quiet around the same time, see why Klaviyo flows stop triggering on Shopify.

Shopify's own help center lists reasons its numbers differ from tools like Google Analytics: visitors who block cookies or JavaScript, browser extensions that block tracking, different reporting time zones, and different tracking methods. Its privacy settings documentation adds that where a cookie banner is required, non-essential data is collected only after consent, which reduces sessions and conversions in analytics.

There's no official 'normal' gap. The useful signal is change: track GA4 purchases divided by Shopify online store orders each week. A steady ratio that suddenly drops points to a tracking break; a ratio above 1 points to duplicates.

Don't call it fixed until you've watched a real order flow through every tool. Place a real low-value order you can refund, or use your payment provider's test mode, and check each step below.

Write the result in your change log: date, what changed, who made the change, and the test order number. When reported ROAS moves next month, you'll know whether tracking changed or performance did. Clean purchase data matters most when you're making budget calls, such as deciding which ads to scale in Meta creative testing on a small budget.

If you'd rather hand the rebuild to someone else, the WordPress & Shopify team at Pixel2Tech works from the same inventory: every old script labeled, each one moved to an app pixel, custom pixel or app block, and each verified with a test order before we sign it off.