How-To: Ignore Duplicate Transaction IDs
Updated on Sep 09, 2016
This article covers:
- Ignoring Duplicate Transaction IDs
- Choosing which Transaction ID Duplication option that is best for your situation
Ignoring Duplicate Transaction IDs is configured per Event at the Advertiser level and DOES NOT allow duplicate transaction ID's to be passed when firing an Event pixel. This feature works in conjunction with "Allow Duplicates", which lets Events fire multiple times on the same session. With both features on, multiple events in the same session with a duplicate unique transaction ID will prevent the event from converting the second time around, though events with non-duplicate ID's can still convert on the same session. This option to dedup based on the events transaction ID's can be established across all events from the advertiser or across just a single offer's events.