How Can We Help?
Do you support Postback?
The essence of the Postback feature is that it provides an ‘alternative’ way of reporting limited stats from promoting our five featured brands, including our flagship product MyBookie (based on the events: Registrations and/or First Deposit Count) to a limited list of affiliates (whoever has requested the feature, and has the supporting means and tools on their end). Postback calls need to be setup for each and every affiliate that want to get this call and can be setup to be fired on either one or multiple events happening.
Reporting is done on a server 2 server basis, through a Postback call made to a url provided by the affiliate, for the event in question. MyAffiliates will send the Postback call to the affiliate url, as frequent as we receive and process data of the nature of the event.
So for eg: if we process FTD count data once a day (for yesterday’s data), the Postback calls for FTD would be done once a day, hence this is not real time ‘reporting’ but based on data frequency.
In terms of MyAffiliates UI feature specifics:
On every affiliate profile (left hand side of navigation pane) there will be a sub menu named Postbacks.
Each of the events needed by the affiliate can be granted.
This will allow the affiliate to receive ‘calls’ for the chosen event only if:
– he has submitted the ‘expecting’ url to be called (from his affiliate front end account)
– or a manager has configured the ‘expecting’ url from the Postback URL tab
There is a certain set of additional information that MyAffiliates can set for every postback call event, and it is covered by the available replacements below.
In other words the affiliate might wish to receive the media ID, or campaign name etc for the player registration which the Postback call would post.
In such cases the respective replacement needs to be inserted in the affiliate Postback url saved in the profile, but the affiliate ‘server’ should be configured to support and ‘read’ this info once it reaches his webserver.
|A unique identifier for the customer.
|The payload value you may have used when referring the customer.
|The s2s.req_id value you may have supplied when referring the customer.
|The s2s.pub_id value you may have supplied when referring the customer.
|The ID of the media you had used when referring the customer.
|The current title of the media you had used when referring the customer.
|The ID of the landing page you had used when referring the customer.
|The current title of the landing page you had used when referring the customer.
|The campaign you had used when referring the customer
|The current title for the campaigned you used to refer the customer.
|The name of the brand for which the event occurred. This value may be empty if the event is not associated with a brand.
In some particular cases affiliate (networks) desire to receive additional information over the Postback call, for eg: clickID, publisher ID.
In order to achieve this MyAffiliates should have received the clickID, publisher ID values first, and this would happen through any of the 3 additional tracking parameters available:
So, a typical tracking link that the affiliates currently use would look like:
if for example the network clickID needs to be passed the affiliate tracking link would look like:
where 123 (is an example of the click ID on the affiliate network side)
Once we have received FTD data and processed it, we’ll call the affiliate provided url, which for the sake of the clickID example would look like:
Our postback server will record the HTTP status code of the affiliate postback URL. However it will not follow a redirect such as a 301 or 302. Nor will it retry a failed request such as a 500 or 404.
Example of Postback Events for CPA plans (only) are:
- First Deposit Count
- Qualified Players
- Reload Deposit Count
More on how to enable Postback found here.