Overview
1. Introduction
There are two types of postback service invocation:
- client - server
- server - server
Client-server is used in such cases when the user's action causes a lead, while the user is interacting with the page at this moment (e.g. when the lead is filling in the registration form). Such scheme makes it clear, if there was a fact of making a lead.
Server-server is used when the user is not interacting with the page while making the lead (e.g. when the lead is a confirmed order, it means, that before making the lead, the call center operator should call the user and at this moment the user is not interacting with the page). With this scheme, the advertiser server interacts with the adSniper server by transferring the delivery identifier.
The key point of the postback invocation is the notification of lead. All the traffic that adSniper sends via the Super Sniper system contains a unique impression number in the get parameters, in most cases it is called "s_trk". In order to avoid collisions with other parameters, adSniper can give this parameter any name.
In order to inform about the lead, it is necessary to return adSniper the s_trk get parameter of the user who has made the lead.
As for the client-server, you can keep the key in the cookie and read it at the time of the lead.
For the server-server you have to keep the user id mapping, which identifies users and assigns the value s_trk to it.
2. Example of the postback link
Possible is a modifier for the lead type (used for rejected leads)
type=decline
| {partner_ID} | this is the identifier of the partner in our system, you can normally use site_{site_name} where {site_name} for test.ru - testru Finally it is site_testru |
| {revenue} | the cost of the lead, if it is a test campaign or if the cost of a lead has not been specified, you can transfer "1". The value transferred in this field may be not an integer, the separator ".", for example: "154.32", means that the currency is ruble. |
| {offer_id} | Identifier of the offer in the partner If the offer is one, you can pass "1" to this field, if there are more offers, you can transfer their identifier or a text name. |
| {s_trk} | - value of strk get parameter which has user ChRhZHA0WncRerU-EeSLfgElkJWCShCpsuuqDBjNw4OnBSDkw4OnBQ* (e.g. s_trk) alphabet a-zA-Z0-9- |
| {trans_id} | - unique transaction number If transactions are not separately monitored, you can transfer Unix Time Stamp in this field |
| {s_leadid} | - lead identifier Generally this get is missing, it is neccessary only when you need to monitor several lead types alphabet a-zA-Z0-9_- |
| {currency} | - the currency in which the lead is transferred, is taken at the rate of the Central Bank of Russia and is converted into rubles. (this is an optional field and can be missed, in this case the conversion won't be made) |
3. Description of the postback work principle
SuperSniper has an aggregate statistics and that is why it can't change the lead status. Update is supported by storing lead / unlead status. So when a lead will be created in the hold status for SS, this is an accepted lead. If this lead was accepted in the CPA, the SS does not handle it. If the lead was rejected in CPA, the SS will create another entry with the "unlead" lead status. It means, that when calculating the CPA profit from the amount of leads with the lead status, the amount of leads with the unlead status will be subtracted.
An example how offer works with the automatic acceptance:
The offer doesn't deal with hold / acceptance / rejection, it means that all the leads are accepted. As for CPA, it has three settings fields: lead / hold / reject, but only the lead field has to be filled in.
An example how offer works in different cases:
There are three modes for the offer: hold / lead / reject.
But in SS you have to transfer type=accept, when lead in the CPA is in the hold mode. It means that once the lead is created in CPA, SS gets this information and starts handling it.
While accepting lead in SS you don't have to send info, because of it the lead can begin to double.
If the lead is rejected in the CPA in the SS, you have to send type = decline, in order the SS could count this lead as rejected.
Learn more
https://docs.google.com/document/d/1RcJbPfZ4RuwUfmXW9VvXHtOjZyHU4sPtNxo-Zf65yHM/edit
4. Calculating statistics
SuperSniper registers statistics in 2 different cases: the click time (lead) and the lead now. Such statistics allows to calculate the revenue according to the time the user clicked and to the time the action was committed. This is necessary to calculate profits. Below you will find an example when the advertising campaign was launched for 1 day:
| Date | Impressions | Clicks | Lead | Lead Now | eCPM (lead) | eCPM (lead now) |
|---|---|---|---|---|---|---|
| 01.08.ХХХХ | 10000 | 100 | 100 | 0 | 10 | 0 |
| 02.08.ХХХХ | 1 | 1 | 0 | 100 | 0 | 100000 |
Updated over 6 years ago