Duplicate blocking
Networks sometimes call a postback more than once. Duplicate blocking makes sure one sale is counted once.
What it is
Duplicate blocking compares the txid of each incoming conversion to earlier ones. If it has seen that transaction ID before, it does not count it again.
Why it matters
A repeated postback would double your payout and ROI. Blocking keeps your numbers right and keeps your event count honest.
Step by step
Always send
txidUse the network's unique sale or transaction ID macro.
Keep it unique per sale
Two different sales must not share the same ID. A refund update for a sale should reuse that sale's ID, so it updates the sale.
Check for blocked duplicates
[VERIFY: where blocked duplicates can be seen in the app, if at all]
Example
Same txid twice, counted once
...&cid=7f3a9c&payout=23.50&txid=ABC123 -> recorded
...&cid=7f3a9c&payout=23.50&txid=ABC123 -> blocked as duplicateCommon mistakes
- No
txid. TrafficTaps cannot tell a repeat from a new sale. - Using the click ID as
txid. Two sales from one click would look the same. - Expecting blocking across workspaces. Each workspace is separate.
Related pages
Stuck? Write to support@traffictaps.com with your campaign name and a sample click ID.