On August 28, 2025, something happened that nobody saw coming. Shopify disabled checkout.liquid - the code layer that powered custom JavaScript on checkout pages for thousands of Shopify Plus merchants. They didn't announce it with a warning. They didn't give advance notice. They just turned it off.
What does that mean for you? If you're running a Shopify Plus store with custom conversion tracking, you're likely losing 30-40% of your conversion data right now. Your GA4 setup is broken. Your Meta pixel isn't firing on the thank-you page. Your Google Ads conversion tracking is incomplete. And if you're running a $10M/year business, that's roughly $250K-$330K per month in untracked revenue.
The problem is worse than it sounds because your ad platforms don't know they're working with incomplete data. Meta's algorithm is optimizing campaigns on 60% of the signal it should have. Google is misattributing conversion value. You're paying more for ads because the platforms can't see the true return on your spending.
This guide shows you exactly what happened, how to audit your store in five minutes, and three proven ways to fix it.
What Happened (Timeline)
To understand where we are, you need to know what changed. Shopify's transition from the old checkout system to their new one was driven by legitimate concerns: privacy compliance, performance, and security. But the execution left thousands of merchants in the lurch.
| Date | Event | Impact |
|---|---|---|
| Aug 28, 2025 | Shopify disabled checkout.liquid for thank you / order status pages | All custom JavaScript in checkout stopped firing |
| Jan 2026 | Auto-migration to checkout extensibility began | Stores migrated without guaranteed tracking carry-over |
| Ongoing | Web Pixels API is the new standard | Not all tracking scenarios are supported yet |
Here's what actually happened under the hood. Shopify moved checkout into a sandboxed environment. That sounds great in theory - it's more secure, faster, and harder for bad actors to inject malicious code. But it also means you can't use the same JavaScript tracking techniques you've been using for years.
In the old system, you could inject a script tag on the checkout page. That script could listen to the DOM, read the cart contents, wait for the order confirmation, and fire tracking events directly to Google Analytics, Meta, or any pixel you wanted. Your tracking was guaranteed to fire because you controlled the code.
The new system uses Web Pixels API - Shopify's official way to track events. The problem: Web Pixels API is a restricted environment. Not every tracking scenario is supported yet. Some tracking vendors have adapted; many haven't. And because the migration was automatic (not opt-in), most merchants didn't realize their tracking had broken until weeks or months of data were already lost.
Shopify replaced their old checkout.liquid templating system with checkout extensibility - a new API that claims to give you the same power. In practice, it doesn't. You can build pixel-perfect UIs, add custom fields, and extend the checkout flow. But core conversion tracking - the absolute most critical use case - still has gaps.
How to Check If Your Store Is Affected (5-Minute Audit)
You don't need to guess whether your tracking is broken. You can audit it right now in five minutes. The goal is simple: compare what Shopify says you sold to what your tracking platforms say you sold. If there's a big gap, you're affected.
- Compare Shopify orders vs GA4 purchases (last 30 days). Go to Shopify admin → Orders → count total orders. Now open Google Analytics 4 → Reports → Ecommerce → Purchases. Compare the numbers. If GA4 shows 30% or more fewer purchases than Shopify, your checkout tracking is broken. The Shopify number is the source of truth here - it's counting actual orders.
- Check Meta Events Manager. Log into your Meta Ads account and open Events Manager. Look at purchase event volume for the last 30 days. Now look back at August 2025 and earlier. If you see a sudden drop-off right around late August, your Meta pixel stopped firing on the checkout. This is one of the easiest red flags to spot.
- Check Google Ads conversions. Open Google Ads and look at conversion counts reported by the system. Compare that to actual Shopify orders for the same period. A growing gap between these numbers means tracking is incomplete. Google's algorithm is working with partial data.
- Review Customer Events in Shopify admin. Go to Shopify admin → Settings → Customer Events. Check which pixels are currently active. Look for any error messages or warnings. Some integrations may show degraded status.
- Test a purchase yourself. Use an incognito window and place a test order through your checkout. While you're placing it, have Meta Pixel Helper and Google Analytics DebugView open in another tab. Watch whether the purchase event actually fires on your thank-you page. If you see the event fire in the debugger but not in GA4 or Meta, there's a data pipeline problem.
For a $10M/year brand: 30-40% lost conversion data means $250K-$330K/month in untracked revenue. Your ad platforms are optimizing on incomplete data. Meta thinks your ROAS is lower than it actually is. Google thinks your conversion rate is lower. Both platforms respond by reducing spend or raising bids. You're overpaying for ads and underfunding the channels that actually work.
If you see any of these red flags - GA4 much lower than Shopify, Meta purchase events dropping off in August, or test orders not tracking - you need to act. The longer you wait, the more bad data accumulates and the harder it is to get a clean picture of what's actually working in your business.
How to Fix It
There are four approaches to fixing checkout tracking. Each has different trade-offs in cost, complexity, and timeline. Choose based on your technical resources and urgency.
If you have an in-house developer or are willing to hire one, building custom Web Pixels is the most direct solution. You write code that listens to Shopify's checkout events (like `payment_complete`) and sends conversion data to GA4, Meta, and Google Ads using their APIs.
The timeline is typically 2-4 weeks for a full migration. You'll need a developer who understands Shopify's sandboxed pixel environment (different from browser JavaScript), can work with the Web Pixels API, and knows how to test against Shopify's staging environment. Most brands end up paying a Shopify Plus agency $2K-$10K to do this correctly. The upside: once it's done, you own the tracking logic and can customize it however you want.
This is the fastest path for most brands. Companies like Analyzify and Littledata specialize in Shopify tracking migrations. They've already built Web Pixels implementations that handle GA4, Meta, and Google Ads. You install their app, connect your accounts, and they handle the setup.
Cost is typically $100-$500/month depending on the provider and your data volume. Timeline is hours, not weeks. The trade-off is that you're dependent on a third party to maintain the integration as Shopify's APIs evolve. But for most merchants, this is the right call - fast, low-risk, and professional.
This is the most reliable approach, and it solves a problem bigger than the checkout migration: browser tracking is getting weaker every year. iOS privacy changes have already gutted Apple platform tracking. Chrome is moving toward phasing out third-party cookies. Server-side tracking is the future.
Here's how it works: When a customer completes an order in Shopify, your backend immediately sends that order data to Meta's Conversions API, Google Ads, and GA4's Measurement Protocol. You're not relying on browser JavaScript at all. The data goes straight from your server to theirs.
- Meta Conversions API: Send purchase events directly from your server. These conversions carry higher confidence because they come from your authenticated backend, not a user's browser.
- Google Ads Enhanced Conversions: Server-side conversion verification that Google matches to users in its system. More reliable for attribution.
- GA4 Measurement Protocol: Stream conversion events directly to GA4 from your backend, bypassing browser limitations entirely.
The setup takes 1-2 weeks and requires backend development. But once it's live, your conversion data is rock-solid because it's source-verified from your order system. You'll also recover data you were losing anyway (iOS customers, browsers with tracking disabled, etc.).
While you're fixing the tracking problem, you need visibility into where data is being lost. Use anomaly detection to compare Shopify order volume to platform-reported conversions. When GA4 shows a sudden drop in purchase events while Shopify orders stay flat, you get alerted immediately - before days of bad data pile up and skew your insights.
Niblin's conversion tracking monitor watches for exactly this problem: divergence between Shopify's order data and what GA4, Meta, and Google Ads are seeing. When the gap exceeds your normal variance, you get an immediate alert. This won't fix the problem, but it will tell you how much damage is happening in real-time.
What Still Works After the Migration
While the migration broke a lot, some critical systems are still working. Before you panic, know what you still have access to.
- Shopify's own analytics. Order data in Shopify is always accurate. This is your single source of truth. Never trust platform pixels more than you trust your actual orders.
- Klaviyo integration. Klaviyo has built native Web Pixels support, so email tracking is still working well. Revenue per email sent and cohort analysis are reliable.
- GA4 via Shopify's Google & YouTube channel. Shopify maintains a direct integration with Google. It doesn't capture everything (some custom tracking scenarios still don't work), but it's more reliable than browser pixel.
- Apps built for Web Pixels API. Any app that was updated post-migration to use Web Pixels instead of checkout.liquid is working fine. Check your app dashboard to see which integrations have been updated.
- Server-side tracking via Conversions API. If you're already using Meta CAPI or GA4 Measurement Protocol, those are independent of the checkout.liquid deprecation and should be working fine.
The key insight: Shopify's data is always reliable. Everything downstream of Shopify (GA4, Meta, Google) is only as good as your tracking implementation. Fix the tracking, and everything else falls into place.
Here's what to do Monday morning:
- Run the 5-minute audit above. Compare Shopify orders to GA4, Meta, and Google. Quantify the gap.
- If the gap is more than 20%, this is urgent. Request quotes from a Shopify Plus agency or a managed service like Analyzify.
- In parallel, set up anomaly detection on conversion tracking so you know immediately when data is being lost.
- Pull 90 days of clean order data from Shopify. You'll need this as a baseline once tracking is fixed - to know how much data was lost and validate the new setup.
This isn't a problem that will fix itself. Shopify has no incentive to move fast on backward compatibility. The merchants who move fast to fix their tracking will have clean data and good optimization. The ones who wait will have months of garbage data, misaligned ad strategy, and wasted spend.
Key Takeaways
- Shopify disabled checkout.liquid on August 28, 2025, breaking custom conversion tracking for thousands of Plus stores.
- Most affected merchants are losing 30-40% of conversion data without realizing it.
- A 5-minute audit comparing Shopify orders to GA4 purchases tells you if you're affected.
- Four solutions exist: DIY Web Pixels migration ($2-10K), managed platforms ($100-500/month), server-side CAPI (most reliable), or anomaly detection (early warning).
- This problem gets worse the longer you wait - fix tracking before weeks of bad data skew your ad spend and strategy.
Frequently Asked Questions
Is my Shopify Plus store definitely affected?
Only if you had custom JavaScript on checkout or thank-you pages. If you were using native Shopify pixels (like Meta Pixel, Google Analytics) installed through the Shopify admin, you're less affected but may still see 20-30% data loss. Run the 5-minute audit to know for sure.
How long does it take to fix?
Depends on the approach. Managed platforms (like Analyzify): a few hours. DIY Web Pixels: 2-4 weeks. Server-side CAPI: 1-2 weeks. The longer you wait, the more data you lose, so prioritize this.
Will my Web Pixels API implementation break again?
Unlikely. Web Pixels API is Shopify's official future for checkout tracking. It's more stable than the old checkout.liquid approach and actively maintained. But monitor Shopify's changelog - API changes occasionally break custom integrations.
Should I implement both Web Pixels and server-side CAPI?
Yes, if your budget allows. Web Pixels handles browser-based tracking. CAPI handles everything else and provides higher-confidence conversions. Together they'll catch 95%+ of your orders, even accounting for privacy blockers and iOS limitations.
Is there a free solution?
Not really. DIY development costs time or agency fees. Managed platforms charge monthly. Server-side CAPI requires development. But the cost of doing nothing (lost data, bad optimization, wasted ad spend) is much higher.
By