WooCommerce Conversion Tracking for Google, Meta and Microsoft

Below: what each platform needs, the double counting problem, the value problem, and a test plan that takes half an hour.

Almost every WooCommerce tracking plugin fires when the order received page renders. That page is a reasonable proxy for a purchase and it is not the purchase, and the difference shows up as missing conversions in four specific cases.

• The customer never sees itAn off-site payment can leave the customer on the provider's page, or they close the tab once the payment confirms. The order exists in WooCommerce; the page never rendered, so nothing fired.
• The page is cachedIf a cache layer touches the order received page, tags fire against stale content or the page is served without the order details at all.
• The order is paid laterBank transfer, invoice and pay-on-delivery orders are paid days after the page rendered, and some of them are never paid. A thank you page event counts them all as revenue on day one.
• The refund is invisibleA tag fires once. The return three weeks later exists only in WooCommerce, so the campaign keeps revenue the customer sent back.

None of that makes plugins useless. It means the purchase is the one event worth moving off the page, and WooCommerce gives you the mechanism for free.

• A plugin per platform

  Install, paste the conversion ID, done in ten minutes. Each plugin knows only its own platform, so you get one number per platform and no way to reconcile them. Fine for a store buying on one channel.

• A data layer plus a tag manager

  One purchase event in the data layer, several tags reading it. One place to change things and one definition of a purchase, at the cost of a container somebody has to own. Still a browser event.

• The order by webhook

  WooCommerce, Settings, Advanced, Webhooks: pick the order topic, paste a delivery URL, save. The paid order leaves your server with its total, currency and status, and no browser is involved.

Two details apply to all four. The click ID has to survive your landing page: a redirect, a cache rule or an aggressive parameter strip can remove gclid or msclkid before anything stores it. And the value has to carry its currency, or a multi-currency store teaches every platform that 40 and 4,000 are the same order.

Once tracking works, the counts are too high rather than too low, and there are two separate causes that look identical in a dashboard.

• One platform counting an order twice. A tracking plugin and a server-side feed both sending the purchase, with no shared event ID. The fix is configuration: one owner per platform, or the same event ID on both paths.
• Several platforms counting the same order. Each claims a purchase it can attribute to itself inside its own window, and a shopper who touched three campaigns satisfies three platforms. There is no configuration that fixes this, because none of them is wrong. Count the order once, from the order list, then choose a model.
• Order status changes firing again. A tag or webhook bound to order updated rather than a single paid state can fire on every status change, so one order becomes three conversions as it moves from processing to completed.

That third one is specific to WooCommerce and specific to webhooks, and it is the first thing to check if a store's conversion count is a clean multiple of its order count.

1. List what is already firing. Every tracking plugin, the tag manager container, any theme snippet. Most stores find a forgotten pixel from a previous agency.
2. Place one test order per payment method, including wallets and express buttons, and watch what each platform receives.
3. Check the order received page is excluded from caching, along with cart and checkout.
4. Place a bank transfer order and leave it unpaid. If a conversion is reported anyway, your trigger is the page rather than the payment.
5. Refund a test order and see whether anything downstream hears about it. Usually nothing does, which tells you where the revenue number will drift.
6. Compare one month of platform conversions against your order list, per platform and in total. Fix duplicates inside each platform, and stop adding the platforms together.

A sensible default for a store buying on more than one channel, in the order you would build it.

• Keep a browser layer for behaviourPage views, product views, add to carts. GA4 through a tag manager is the cheapest way to have it, and it is the half of measurement that genuinely belongs in the browser.
• Move the purchase to the orderOne webhook on the paid state, delivering the order with its total, currency and status. That becomes the number you reconcile everything else against.
• Send the order back from thereGoogle, Meta and Microsoft all accept conversions from a server, with a value and a click ID. Sending them from the order means the value is real and the refund can correct it.
• Tag every link you publishNo method invents a source that was never in the URL. Paid, bio, email, affiliate and partner links, every one of them.

Next to this one: WooCommerce order attribution and why it says Unknown. The same job elsewhere: Shopify conversion tracking and Shopware server-side tracking. On the product side, the WooCommerce integration, conversion tracking software, offline conversion tracking and the Meta Conversions API. On the concepts, GCLID explained and UTM parameters.