wesaw
FRGet started

Why Meta counts your purchases twice

Your store recorded 30 orders and Meta reports 47 conversions. Duplicate emissions are one possible explanation, not a conclusion from those totals alone. This page explains the evidence to check before changing your setup.

Meta counts a purchase twice when the same sale reaches it by two routes, the browser pixel and the Conversions API, with nothing marking them as one event. Deduplication relies on an event identifier shared by both reports. If the two differ, even only in capitalisation, Meta sees two separate purchases.

How do you confirm you are counting twice?

A total close to twice the order count is a reason to investigate, not proof of double counting. Align the period, time zone and report scope, then inspect the browser and server events for specific orders: their event names, event identifiers and emitting integrations.

Use Events Manager's diagnostics as additional evidence. A Multiple integration label shows that both routes exist; it does not prove that each order was merged. The absence of a diagnostic does not prove that deduplication succeeded.

Why send it twice at all?

The two paths can provide complementary evidence when the event is eligible for each. A browser emission may be blocked or unobserved. Server delivery can also be withheld, fail or remain pending. In wesaw, sending to Meta from the server requires recorded consent to be granted.

Identify independent purchase senders before changing anything. For the browser/server pair you retain, verify matching event names and event identifiers; do not send an event simply to complete a pair.

What breaks the join?

The shared identifier, almost always. It has to be the same string on both sides and it is case sensitive, so one route sending an uppercase form joins nothing. It also has to be derived from the sale rather than from the moment: an identifier built from a timestamp gives two different values to two reports of one order, and merges two genuinely separate events that happened in the same second.

For a purchase the order number is the natural choice, because it is the one value both halves can see and neither has to guess.

Does switching the pixel off fix it?

Disabling a duplicate sender can remove an extra emission, but the correct change depends on which integrations produced the events. First identify each source and the event identifiers it uses. Our test-store EMQ readings of 8.0 and 9.3 do not establish the effect of removing a pixel from another store.

What actually joins the two reports

  1. Give both reports of one sale the same event identifier, derived from the order rather than from the time it happened.
  2. Keep it a string and keep its capitalisation identical on both sides. A lowercase and an uppercase form of the same value are two events.
  3. Inspect the result and diagnostics in Events Manager. Multiple and an absence of warnings alone do not establish a per-order merge.
  4. Check a small set of known orders and preserve the evidence and sample size. A successful sample is not a measured merge rate for every conversion.

Sources

  • Meta documents deduplication between pixel and server events as resting on a shared event ID, and states that it is case sensitive.Meta for Developers
  • On our own test store, three test orders reported from both the browser and the server produced three Purchase events and not six, with the integration shown as Multiple and no unmerged-event diagnostic, checked on 21 August 2026.wesaw, own test store

The terms on this page

What wesaw does about it

Last reviewed: