Clarvivo

Free tool by Clarvivo · no login

Find repeated transaction IDs before they inflate purchase reporting

Upload a purchase export to detect duplicate and missing transaction or order identifiers.

Purchase or transaction export

Upload an ecommerce or GA4 export with transaction/order IDs. We find repeat and blank IDs that can inflate purchase reporting.

This tool answers: Which transaction IDs are repeated or missing in my purchase export?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

A repeat purchase event can quietly inflate revenue in GA4 and ad platforms while the store remains correct.

Transaction IDs make repeat firing measurable, but only when every row carries a stable identifier.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. Locate common ID columns

    Transaction, order and purchase ID aliases are recognised.

  2. Count repeats and blanks

    The output provides row-level evidence without retaining the source file.

Common causes and fixes

Confirmation page replay
Refresh or revisit emits a second purchase.
Two tags report one order
Theme code and a tag manager both send purchase.

Frequently asked questions

Is a duplicate always invalid?
It is a critical signal unless the export intentionally contains multiple event types per order.
What IDs work?
Transaction ID, transaction_id, order ID and common aliases.

Make every revenue event answer to an order.

Clarvivo reconciles tracking claims with payment truth.

Trust transaction-level revenue

What this tool reads, and what it keeps