How Are Duplicate Transactions Prevented?

Duplicate transactions are dangerous because they can cause double-crediting and overpayment of sales incentives. We provide different ways to protect against duplicate transactions.

For transactions having been imported with a "Unique ID" field:

• We will use this field to prevent other transactions with the same "Unique ID" from being imported
• If transactions are modified at the source, and re-imported (manually or automatically) with the same "Unique ID" data, the current transaction will be updated to reflect the latest changes (instead of creating a duplicate)

For transactions having been imported without an "Unique ID" field:

• We calculate a checksum using all mapped fields (note: we also offer the option to choose which fields should be used to generate this checksum)
• If transactions are re-imported (manually or automatically), transactions will be ignored if they match others with the same checksum (i.e. no duplicates will be created)
  

Unique IDs Must Be Unique

You should not map fields to the "Unique ID" category if not truly unique. For example, if a purchase and its corresponding refund transaction share the same ID, then you should NOT map this ID to the "Unique ID" category. Indeed, once the refund transaction is added, it would replace the purchase transaction in Sales Cookie.

• Related Articles

• What Are The Effects Of Duplicate Aliases?

  You should avoid duplicate aliases as they prevent proper crediting of transactions to users or teams. Duplicate user aliases are problematic in the following scenario: A transaction refers to the duplicate user alias in a field mapped as a "credit ...

• How Can I Find Duplicate Aliases?

  Here are the steps to identify duplicate aliases across users or teams: Login to your workspace On the left pane, click on "Aliases > Review Aliases" Click on the "User Aliases" or "Team Aliases" tab Check the "Only Duplicate" checkbox You will see a ...

• How Can I Export Transactions?

  Here are the steps to export transactions: Login to your workspace On the left pane, click on "Transactions > All Transactions" Search for transactions (more details) Customize field display to include columns you want in your export (more details) ...

• Who Can Import, Edit, Or Delete Transactions?

  Only full admins can import, update, or delete transactions. Limited admins cannot import, update, or delete transactions. You can also hide transactions from limited admins by editing workspace security settings. To learn more about different roles, ...

• How Many Transactions Can I Have?

  We will store the most recent 100,000 transactions for every workspace. Once this limit has been reached, transactions will be deleted (permanently) - starting with the oldest ones. If this is an issue, please contact our support team to request ...