CAKE Knowledge BaseCAKE For Networks Setup & SettingsHow-To: Ignore Duplicate Transaction IDs

How-To: Ignore Duplicate Transaction IDs

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.

Enabling the Feature

1. Navigate to the Advertiser card for which you would like to change the event deduplication settings.  

2. Open the Events tab.

3. Select a specific Event.

4. Enable "Allow Duplicate".

5. In the drop down for Ignore Duplicate Transaction ID's, select either By Advertiser or By Offer based on how you would like to dedup the events. For additional information on these options please see below.

Ignore Duplicate Transaction ID's: Disabled vs. By Advertiser vs. By Offer - Which to choose?

When Ignoring Duplicate Transaction ID's you will be presented with three options in the dropdown field. These three options are outlined below in greater detail so that the most applicable option for your needs can be established on the event.

Disabled: Allow duplicate transaction ID's across the board for all offers under this Advertiser. This will essentially pretend this feature doesn't exist.  All events fire normally regardless of the value passed in the "&t" parameter.

By Advertiser: Do not allow duplicate transaction ID's for ANY offer under this Advertiser.

Example: Offer ID 1 fires Event ID 10 for a user and provides a transaction ID of 12345. If Offer ID 2 Event ID 10 fires with transaction ID 12345 then this conversion will be considered a duplicate.

By Offer: Do not allow duplicate transaction IDs for a single offer under this Advertiser.

Example: Offer ID 1 fires Event ID 10 for a user and provides a transaction ID of 12345. If Offer ID 2 Event ID 10 fires with transaction ID 12345 then this conversion will be stored. If Offer ID 1 fires Event ID 10 and provides the transaction ID 12345 again then this conversion will not be stored as it will be counted as a duplicate.

0 Comments

Add your comment

E-Mail me when someone replies to this comment