
Measurement
Part of Programmatic conversion tracking
Separating duplicate conversions from repeat purchases
Use transaction IDs, order status, event paths and counting methods to distinguish repeated records from genuine new purchases.
undefined
Treat the order, not the customer, session or day, as the unit for purchase counting. A duplicate is another record of the same order; a repeat purchase is a distinct completed order. Start with the order ledger and order IDs, then check status before changing the conversion total.
Identify the order being counted
Give each order a stable ID and pass it with the purchase event wherever the source supports it. Compare that ID with the first-party order record: repeated records with the same ID are candidates for duplicate handling, while different IDs can represent separate orders. Confirm that each distinct order was completed and valid; a customer ID identifies a person, not an order.
Define the counted action as a completed order and retain order status alongside the event. A cancelled order is not a completed purchase under that definition; record a full or partial refund as an adjustment to the order, rather than treating the refund as another purchase. Keep gross completed-order counts distinct from net revenue so the reporting rule is explicit.
Use the order ledger to classify the patterns. If one order ID appears repeatedly for one completed order, inspect reloads, retries and repeated triggers before suppressing a record. If different order IDs map to distinct completed orders for the same customer, retain both; if one ID carries different values or a changed status, resolve the order update, cancellation or refund before reporting.
Do not remove an event solely because its customer, session or date matches another event. Make the counting decision from order identity and status, not a similarity signal.
Trace the purchase event
Trace each event against the first-party order record. Compare order ID, event time, source and value, then inspect the confirmation-page trigger, retries and duplicate deployments. Preserve the original event and order status while diagnosing; this helps distinguish a repeated transmission from a changed or refunded order.
Name the reporting route before testing: for example, a GA4 purchase event can be sent using the GA4 Measurement Protocol. In GA4, inspect the purchase event's transaction_id parameter; it helps avoid duplicate events for a purchase (Google Analytics). Compare it with the first-party order ID rather than assuming that the same customer or session means the same order.
Then check the platform's configured counting method and confirm what it counts against the order definition. A user- or session-based limit can hide a valid separate purchase, while counting every event can expose repeat firing. Do not change settings until you know whether the problem is a repeated event for one order or an omitted distinct order.
GA4's guidance says not to send an in_app_purchase through the Measurement Protocol if it duplicates an event sent by the Google Analytics for Firebase (GA4F) SDK; Google Analytics does not automatically detect or remove duplicate in_app_purchase events (Google Analytics). For a standard purchase, use transaction_id as a duplicate-avoidance aid, but verify the order records and the platform's actual configuration before treating a record as suppressed.
Correct the cause
Correct the cause for the diagnosed pattern. If one completed order fires repeatedly, fix the trigger or retry path, retain the same order ID for that order, and test that it still reports once. If one order appears from multiple sources, reconcile records to the order ID and use only a deduplication method that the receiving platform supports; do not assume cross-platform ID matching is automatic. Keep distinct completed orders.
Record the affected activity, time period and correction time, then compare subsequent events with order status and IDs before closing the issue. Check cancellations and refunds separately from duplicate firing, including partial refunds, and state whether the reported metric is completed orders or net revenue. A lower total after a configuration change does not by itself prove duplicates were removed; valid repeat purchases may also have been excluded.
Key Metrics and Configuration Guidelines
- Valid Completed Orders
- Count only orders with 'completed' status
- Refunds & Cancellations
- Record as adjustments, not new purchases
- GA4 Transaction ID
- Use as duplicate avoidance aid; verify against first-party records
- Gross vs Net Reporting
- Keep separate: gross for order count, net for revenue



