Paid orders with no conversion: the missing thank-you page
The order is paid. WooCommerce has it, the money is in your account, and Meta, GA4 and Google Ads have never heard of it. A common reason is that the shopper never came back to the thank-you page, and that page is where your browser tags send the purchase. The fix is to send the purchase from your shop’s server when the order is paid, not when a page loads. Our guide to server-side tracking for online shops has the bigger picture.
Why the purchase depends on one page
In many WooCommerce shops, the pixels and tags send purchase from the order confirmation page. The tag runs in the shopper’s browser, so the purchase exists for the ad platforms only if that browser loads that page.
Plenty of paid orders never get there:
- The shopper pays in a payment gateway (an online transfer, a card form on the bank’s page) and closes the tab instead of clicking back to the shop.
- The connection drops after the payment, on mobile in particular.
- The shopper pays later. An order placed with a traditional bank transfer is paid days after checkout, when nobody is looking at your site. The thank-you page loaded at checkout, before anything was paid.
How to tell this is your problem
Compare paid orders with purchases in GA4 or Meta for a closed week, by payment method. Our article on why GA4 shows fewer orders than WooCommerce has the full comparison. If the missing orders gather around methods that send the shopper away from the shop, or around transfers paid days later, the thank-you page is the gap. If they are spread evenly across methods, look first at ad blockers and consent.
Why a server container alone doesn’t fix it
A server-side container (server-side Google Tag Manager, for example) moves the requests to the platforms from the browser to a server. It still gets the purchase from the same browser tag on the same thank-you page. No page, no request to the container, nothing to forward.
What fixes it is a purchase that starts from the order itself, on your shop’s server: WooCommerce marks the order as paid, and the shop sends the purchase. The shopper’s browser plays no part at that moment.
What a purchase from the server needs
Sending it is the easy part. Four details decide whether it counts, and counts once:
- The right moment. Send when the order becomes paid or moves to processing, once per order. Sending at checkout would count orders that are never paid; waiting for “completed” would wait for shipping.
- The time of payment. The purchase should carry the time it was paid. GA4’s Measurement Protocol records an event at its own time only up to 72 hours back, and Meta accepts events up to 7 days old. A transfer paid three days after checkout still fits Meta’s window, but not GA4’s, if the event carries the time of checkout.
- The shopper’s consent and identifiers. The server knows the order, not the browser. Consent, the
_fbpand_gacookies and the click IDs have to be saved with the order at checkout, while the shopper is still on your site. Without the identifiers the platforms tie fewer orders to the ad, and without consent nothing should be sent. - One copy per platform. When the thank-you page does load, the browser tag sends the same purchase too. Both copies need the same ID, or the order counts twice. How Meta matches the Pixel and the server copy is a separate article.
How TallyHost does it
The TallyHost plugin for WooCommerce saves the shopper’s consent in the order at checkout and, as far as that consent allows, the browser identifiers, IP and user agent, both the classic and the block checkout. When the order is paid, or moves to processing or completed, whichever comes first, it sends the purchase once, in the background, with the time of payment. Checkout never waits for it. GA4 gets only the copy from the server. For Meta, TikTok and Google Ads, when the browser sends the purchase too, that copy waits up to 15 minutes for the one from the server, and the server copy wins if it arrives in that time. A transfer paid later goes out from both sides, and Meta counts it twice: both copies come through the Conversions API, and Meta doesn’t merge two server copies.
Some orders still don’t go out, on purpose. Orders placed before the plugin was activated aren’t sent. A shopper who declined consent at checkout stays declined in the order. GA4 also needs the _ga identifier, which exists only with analytics consent. The debugger shows each purchase, where it went and why it was skipped, so you can see which case an order falls into.
Send your shop's orders from the server
TallyHost reports paid orders with consent checked, to Meta, TikTok, GA4 and Google Ads. Free up to 100,000 events a month.
Start free