There are hundreds of different tracking platforms and parameters that you can include in a postback, so generally no two will look alike.

However, here is an example of what a more ‘typical’ postback may look like: 


http://www.adserver3.com/pstCallback.php?data={aff_sub}&data2{aff_sub2}&payout={payout}


where the first part http://www.adserver3.com/pstCallback.php is the tracking platform you use and the second part represents the parameters that define the information that will be sent back to you.


The ad server dynamically replaces the parameter in the brackets with the actual value when delivering a postback, for instance, payout={payout} will become payout=$1.80.


Please ensure that you add the following parameters to our tracking link, as in the example below:


http://go.trackinit.com/aff_c?offer_id=2312&aff_id=2170&aff_sub=YOURDATA&aff_sub2=YOURDATA


Additional parameters that can be used:


{transaction_id} – This sends you our transaction id. However, if you would like to receive yours, then this needs to be changed to {aff_sub}.


{aff_sub} – This will pass back your affiliate sub id as specified in the tracking link.


{aff_sub2} – The rest of the aff subs, so 1–5, can be used to identify any specific info that you want to receive – just make sure it matches the tracking link.


Please find more parameters below:


{offer_id} ID of offer.


{offer_name} Name of offer.


{offer_ref} Reference ID for offer.


{goal_id} ID of goal for offer.


{affiliate_id} ID of affiliate.


{affiliate_name} Company name of affiliate.


{affiliate_ref} Reference ID for affiliate.


{source} Source value specified in the tracking link.


{aff_sub} Affiliate sub specified in the tracking link.


{aff_sub2} Affiliate sub 2 specified in the tracking link.


{aff_sub3} Affiliate sub 3 specified in the tracking link.


{aff_sub4} Affiliate sub 4 specified in the tracking link.


{aff_sub5} Affiliate sub 5 specified in the tracking link.


{offer_url_id} ID of offer URL for offer.


{offer_file_id} ID of creative file for offer.


{file_name} Name of creative file for offer.


{advertiser_id} ID of advertiser.


{advertiser_ref} Reference ID for affiliate.


{adv_sub} Advertiser sub specified in the conversion pixel / URL.


{transaction_id} ID of the transaction for your network. Do not confuse this with the ID an affiliate passes using the parameter {aff_sub}.


{session_ip} IP address that started the tracking session.


{ip} IP address that made the conversion request.


{date} Current date of conversion formatted as YYYY-MM-DD.


{time} Current time of conversion formatted as HH:MM:SS.


{datetime} Current date and time of conversion formatted as YYYY-MM-DD HH:MM:SS.


{ran} Randomly generated number.


{currency} 3 digit currency abbreviated.


{payout} Amount paid to the affiliate for the conversion.


{sale_amount} Sale amount generated for the advertiser from the conversion.


{device_brand} For mobile app tracking, the brand name of the mobile device (example: Apple).


{device_model} For mobile app tracking, the model of the mobile device (example: iPhone).


{device_os} For mobile app tracking, the operating system of the device (example: iOS).


{device_os_version} For mobile app tracking, The numerical version of the device operating system (example: 4.3.2)


{device_id} For mobile app tracking, the DEVICE ID of the Android device iOS UDID is deprecated as of May 1, 2013.


{device_id_md5} For mobile app tracking, the DEVICE ID of the Android device hashed with MD5 algorithm. The value should be generated based on the original value lower case. md5(aaaaaaaa1111111).


{device_id_sha1} For mobile app tracking, the DEVICE ID of the Android device hashed with SHA1 algorithm. The value should be generated based on the original value lower case. sha1(aaaaaaaa1111111).


{android_id} For mobile app tracking, the ANDROID ID for Android devices only. The value should be formatted as lower case.


{android_id_md5} For mobile app tracking, the Android ID of the Android device hashed with MD5 algorithm.


{android_id_sha1} For mobile app tracking, the Android ID of the Android device hashed with SHA1 algorithm.


{mac_address} For mobile app tracking, the MAC address of the phone’s wifi adapter formatted as uppercase with colons. AA:BB:CC:DD:EE:FF


{mac_address_md5} For mobile app tracking, the MAC address of the phone’s wifi adapter hashed with MD5 algorithm. The value should be generated based on uppercase characters with : separating colons. md5(AA:BB:CC:DD:EE:FF).


{mac_address_sha1} For mobile app tracking, the MAC address of the phone’s wifi adapter hashed with Sha1 algorithm.


{onid} For mobile app tracking, the ODIN of the device which is the the MAC address of the phone’s wifi adapter in a binary array and then hashed with SHA1 algorithm.


{open_udid} For mobile app tracking, the OpenUDID of the device.


{ios_ifa} For mobile app tracking, Apple’s advertiser identifier with iOS


{ios_ifa_md5} For mobile app tracking, the IFA ID of the iOS device hashed with MD5 algorithm.


{ios_ifa_sha1} For mobile app tracking, the IFA of the iOS device hashed with SHA1 algorithm.


{ios_ifv} For mobile app tracking, Apple’s vendor identifier with iOS 6+.


{unid} For mobile app tracking, the unid is not a specific device identifier, but unifies all of the above unique identifiers.


{mobile_ip} For mobile app tracking, the ip address for the mobile device.



If you would like to test whether your postback implementation is correct, please select an offer, generate a tracking link and send both to hello@bidderplace.com.