new

Postback and event improvements

We have rolled out a number of technical improvements to postbacks, JS tracking and API uploads that enables some useful features:

Disabling traffic source postbacks

You can now pass
disable_postbacks=true
into postback URLs to prevent firing of events to your traffic source for a conversion. This is particularly important for search arbitrage users where you may want real time tracking followed by delayed postbacks to update revenue
Likewise you can also pass this into your conversion API uploads (see updated docs) and set the same parameter in JS tracking events

Event statuses

You can now pass
status=value
into postbacks to set a pseudo event status. This is not yet a field in our database or reporting.
However, when you send a status of
pending
,
hold
or
preapproved
, our system will adjust revenue to
0.01
.
When status is set to
rejected
,
reject
,
trash
or
cancelled
, the revenue will be set to
-1
and this will delete the conversion
This has been added to assist with networks where they can only set a single postback, but can send a dynamic status value for the various events.
Let us know if there are other values you need caught here, or if you'd prefer a revenue of
0
instead of
0.01
for the pending conversions.
We intend to add a mutable event status column to our database later

POST support in postbacks

Incoming postbacks using POST rather than GET are fully supported
We will check the POST body for relevant parameters for hit, revenue and transaction ID - we have a list of possible names here we will check through
The standard keys/values in the query string will take priority

Other changes

We have moved our reporting system's caching back to an old version to remedy the issues some users were having with asset pages not showing updates reliably (e.g. you delete an offer and it reappears on refresh of the table).