If you run ads to a Shopify store and your GA4, Google Ads or Meta numbers never match your Shopify orders, this page is for you. Shopify's checkout now runs on checkout extensibility, so old thank-you page scripts no longer fire and tracking has to live in Customer Events and on the server. I rebuild it so every platform sees the same purchases, with the right value and order ID.
Proper Shopify conversion tracking means sending checkout events from a Customer Events custom pixel (or a well-configured app), backing up purchases server-side from Shopify order webhooks, and using the order ID as the transaction and event ID everywhere, so GA4, Google Ads and Meta count each order once, with the correct value and currency.
The events I set up on Shopify, and where each one is sent.
Shopify has been retiring 'additional scripts' on the thank-you and order status pages (Plus stores first, then all plans). Any purchase tag that lived there has quietly stopped firing, which is often why conversions dropped without anyone touching the ads.
Customer Events pixels load in an isolated sandbox, so they cannot read your theme's page, click on checkout buttons or rely on GTM Preview mode the normal way. Tags copied from a regular website usually break or send empty values there.
The Google & YouTube and Facebook & Instagram apps send their own events. Add a GTM setup on top without turning anything off and you get two purchases per order and inflated ROAS.
The native apps give little control over event names, parameters, consent behaviour or which conversion action gets credit, and they don't cover TikTok or custom events like WhatsApp clicks.
Ad blockers, iOS restrictions and customers who close the tab before the thank-you page loads all mean missed purchases. Only a server-side feed from Shopify's order data catches those.
| Event | When it fires | Sent to |
|---|---|---|
view_item / ViewContent | Customer views a product page (product_viewed) | GA4, Meta Pixel + CAPI, TikTok |
add_to_cart / AddToCart | Product added to cart, including cart drawer adds (product_added_to_cart) | GA4, Meta Pixel + CAPI, TikTok |
begin_checkout / InitiateCheckout | Shopify checkout opens (checkout_started) | GA4, Meta Pixel + CAPI, TikTok |
add_shipping_info | Shipping step completed (checkout_shipping_info_submitted) | GA4 |
add_payment_info / AddPaymentInfo | Payment details submitted (payment_info_submitted) | GA4, Meta |
purchase / Purchase | Order completed (checkout_completed), backed up by order webhook | GA4, Google Ads, Meta CAPI, TikTok |
refund | Refund issued in Shopify admin (webhook) | GA4 |
I list every app, theme snippet and pixel that sends data, then compare a week of platform conversions against Shopify orders to see where the gaps and duplicates are.
We agree which native apps stay, which events go to which platform and what counts as a primary conversion, so nothing fires twice.
I set up the Customer Events pixel, the server container and the order webhook feed, with the order ID tying browser and server events together.
I place real or test-gateway orders across devices and check each one lands once in GA4, Google Ads and Meta with the right value.
For two weeks after launch I compare platform numbers against Shopify orders and fix anything that drifts.
On older Shopify stores you could paste a purchase tag into the order status page and be done. That option has been retired. Checkout and thank-you pages are now locked down, and the supported way to track them is Customer Events: a pixel that subscribes to events Shopify itself emits, like checkout_started and checkout_completed.
That is a good thing for reliability, but it means your tracking has to be rebuilt rather than copied. The pixel can't see your page's HTML, so all product and order data has to come from the event payload Shopify provides. I map that payload to GA4's ecommerce format and Meta's standard events, and keep the code short enough that the next person can read it.
The Google & YouTube and Facebook & Instagram apps are fine for a small store getting started. They send purchases, and the Facebook app can send server events too. The trade-off is control: you can't easily change parameters, add TikTok, respect a custom consent banner the way you want, or track things like WhatsApp clicks.
For stores spending seriously on ads, I usually keep the apps for what they do well (catalogue and Merchant Center sync) and move conversion tracking to a custom pixel plus server-side GTM. Either way, the key is that only one source sends each purchase to each platform.
A browser pixel only fires if the customer's browser loads the page and nothing blocks it. Shopify's order webhooks fire when the order is created, whatever happened in the browser. Feeding those into a server GTM container, through the Stape Shopify app or a direct webhook, gives Meta CAPI and other platforms a purchase signal that doesn't depend on the thank-you page. Sharing the order ID with the browser event lets each platform deduplicate the two.
Deduplicated Pixel + Conversions API and GA4 enhanced ecommerce for a Shopify loungewear brand, recovering purchases lost to iOS restrictions and ad blockers.
Read case studyNot for long. Shopify has been retiring additional scripts on the thank-you and order status pages as part of checkout extensibility, Plus stores first and then all plans. Purchase tracking now belongs in a Customer Events custom pixel or an app that uses the same events, ideally with a server-side backup.
Yes, for your storefront pages you can load GTM in the theme, and you can load it inside a custom pixel for checkout events. Inside the pixel it runs in a sandbox, so Preview mode and click triggers behave differently. I usually keep checkout logic in the pixel and use GTM mainly to route data.
It can send Pixel and server events and is a reasonable start. If you need control over parameters, consent handling, extra events or other platforms, a server GTM setup gives you that. Don't run both for the same purchase event, or Meta may count orders twice.
Common causes are retired thank-you page scripts, a purchase event firing from two sources, consent blocking tags, and orders the browser never reported. Some gap is normal because of consent and blockers, but a large one usually means a setup problem I can find in an audit.
No. Customer Events, custom pixels and order webhooks are available on standard Shopify plans. Plus adds checkout customisation options, but conversion tracking itself doesn't require it.
A typical setup with GA4, Google Ads and Meta CAPI takes a few working days including testing. Adding TikTok, server-side GTM on a custom domain or cleaning up a messy app setup can add a day or two.
A practical guide to Meta CAPI on Shopify and WooCommerce: native integrations, server-side GTM, Conversions API Gateway and how to test it all.
Meta merges Pixel and server events only when the event name and event ID match. Here is how to set that up correctly and prove it works.
What server-side tracking really is, how server-side GTM works, what it fixes and what it does not, and a checklist to decide if your business needs it.
Get a free audit of your tracking and ad account. Usually replies within 1–2 hours.
