Postback

‎

This section will be useful only to those partners who use the tracker in their work.

Setting up postback

In our system, you can select the following notifications for sending in postback:

• conversion (subscription, unconfirmed lead);
• confirmed conversion (including buyout, IC, rebilling);
• rejected conversion;
• unsubscribe;
• trash conversion.

In addition, you can pass additional parameters if necessary, such as:

• {TRAFFIC_ID} - Unique subscriber ID
• {OFFER_ID} - Offer ID
• {SUB_ID} - Sub id from tds link
• {DATE} - Event date
• {OS} - Operating system
• {OS_VERSION} - Operating system version
• {SMARTLINK_HASH} - Smartlink hash
• {INCOME} - The amount of income to the balance
• {PAYMENT_ID} - Unique transaction ID
• {IP} - Ip of the subscriber
• {BROWSER} - Browser
• {OPERATOR_NAME} - Operator name
• {TYPE} - Event type
• {PHONE} - Subscriber's phone
• {DEVICE_BRAND} - Device brand
• {DEVICE_MODEL} - Device model

After saving the postback URL, you can test send the postback by clicking on the "Test" button in the tool.

TrafficBack (trafficback, TB, TB)

If for some reason your traffic cannot be accepted by an offer or a smart link, it will be sent to the URL for inappropriate traffic. This URL is called the TrafficBack URL. Filling in this URL is optional - if the field is empty, traffic will be redirected to the system TrafficBack URL.

In addition, you can pass additional parameters if necessary, such as:

• {SUB_ID} - Sub id from tds link
• {SOURCE} - Source 1
• {SOURCE2} - Source 2
• {SOURCE3} - Source 3
• {SOURCE4} - Source 4
• {SMARTLINK_HASH} - Smartlink hash
• {REASON}- Reason tb

Possible causes of TrafficBack

Tele2:

• 403 - Partner's IP is not added to the white-list.
• 600–699 - landing page setup error.
• 640–659 - landing page setup error.
• 661 - MT subscription already exists. Occurs when trying to create a session for an existing mt-subscription.
• 662 - operations on this subscriber number are not possible. Occurs when trying to create a session for an existing mt-subscription.
• 700-799 - error on the control side. Perhaps the KP is temporarily unavailable or a denial of service for the subscriber number specified in the request has been received.
• 701 - permanent error on the CP side.
• 500–599 - error on the CP side.

Beeline, MTS:

• tb-Meizu - tb for banned devices;
• tb-ua-wv - webview;
• virus - "viral" traffic;
• tb-cap-{offer_id} - cap excess code + offer_id (offer id, respectively);
• tb-Desktop - device type - desktop;
• tb-Tablet – device type - tablet;
• tb-micromax - traffic from prohibited devices;
• tb-tb-for-all – tb if the offer is disabled;
• tb-tema-522 - tb from temafon, the Subscriber is in the stop list;
• tb-tema-521 - tb from temafon, The subscriber is not recognized as a Beeline subscriber;
• tb-tema-513 - tb from temafon, Subscriber's request was blocked as a fraud;
• tb-tema-524 - tb from temafon, daily limit is over;
• tb-tema-530 - tb from temafon, transmitted traffic source not found;
• tb-tema-532 - tb from temafon, traffic source is blocked on the TF side;
• tb-mts-6 - request activation timeout exceeded;
• tb-mts-8 - failed to determine the MSISDN for the subscription;
• tb-mts-10 - unknown error;
• tb-mts-13 - MODETECT validation error;
• tb-mts-14 - the Content Ban service is enabled;
• tb-mts-16 - the user clicked the "Return to the site" link.
• tb-vaimobi-1 - internal server error;
• tb-vaimobi-2 - CDP access error;
• tb-vaimobi-3 - invalid conditions (not from mobile internet or mobile device);
• tb-vaimobi-4 - fraud filter triggered (multiple requests from the same device);
• tb-vaimobi-5 - subscriber in the stop list.

Postbacks sent

This function allows you to download sent postbacks (according to filters) in .csv and .json formats.

An example of a well-formed postback and trafficback link

Postback: http://my-site.test/?clickId={traffic_id}&uid={sub_id}

Trafficback: http://my-site.test/?t={sub_id}&reason={reason}