Meta Ads
Working
wesaw reports sales to Meta through the Conversions API, from its servers rather than the shopper's browser. Your existing pixel keeps running; Meta matches the two on a shared event identifier so a sale seen by both is counted once.
Does wesaw replace the Meta pixel?
No, and Meta does not recommend replacing it. The pixel still sees browsing that never reaches the shop's server. The two are designed to run together, which is why the shared event identifier exists.
How is double counting avoided?
Both reports of the same sale carry the same event identifier, derived from the order ID, as the same case-sensitive string. Meta deduplicates on it. Because the identifier comes from the order rather than from a random draw, replaying the same purchase produces the same identifier and no second sale.
What match quality does it reach?
On our own test store, 8.0 out of 10 on purchase events, read from Meta Events Manager on 18 August 2026, with fourteen match parameters attached where a default setup attaches four. That is a measurement of our store, not a promise about yours.
Last reviewed: