If purchases in GA4, Google Ads or Meta fell off at the end of August and your Shopify orders did not, the Thank You page is the first place to look. Agency write-ups report that Shopify set an August 26, 2026 deadline for upgrading its Thank You and Order status pages. After the upgrade, tracking code placed in Additional Scripts or old script tags stops running on those pages.
Check the date and the exact scope in Shopify's own migration notices or your admin, because most of what we found comes from agencies and not from Shopify. The fix is the same either way: move purchase tracking to Customer Events, and add a server-side copy as a backup.
How to tell whether you are affected
Run these checks:
- Compare daily orders in Shopify with purchases in GA4 for August through today. A step down that starts in late August points to this issue.
- Open Settings, then Checkout, and see whether your tracking snippets sit in Additional Scripts.
- Place a test order with Tag Assistant or the Meta Pixel Helper open. If the purchase tag does not fire on the order confirmation page, the code is not running.
- Check Google Ads conversion status for purchase actions that show "no recent conversions".
Stores that already used Customer Events or the official channel apps for Google and Meta may be fine. Stores with a pasted GTM snippet or old gtag code are the ones most at risk.
The fix: track purchases through Customer Events
Shopify's Customer Events and Web Pixels API are the supported way to run tracking on checkout and order confirmation. Pixels run in a sandbox and subscribe to events such as checkout_completed.
You have three options:
- Install the official apps. The Google & YouTube channel and the Meta channel can send purchase events without custom code. They give you less control over parameters.
- Add a custom pixel that pushes events to Google Tag Manager. This keeps your existing GTM tags.
- Send purchases server-side from the
orders/createwebhook to a server-side container. This does not depend on the browser at all.
Most stores that need control should use a custom pixel plus a server-side backup.
Example custom pixel
In Settings, then Customer events, choose Add custom pixel. Load your GTM container at the top of the pixel, as in Shopify's documentation, then add a subscription like this:
analytics.subscribe('checkout_completed', (event) => {
const checkout = event.data.checkout;
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: String(checkout.order && checkout.order.id),
value: checkout.totalPrice.amount,
currency: checkout.currencyCode,
items: checkout.lineItems.map((item) => ({
item_name: item.title,
price: item.variant && item.variant.price.amount,
quantity: item.quantity
}))
}
});
});
Treat this as a starting point. Check the field names against Shopify's current Web Pixels API reference before you publish, because they can change. Then create a GTM trigger on the custom event purchase and attach your GA4, Google Ads and Meta purchase tags.
Our guide on Shopify tracking with native integration, custom pixel or GTM compares the approaches in more detail.
Add a server-side backup
Customer Events still depend on the browser. A buyer who closes the tab, blocks scripts or pays through an accelerated checkout may never trigger the pixel. A webhook-based event comes from Shopify itself, so it fires for every order.
The setup looks like this:
- Create an
orders/createwebhook that sends order data to your server-side GTM container. - Map the order to GA4's purchase event, with the same transaction ID your browser event uses.
- Forward it to Google Ads and to the Meta Conversions API.
- Deduplicate so each order counts once. Use the transaction ID for GA4 and an event ID for Meta.
Without deduplication, you trade missing purchases for duplicate ones. See our server-side tracking service for how we build this.
Consent and privacy settings
Each custom pixel has a Customer privacy setting. The options include requiring customer permission before the pixel runs or letting it always run. Pick the setting that matches your consent policy, and test it with a visitor who declines. If you use Google Consent Mode, send the consent state to your container as well.
Test before you trust it
After any change:
- Place a real test order for a low-value product, or use a Shopify test gateway.
- Check GTM Preview to see the
purchaseevent and its values. - Check GA4 DebugView or Realtime for one purchase with the right revenue.
- Check the Meta Events Manager test events tab and the Google Ads conversion diagnostics.
- Compare totals over the following week against Shopify orders. Allow a small gap for cancelled orders and test orders.
If you also followed our Google Ads conversion tracking for Shopify steps, note that the Additional Scripts method in that older guide no longer works on upgraded pages.
Need expert tracking setup?
Our Google Tag Manager experts have delivered 500+ tracking setups with a 98% success rate.
Get a Free Consultation →