Duplicate conversion identifier
One stable identifier arrived with conflicting data, or was reused across several visits. Verification is blocked until each identifier names one conversion.
What was observed
Within one project-local day, one stable identifier arrived in one of these ways:
- under the same conversion name, with a different value or currency
- under another conversion name
- from three or more separate browser visits, each with a declared step before the conversion
A retry or a reopened confirmation page that repeats the same name, value and currency does not raise this row.
Use one stable identifier for one conversion record and keep its value consistent.
Possible causes
- A confirmation page that fires the conversion on every render, including a refresh, with a different conversion name each time
- Two installations on one site — a tag manager and a hard-coded snippet, or a plugin left active beside a manual install
- An identifier that is not actually unique in your own system: a cart id reused across orders, or a per-day sequence number
- A fixed value sent where the identifier should be —
undefined, a template variable that never resolved, the form's own name — so every order arrives under one identifier, visit after visit
What to check
- The row names the conversion it concerns. List every place your code sends that conversion, and the identifier and value each one sends.
- Remove the second installation if there is one — two installations on a page double everything, not only this row.
- Confirm the identifier is unique in your own database. If it is not, use the field that is.
- Fire the conversion once per completed order, not once per view of the page that shows it.
- If every conversion carries the same identifier, the variable behind it is not resolving. Send the order number itself.
Effect on verification
It blocks. Nothing built on those records is published until each identifier names one conversion again.