Status mapping and refunds
Sales can change after they are recorded. Status updates keep your profit numbers honest.
What it is
A conversion has a status. A sale may start as approved and later be refunded or reversed. You can update the status by sending another postback with the same transaction ID and a new status value.
Why it matters
If refunds are not recorded, your profit and ROI look better than they really are.
Step by step
Find out what your network sends
Some networks send a status value (for example Digistore24 sends
{transaction_type}). Others do not send refunds at all, such as ClickBank, which may not send them. Check the network guide.Map the values
Add the network's status macro to the postback as
status. [VERIFY: the list of status values TrafficTaps accepts and how a network's own words are mapped to them]Send the update with the same
txidTrafficTaps finds the original conversion by its transaction ID and changes its status instead of adding a new sale.
Update by hand when the network does not send it
[VERIFY: whether conversions can be edited or refunded by hand in the app]
Example
https://trk.traffictaps.com/api/postback?token=<WORKSPACE_TOKEN>&cid=7f3a9c&payout=23.50¤cy=USD&txid=ABC123&status=refundedCommon mistakes
- Using a new
txidfor the refund. TrafficTaps would see a new sale, not an update. - Assuming every network sends refunds. Many do not.
- Sending a status TrafficTaps does not know. Check the accepted values first.
Related pages
Stuck? Write to support@traffictaps.com with your campaign name and a sample click ID.