1.5 Type of integration
Last update Nov 12, 2019
ACCESSTRADE has 3 main methods of integration with our advertisers. Divided mainly into S2S synchronization (Postback and API reporting), and cookies.
Postback
What is postback ?
Postback refers to a callback method that is mainly used in server to server synchronization, if an advertiser's website has its own backend database and is able to support Postback, we can use the function to fire an entry to our own backend to record the conversion as well.
For publishers, Postback is a function that will notify publishers when a conversion occurred or was approved/rejected. Publishers can use postback function to sync conversion data from ACCESSTRADE.
How to set up postback ?
Setting up postback will require the advertiser to have an internal server that can support the postback function, every server is different but in general, when an event is fired in the internal server, a postback function can also be called to fire an entry to our backend. Usually, we will help in setting this up, but as a general rule of thumb, the Postback URL that has to be implemented will look like this
https://cv.accesstra.de/cv.php?result_id=1&identifier={Transaction(95 B) ID}
For more information, please visit
API
What is API ?
API reporting refers to a report retrieval method that is also used in server to server synchronization. If an advertiser's website is able to support API report retrieval, we can create a function on our server to send a request to their server to give us all entries that have been created that day, and saving the conversion in our backend as well.
How to set up API ?
In general, a server should be set to receive requests from other servers so that they may share information. For more detailed reading, please visit
https://accesstrade-global.freshdesk.com/support/solutions/folders/36000183856
Cookies
What is Cookies ?
Cookies are a piece of code that will be saved in a computer's local files when it saves passwords or settings. But for Accesstrade, our tracking cookies saves the click_id and the click time of the user when the user clicks on one of our banners. No other data is saved within the cookie other than these 2 essential data that helps us to validate the conversion and make it unique and differentiable.
Function of Cookies
When a cookie is saved on the User's local data, it will retain itself in the user's computer until a set period of time has passed. Usually determined by the advertiser's request (usually 30 days or 14 days), If a conversion happens on the advertiser's website within the cookie's duration, a tracking pixel will be fired to our backend thus completing the conversion. If the cookies are cleared on the User's computer, or the cookie expires before the conversion is completed, the conversion is regarded as null and the tracking pixel will not be fired back to us.
Sub ID
What is Sub ID ?
Sub IDs refers to parameters that are available for publishers, ACCESSTRADE and advertisers to send data to each other. These are generally used for dynamic values such as Total Price and Transaction ID, Publishers can then use returned data to analyze what needs to be done to lead to more conversions and optimize the performance of the campaign they're taking.
How to set up Sub ID ?
Sub IDs are set up at the end of URLs, usually separated with a '&' and assigned using a '='. In the
example above explaining about postback, (https://cv.accesstra.de/cv.php?result_id=1&identifier={Transaction(95 B) ID}), 'identifier' is a Sub ID that is passed from Accesstrade to the Publisher. The publisher may then retrieve this data and assign it elsewhere and use this collated data to optimize the campaign.
For more information, please visit https://accesstradeglobal.freshdesk.com/support/solutions/articles/36000036818-what-are-sub-ids-and-how-to-use-
Related Courses
