Fixing broken pixel attribution in WooCommerce

If WooCommerce sales are missing from Meta or Google, the usual cause is a custom thank-you URL the purchase event was never set up to fire on. The order completes, but the conversion never reaches the ad platform, so it optimises against incomplete data. To diagnose it, run a real test order with the platform's event-testing tool and check whether the purchase event fires on the page the customer actually lands on. To fix it, re-fire the purchase event on that landed URL with the real order values.

The symptom

WooCommerce reports more sales than Meta or Google does. The gap is not random — it tends to appear after a checkout or thank-you-page change, and it grows as more of your traffic flows through the affected path. Because the ad platforms optimise spend against the conversions they can see, missing events do not just under-report; they steer your budget toward the wrong audiences.

The usual cause: a custom thank-you URL

The purchase event — the one that tells Meta or Google a sale happened — is typically wired to WooCommerce’s default order-received page. When a checkout plugin or a custom setup sends customers to a different thank-you URL, that event is often left behind on a page they never reach. The order is real; the signal is lost. This is one of the most common reasons a WooCommerce pixel appears to “stop working” after a checkout change. [VERIFY: cite Meta pixel docs at publish.]

How to diagnose it

  1. Open your platform’s event-testing tool (Meta and Google both provide one).
  2. Complete a real test order through your live checkout.
  3. Watch for the purchase event on the page you actually land on after paying.

If the event does not appear there, it is firing on the wrong page or not at all. [Platform tools change — check the current documentation for the exact testing steps.]

How to fix it

The fix is to re-fire the purchase event on whatever thank-you URL the customer lands on, sending the real order values rather than a placeholder. Done properly it covers each platform you advertise on — Meta, Google, TikTok — so the redirect no longer strips the conversion.

Server-side conversion APIs can complement this, but they solve a different problem (browser blocking) and still need the correct event data; getting the on-page event right first is the foundation.

How Asteris Cart helps

The Pixel Bridge module re-fires the canonical purchase event on custom thank-you URLs for Meta, Google and TikTok, with the real order values. The reasoning behind the approach is in the wedge essay. Why the pixel survives custom URLs → · See pricing →

FAQ

Why are my WooCommerce purchases missing from Meta Ads Manager? Usually a custom thank-you URL the purchase event was not set up to fire on.

How do I check if my pixel is firing on purchase? Run a real test order with the platform’s event-testing tool and watch the page you land on.

How do I fix attribution on a custom thank-you page? Re-fire the purchase event on the landed URL with the real order values.

Sources