Why your WooCommerce pixel breaks on custom thank-you URLs

Q: Why does my Facebook pixel stop tracking purchases after I add a custom thank-you page?

Many checkout plugins redirect to a custom thank-you URL that the pixel's purchase event was not set up to fire on. The order completes, but the purchase event does not reach Meta or Google, so attribution breaks.

Q: How does Asteris Cart keep attribution intact?

Asteris Cart re-fires the canonical purchase event on whatever thank-you URL the customer actually lands on, so Meta, Google and TikTok receive the conversion regardless of the URL.

Q: Which platforms does it support?

The Pixel Bridge module re-fires purchase events for Meta, Google and TikTok.

Custom thank-you URLs are the most common reason WooCommerce checkout plugins break Meta and Google purchase tracking. The standard purchase event is wired to the default order-received page; move the thank-you page to a custom URL and the event often never fires, so the order completes but the conversion never reaches your ad platform. Asteris Cart's Pixel Bridge re-fires the canonical purchase event on whatever thank-you URL the customer actually lands on, for Meta, Google and TikTok — so attribution survives the redirect.

A sale that your ad platform never sees

You run a checkout plugin, you point the thank-you page at a nicer custom URL, and everything looks fine — orders complete, customers are happy. Weeks later you notice the numbers do not add up: WooCommerce shows the sales, but Meta and Google report far fewer conversions than you made. The ad platforms are optimising against incomplete data, and you are paying for it.

The cause is usually mundane. The purchase event — the one that tells Meta or Google a sale happened — was set up to fire on WooCommerce’s default order-received page. When a checkout plugin redirects to a custom thank-you URL, that event is often left behind on a page the customer no longer reaches. The order is real; the signal is lost.

What Asteris Cart’s Pixel Bridge does

The Pixel Bridge module treats the thank-you URL as variable, not fixed:

It re-fires the canonical purchase event on whatever thank-you URL the customer lands on, so the redirect does not strip the conversion.
It covers Meta, Google and TikTok purchase events.
It fires the real order values, so the platforms receive an accurate conversion rather than a guess.

Code receipt: src/Checkout/Pixel_Bridge.php [CODE SNIPPET — CC to insert the relevant Pixel_Bridge logic from src/ at build; must match shipping v1.0.]

Why this is the wedge

Attribution is where checkout customisation quietly costs money. The prettier checkout flow that uses a custom thank-you URL is exactly the change that breaks tracking, so store owners are forced to choose between a good post-purchase experience and accurate ad data. Asteris Cart’s position is that you should not have to choose: the canonical event re-fires wherever the customer ends up. [VERIFY: cite Meta pixel debug behaviour + public reports at publish.]

How this fits

The Pixel Bridge is one of 22 Asteris Cart modules and one of the six wedges. It pairs with the Thank-You Page module, which is where custom thank-you URLs are configured in the first place. See the Pixel Bridge module → · See the Thank-You Page module → · See pricing →

FAQ

Why does my Facebook pixel stop tracking purchases after I add a custom thank-you page? The purchase event was wired to the default order-received page; the custom URL is not where it fires, so the conversion is lost.

How does Asteris Cart keep attribution intact? The Pixel Bridge re-fires the canonical purchase event on whatever thank-you URL the customer lands on.

Which platforms does it support? Meta, Google and TikTok purchase events.

Sources

Asteris Cart code receipt: src/Checkout/Pixel_Bridge.php
Pixel behaviour on custom URLs: Meta pixel docs [attach cite at publish]