Hi everyone,
I am writing to address a significant architectural flaw in how Wix currently handles the native Meta Conversions API (CAPI) integration for e-commerce. This design choice is causing severe tracking discrepancies and loss of ROAS for businesses operating on professional paid plans.
Currently, Wix triggers the server-side Purchase CAPI event exclusively when the Thank You Page renders in the browser. While this might be easier to link with the front-end pixel, it completely defeats the core purpose and advantage of server-side tracking.
The Problem
In modern e-commerce—especially in markets with asynchronous payment methods like Pix, Bank Slips (Boleto), or external gateway redirections—it is extremely common for a user to complete a payment and immediately close their browser tab or lose connection before the auto-redirection back to the Wix Thank You page happens.
When this occurs:
- The Meta Pixel does not fire (which is expected for front-end).
- The native Wix Meta CAPI also does not fire, because its execution is dependency-locked to the page load.
As a result, professional merchants are losing a massive percentage of their actual purchase data in Meta Events Manager, tanking their Event Match Quality and directly harming ad campaign optimization. Relying on a browser action to trigger a backend API is an obsolete practice that leaves data gaps.
As premium paying customers who invest heavily in ad traffic, we expect a robust, enterprise-grade e-commerce infrastructure that accurately reports our data, regardless of whether a customer closes a tab after paying.
I urge the Wix eCommerce product teams to review this integration and ensure that paid orders are tracked server-to-server based on the actual payment confirmation, not browser visits.
Is anyone else experiencing this data gap, or has the community found a way to make Wix address this natively?