Shopify stores
One order. Three purchases in Google Ads.
Shopify stores collect tracking the way they collect apps: a channel app here, a GTM container there, a theme snippet from a past developer. We find what fires on every purchase, keep one clean source for each platform, and make sure the value sent matches the revenue the client actually counts.
WHO IT'S FOR
- Shopify and Shopify Plus stores running Google Ads, Performance Max and Meta
- Agencies taking over a store with years of leftover pixels and apps
- Stores where ad-platform revenue and Shopify revenue don't line up
What's tricky on Shopify
Where Shopify tracking usually goes wrong.
- 01
Checkout runs in its own sandbox
Shopify has moved checkout tracking to customer events and web pixels, which run in a restricted sandbox. Old scripts pasted into checkout or the order status page stop working or behave differently, and GTM can't simply read the checkout page.
- 02
Channel apps and GTM overlap
The Google & YouTube app and the Meta app each install their own tags. Add GTM or a custom pixel on top and the same purchase is sent two or three times, often with different values.
- 03
Value means different things
Order total, subtotal, with or without tax, shipping and discounts. Google Ads, Meta, GA4 and the client's finance team often each count a different number unless it's agreed and set once.
- 04
Browser tracking misses orders
Ad blockers, browser privacy and consent mean some purchases never reach the pixel. The Conversions API and server-side options recover part of that, but only if they're deduplicated against the browser events.
What we set up
What we connect, and what we clean up.
What we connect
- One purchase event per order for each platform, with the transaction ID for deduplication
- Meta Pixel and Conversions API through the Meta app or a server setup, deduplicated by event ID
- Google Ads purchases with enhanced conversions, and GA4 ecommerce events from a single source
- A purchase value agreed with the client, with tax, shipping and discounts handled the same way everywhere
Mistakes we fix most
- Purchases sent by the channel app and again by GTM or a theme snippet
- Old checkout scripts left in settings that no longer fire, or fire on page reload
- Values that include tax and shipping in one platform and exclude them in another
- Conversions API events sent without an event ID, so Meta counts them twice
How we set it up
Step by step, in the client's own accounts.
Pricing
Purchase tracking, enhanced conversions and the Meta Conversions API are in Essentials, $390 per store. Server-side tracking is part of Server-side & Privacy, from $1,490. Starts with a free tracking check.
See full pricing- 01Inventory every tagChannel apps, custom pixels, theme code, GTM, legacy checkout scripts and third-party apps, with what each one sends on a real test order.
- 02Choose one source per platformFor each of Google Ads, GA4 and Meta, we decide whether the native app, GTM with custom pixels, or a server setup is the source, and remove the rest.
- 03Fix the checkout eventsCheckout and purchase events through Shopify's customer events, so they keep working with the current checkout.
- 04Agree the valueTogether with the client we decide what a purchase is worth, gross or net of tax, shipping and discounts, and set it the same way everywhere.
- 05Set up the Conversions APIThrough the Meta app or server-side GTM, with event IDs that match the browser pixel so each order counts once.
- 06Add server-side where it paysFor stores where enough orders go missing, server-side GTM on a first-party endpoint, scoped and priced before we start.
- 07Test with real ordersTest orders through the full checkout, including discount codes and different payment methods, checked in every platform and written up in a test log.
Outcomes
Beyond the first purchase
Example signals. Which ones are worth sending depends on the store's margins, products and data, agreed with you first.
- Stage 1
Add to cart and checkout
Tracked for reporting and audiences, not as primary conversions.
- Stage 2
Purchase
One per order, with the agreed value and transaction ID.
- Stage 3
New customer
Marked where the platform supports it, for new-customer bidding goals.
- Stage 4
Refunds and cancellations
Adjusted in GA4 or Google Ads where the client wants net revenue reported.
Platforms covered
Works with the client's existing stack.
- Shopify
- Shopify Plus
- Google Ads
- Meta
- GA4
- Google Tag Manager
- Server-side GTM
- TikTok
- Klaviyo
- Consent Mode v2
Something else? Tell us which tools the client uses and we'll confirm before you pay.
What we do and don't claim
We're not affiliated with or endorsed by Shopify, Google or Meta. Shopify's checkout, customer events and channel apps change often, so we describe them generally here and check how the client's store is set up before recommending anything.
Shopify tracking: questions
5 questions
It depends on the store. The native apps are simple and maintained by the platforms, while GTM gives more control over values and events. What matters most is that each platform has one source, not two.
Usually duplicate tags, purchases counted on page reloads, or attribution differences such as view-through conversions. We find which it is on a real test order before changing anything.
Often it's a good base. We still check that it isn't running alongside a second pixel or a custom setup, that events are deduplicated, and that the values match.
For some stores, yes, for many, the native Conversions API is enough. We look at how many orders go missing in the free check and only recommend server-side if the numbers support it.
Yes, collaborator or staff access with permission for apps, customer events and themes. Everything stays in the client's own store and accounts.
Read more
Services used
Also see: HubSpot, GoHighLevel, WordPress, Webflow, CallRail
Got a client on Shopify whose numbers don't add up?
Send us one account. We review it for free and send a short video of what's working and what isn't.