Shopify Conversion Tracking for Third-Party Checkouts
A one-click checkout takes payment on its own page and creates the order in Shopify afterwards. The sale is real, but the browser purchase tag never fires, so Google Ads stops seeing it and bids against the wrong number.
We move the purchase off the browser. The Google click id is recovered from each Shopify order and sent server side, so the checkout app no longer matters to tracking.
The customer pays inside Fastrr, Shopflo or another checkout app. Shopify receives the order, but its thank-you page never loads.
2
Click id recovered
We recover the Google click id for every paid order, from data Shopify already holds but no standard integration reads.
3
Sent server side
The purchase goes to a Stape server-side Google Tag Manager container on your own subdomain, built so Google can match it.
4
Google counts it
The Google Ads conversion fires with the order value, the order id for deduplication and the items bought.
5
Refunds follow
Cancelled and refunded orders come back off the total, so revenue in Google Ads is not overstated.
What we set up
Stape server-side Google Tag Manager container on a first-party subdomain
Order sync that recovers the Google click id from each Shopify order
Purchases sent only for orders with a verified Google click id
Refund and cancellation handling
Audit of every conversion action, with fake or page-view actions removed
Storefront tag clean-up: duplicate containers, double-counting server tags, idle apps with payment access
Request-level proof on a traced order, then a comparison against Google-clicked orders
We do not publish how the click id is recovered or what the server tag needs to match a sale. That is the part stores pay for. What we will do for free is check your store and tell you whether the fix is possible on it.
What goes wrong, and what we do about it
One-click checkouts like Fastrr and Shopflo take payment on their own page and push the order into Shopify afterwards. Sales keep coming in. The tracking that tells Google and Meta which ad made them stops working, and nothing in either dashboard says so.
Google Ads shows far fewer purchases than Shopify since you added a one-click checkout.
The customer pays on the checkout app's page and never reaches Shopify's thank-you page, so the browser purchase tag never fires. The order still lands in Shopify, created through the API.
We move the purchase off the browser and send it to Google from a server, through a Stape server-side Google Tag Manager container on your own subdomain. Refunds follow the same route, so cancelled orders come back off the total.
288 of 307 orders in one week went through the third-party checkout on a womenswear store. Over the first three clean days, Google recorded 105% of the value of its own clicked orders, inside our ±20% bar.
Shopify's own reports cannot tell you which ad sold the order either.
Orders created by a checkout app arrive with an empty customer journey: no first visit, no landing page, zero sessions. Shopify agrees with the wrong number, which makes the gap look normal instead of obvious.
The click id is usually not lost, but it is not where any standard integration looks for it. We recover it for every order and attach it to the conversion we send, and we check that it is recoverable on your store before quoting.
Server-side purchases fire, return 200, and never appear in Google Ads.
The server-side Google Ads tag expects something a browser normally supplies and a server does not. Without it the tag fires, reports success, and has nothing to match the sale against. There is no error anywhere, and for most of a day it looks like reporting lag.
We build every server event so Google can actually match it, then verify at request level: the outgoing conversion request must carry the click id, the value and the order id before we call it working.
Three test orders. Only the one carrying the cookie converted.
Conversions climb above your real Google orders after switching on enhanced conversions.
A hashed email matches an order to any past Google ad click, so sales that came from Meta, organic search or a free listing get credited to paid search. Return on ad spend looks better than it is, and budget follows it.
We only send orders carrying a verified Google click id. Email and phone ride along as enrichment on those rows, never as the only match. The number is smaller, and it is real.
Email-only orders pushed conversions to 1.22x the Google-clicked orders within a day. Restricting to click ids brought it back under 1.0.
A conversion action reports hundreds of thousands of purchases.
Old conversion actions left behind by earlier setups, counting page events that are not sales. Smart Bidding optimises toward whatever is marked primary, fake or not.
We audit every conversion action against real Shopify orders, remove the ones counting page events, and leave a single primary purchase action for bidding.
One action had booked 674,022 conversions worth ₹6.42 crore on a store taking a few dozen orders a day.
Someone tells you 60% of your conversions are missing.
They compared Google conversions with all orders. Only orders that clicked a Google ad are Google's to count. The rest came from Meta, direct or organic search and were never going to show up there.
We split orders by their real source, read from the landing URL rather than UTM tags carried over from an older visit, and measure Google against Google-clicked orders only. We tell you before starting whether fixing tracking will raise the number or just make it true.
49% of orders on that store carried a Google click. The job was a number the owner could trust, not a doubled one, and we said so up front.
Your storefront loads tracking nobody remembers adding.
Checkout and theme apps get write access to theme code and payments, and keep it after they stop being used. Menu and upsell apps inject their own Tag Manager containers. Server tags get switched on next to Shopify's native Meta Conversions API and count every sale twice.
We list every container and script per page view, remove the duplicates, pause server tags that double-count, and flag idle apps that still hold theme or payment access.
Seven Google containers on every page view, one injected by a mega-menu app, and a second checkout app with theme and payment access that had taken zero orders.
Why does Google Ads show fewer sales than Shopify after installing Fastrr or Shopflo?+
One-click checkout apps take payment on their own page and create the order in Shopify through the API afterwards. The customer never reaches Shopify's thank-you page, so the browser purchase tag never fires. The sale is real and Shopify has it; Google simply never hears about it. On one store we measured, 288 of 307 orders in a week went through the checkout app.
Can the Google click id be recovered from a third-party checkout order?+
Usually, yes. Orders from checkout apps arrive with an empty Shopify customer journey, but the click id can usually still be recovered from the order. We check this on your store before quoting, because it decides whether the fix is possible at all.
What is server-side tracking on Shopify, and do I need Stape?+
Server-side tracking sends the purchase from a server instead of the shopper's browser, so it works even when the thank-you page never loads. We run it through a Stape server-side Google Tag Manager container on your own subdomain, fed from your Shopify orders. If every order goes through Shopify's native checkout and your numbers already match, you may not need it.
Will fixing tracking increase my conversions in Google Ads?+
Not necessarily, and we say which before we start. Only orders that clicked a Google ad are Google's to count; on one store that was 49% of orders, and Google was already seeing most of them. There the result was a number the owner could trust, not a bigger one. Where Google is genuinely missing sales, the count goes up.
Should I switch on enhanced conversions?+
Only as enrichment on orders that already carry a Google click id. Matching on hashed email alone credits sales that came from Meta, organic search or free listings to paid search. On one store, email-only matching pushed conversions to 1.22x the real Google orders within a day, which makes return on ad spend look better than it is.
How do you prove the tracking fix actually works?+
At request level first: the outgoing Google Ads conversion request must carry the click id, the value and the order id. Then against the business: we compare what Google records with the value of orders that came from Google clicks, and agree a tolerance before starting. On one store the first three clean days came in at 105%, inside a ±20% bar.
Free tracking check
Tell us the store and the checkout app. We look at your checkout and what your storefront tags are doing, and tell you whether the click id is recoverable and whether fixing it will change your numbers. No charge, no obligation.
Free Quote • No Obligation
Get Your Shopify Store Quote
Tell us what you sell. You get a written scope, a timeline and a fixed price — not a sales call about it.
