Why this matters
If you send duplicate events without proper deduplication, your revenue and conversions are inflated. Using Order ID correctly gives you:- Clean reporting
- Accurate attribution
- No duplicate purchases or payments
What is Order ID?
The Order ID is the unique ID your platform assigns to a transaction.
When you send events with an Order ID, Cometly uses it to decide whether the event is new or a duplicate.
Where you set it
- Webhook and integration events: in the event’s mapping step, map your data to the Cometly field Order Id. The related fields Order Name and Idempotency Key are mapped the same way.
- API events: send
order_id(and optionallyorder_nameoridempotency_key) in the request body. See Create Event.
How Order ID deduplication works
When an event is received, Cometly checks: “Have I already seen this event name + Order ID for this customer?”- If yes: the event is treated as a duplicate. It is ignored completely and no updates are made.
- If no: the event is recorded normally.
- First in wins. The first event received is the one that counts. Later duplicates are dropped.
- No updates happen. Amounts, fields and properties are NOT updated. The original record stays unchanged.
Shopify exception (upsells)
There is one exception, and it applies only to the direct Shopify integration (not to webhooks you set up in your Shopify store):- If a duplicate purchase event comes in with a higher amount,
- Cometly updates the original event amount.
Deduplication priority order
If multiple identifiers are present, Cometly uses this priority:Example
If you send:Purchasewith Order IDABC123ClosedWonwith Order IDABC123Upsellwith Order IDABC123
What this means
If your integration sends multiple event types for the same transaction:- Revenue is counted multiple times
- Conversions are inflated
Common use cases
Use case 1: Simple purchase tracking
- Send one Purchase event per transaction
- Include the Order ID
Use case 2: Track total order value (booked revenue)
- Send
Purchasewith the full order amount
- Ecommerce
- Tracking total order value at checkout
Use case 3: Track revenue from deals (sales teams)
- Send
ClosedWonwhen a deal is finalized
- B2B and sales-led companies
- CRM-based pipelines
Use case 4: Track additional revenue (upsells)
- Send
Upsellevents when additional revenue is added after the initial purchase
- Post-purchase offers
- Add-ons or upgrades
This is a separate event type, not a duplicate. It counts as additional revenue.
Use case 5: Force separate events (advanced)
If you need multiple events with the same Order ID to be treated as separate:- Add different Idempotency Keys
The key takeaway
- Order ID prevents duplicates within the same event type
- The first event wins, duplicates are ignored
- Different event names = separate conversions
- Choose your event strategy carefully to avoid inflated data
Frequently asked questions
Is Order ID required when I send events to Cometly?
No, Order ID is optional. Without it, Cometly falls back to the Order Name, and then to a time window (1 day for purchases, 1 week for other events). Send an Order ID with every transaction event, so duplicates are matched on the transaction itself and not on timing.How do I remove a duplicate conversion that Cometly already recorded?
Delete it from the contact’s Timeline: open the contact, click the three-dot menu next to the conversion and click Delete. Deleting cannot be undone. See Edit or delete a conversion on a contact, and add an Order ID at the source so the duplicate does not come back.Can I use the Meta pixel event ID as the Idempotency Key?
Yes. You can take theevent_id from the Meta browser pixel and send it as the idempotency_key on an API event. When that conversion is attributed to a Meta ad, Cometly sends the same value to Meta as event_id, so Meta can deduplicate it against the browser event.
Next steps
- Send an event with an Order ID through the API
- Learn the two ways to send event data to Cometly
- Edit or delete a conversion on a contact
- See how standard and custom events work