Support Questions:How does the Transaction ID work with conversions
From HasOffers
Each click is assigned a Transaction ID. The value of this ID is set as a preference in your application tracking settings. However, over the Company tab and click Tracking settings.
The ad server does not allow conversions with duplicate transaction IDs unless specifically enabled on an offer. Thus, if the a user created a conversion with the Transaction ID of 123456789 and then 10 minutes later completed the offer again and the conversion pixel was displayed with the user has the same Transaction ID set of 123456789, then this second attempt would be a duplicate conversions and won't be recorded.
Below are the three different methods for how the ad servers generate Transactions IDs:
Random Number - Each time a user clicks on a tracking link or loads an impression pixel, they are assigned a random number for the value of their Transaction ID. Using Random Number records all conversions from unique sessions (random number as transaction ID). Random Number doesn't provide any protection against duplicate transaction by the same user.
IP Address / Date - Each time a user clicks on a tracking link or loads an impression pixel, they are assigned a number comprised of their IP Address and the current date for the value of their Transaction ID. So if a user's IP Address is 123.123.123.123 and today's date is 2010-06-05 then their transaction ID will be 12312312312320100605. Note the the time is actually a unix timestamp and not just the year-month-day. Thus, each time a user with the IP address and same date will get the same transaction ID until its a new day. Thus, this user is only able to create 1 conversion per date. It doesn't take into account if they've created a conversion on another offer already. This setting of IP Address / Date is perfect for Advertisers that have 1 product but use multiple offers for the one offer.
IP Address / Date / Offer ID - Each time a user clicks on a tracking link or loads an impression pixel, they are assigned a number comprised of their IP Address, current date, and the ID of the offer the advertisement is for. So if a user's IP Address is 123.123.123.123, today's date is 2010-06-05 and offer ID is 99, then their transaction ID will be 1231231231232010060599. Note the the time is actually a unix timestamp and not just the year-month-day. Thus, each time a user with the same IP address and date can only create one conversion per offer per day. A user can create on conversions on 100 different offers on the same date, just as long as transaction IDs were set on click or impression by 100 advertisements associated with the offers. This setting of IP Address / Date / Offer ID is perfect for Networks that have lots of offers from different advertisers. It limits 1 conversion per user per day per offer and all other conversion attempts with the same Transaction ID will be flagged as a duplicate conversion.
Conversions that are rejected due to being duplicate as identified by the Transaction ID are logged and displayed in the Server Logs report. These are logged with the action of conversion and a message that reads: "Duplicate conversion for ad_id 123456789, Offer #30, Affiliate #56." ad_id is the Transaction ID.
Email this page to a friend or co-worker
