Three jobs that should not be mixed up
One order can produce two purchase messages: one from the customer's browser and one from your server. That is not automatically double counting. The important question is whether both messages refer to the same purchase and can be recognized as copies.
Meta Pixel sends event information from the browser. Conversions API, usually called CAPI, sends it through a server integration. A click ID identifies the advertising interaction that preceded the visit. Start with the order record, then ask which messages describe it and which ad interaction they can be linked to.
What the browser can report
The browser can report that a page opened or a button was pressed. Whether the message is sent depends on your setup, the page's scripts, and the visitor's choices. A page-view event does not tell you that the whole page was read, and a Submit click does not tell you that the form reached your sales team.
Consider a hypothetical shop that sends Purchase whenever the thank-you page opens. A refresh sends another message about the old order. Before changing the tracking tool, change the question: what confirmed action should cause this event? Give the developer a precise answer, such as “the order service accepted this new order.”
What the server changes
Your server can know that an order was accepted even if the customer closes the browser before its message is sent. A CAPI integration can report that known action. It cannot establish that a purchase happened when the order system has no record of one.
Check the information handed to the integration: the event name, when the action occurred, which action it represents, and any required amount or currency. These are separate fields because they answer separate questions. A missing browser message is not a reason to invent a server event.
Also separate delivery from attribution. Delivery asks whether the message reached the receiving service. Attribution asks which advertising interaction gets credit for the purchase. A successful delivery response does not settle the second question.
One action can have two messages
Browser: Pixel
- Runs in the page context
- Reports the chosen event
- Depends on execution conditions
Server: CAPI
- Uses business-system information
- Reports the same action
- Needs correct event data
These are parallel reporting paths, not two successive purchases.
Deduplication is about the same event
Deduplication means treating repeated reports of the same action as one event. Imagine two receipts describing the same purchase: you need a way to recognize that they belong together, rather than adding their values as two sales.
In Meta's official integration toolkit, event_id identifies the event and event_name names its type. The toolkit describes using these together to match browser and server reports. In a hypothetical shop, both reports of one Purchase should carry the agreed identity for that purchase.
Do not give the two copies unrelated identities. Do not reuse one identity for every purchase by a customer either: that customer may buy again. A delivery retry still describes the original action; a second real purchase needs to remain distinguishable. Follow your integration's current matching rules when implementing this distinction.
- Purchase accepted
The order system confirms it.
- Identity assigned
Both reports refer to that action.
- Copies matched
A retry remains the same event.
A delivery retry refers to the original action; a new purchase must remain distinct.
Click context is not proof of conversion
A click ID helps answer “which advertising interaction preceded this action?” An event ID helps answer “which action is this message about?” Neither field is a substitute for checking that the order exists.
If click context disappears, trace it through the actual route. A redirect can rebuild the address without a needed parameter; an external browser or another service may receive different information. Find the first handoff where the value is missing rather than filling the gap with a made-up identifier.
Keep names, email addresses, and other personal information out of campaign URLs. Send only the information your measurement setup legitimately needs, and apply the visitor's relevant choices to both browser and server reporting.
Create an event register before adding another integration
Before adding another connector, list your existing events. For each, write down what it means in the business, which system confirms it, what starts each message, and who maintains the integration. “Purchase means a new order in this confirmed state” is more useful than an unexplained event name.
Then list every sender: a shop extension, a tag-management tool, and custom server code may all report the same action. Decide whether the new integration replaces a sender or works alongside it. Otherwise, installation can create duplicates without changing anything the customer sees.
During a migration, check both the old and new paths. Turning off a browser tag may leave a server sender running. Record when the definition or sender changed so a later jump in the chart is not mistaken for an improvement in advertising.
Distinguish a delivery retry from a new action
Suppose an order is accepted, but the integration receives no clear answer after sending its event. This hypothetical failure concerns the message's delivery, not whether the customer bought. Inspect the delivery record before sending anything manually.
A documented retry should continue to describe the original action. Creating a fresh purchase identity for every attempt can make one order look like several. Keep a record of who retried the message and which original event it belongs to.
When messages arrive late, compare the purchase time with the delivery time. Today's incoming messages may include yesterday's orders. Reconcile reports using the same time basis before treating the difference as lost sales.
Reconcile one test order before totals
Use the supported test facilities to create one clearly labelled order or lead. Find its business record, then inspect the browser and server messages that should describe it. Compare event name, identity, occurrence time, and the relevant amount and currency.
Test the failure paths next. An abandoned checkout must not become a confirmed purchase. Refreshing a result page or retrying delivery must not create another business action. A second genuine purchase must still be counted as a separate action.
Only then compare totals. Align the event definition, reporting period, time zone, and attribution settings. If a gap remains, investigate a few traceable orders; they will tell you more than trying to force unrelated dashboard totals to match.
- Business record
Confirm the chosen milestone.
- Trigger
Check the sending condition.
- Delivery
Find the message or error.
- Matching
Compare name and identity.
Start with a specific order and trace it toward the report.
Questions answered
Does CAPI replace the order database?
No. CAPI sends information about an action. Confirm that action in the system that accepts the order or lead.
Is a click ID the same as event_id?
No. The click ID points to an advertising interaction. The event ID distinguishes the action being reported, such as one purchase.
