An identifier arrived with another value

What was observed

Within one project-local day, a conversion's stable identifier arrived again under the same conversion name with a different value or currency, and the identifiers that did so were fewer than 1 in 100 of that day's distinct identifiers for the conversion.

TraceLog keeps one record per identifier, so the second order under that identifier is not counted as its own. Fewer than 1 in 100 bounds what that can change in a figure, so the row warns instead of withdrawing every figure. From 1 in 100 it is a duplicate conversion identifier, which blocks.

In the application the row names the day, how many identifiers arrived with another value and how many the day held. It never names the identifier itself.

Possible causes

• An order number given again to a new order: a sequence restarted, an order restored from a backup, or a store migration that reused old numbers
• An order edited after it was placed and sent again with its new total. On Shopify, WooCommerce and PrestaShop the app, plugin or module sends each order at checkout and again when it is paid, so an order edited before payment arrives the second time with its new total.

What to check

1. Look up the conversions of the day the row names in your own system, and find the identifier that two orders share.
2. Check that your system assigns each new order a number never used before.
3. If an edited order is sent again, send it with its original value, or do not send it again: the conversion was already counted.

Effect on verification

It warns and never blocks verification. The row clears once fourteen days pass without another identifier arriving with a second value.