How the tracker receives conversions

The tracker learns about a lead or sale from the affiliate network's postback and reports the conversion to the ad source on its own. Below is the whole path in order, with links to detailed instructions.

The conversion path

1. The visitor follows the campaign link. The tracker records the click and assigns it a subid.
2. The tracker sends the visitor to the offer. The subid gets into the offer link through the {subid} macro.
3. The affiliate network registers a lead or sale and calls the tracker's postback URL with this subid.
4. The tracker finds the click, determines the status and payout and records the conversion.
5. The tracker sends the event further: to the traffic source, to the campaign's recipients and to Facebook, if this is configured.

Subid and external_id

A click has two identifiers for different directions.

For the network to get the subid, add the macro to the offer link, for example sub1={subid}. The parameter name is set by the network. If a network from the catalog is selected in the Affiliate network («Партнёрская сеть») field, the Add the selected network's parameters («Добавить параметры выбранной сети») button appears under the link — it appends this network's parameters to the link.

The tracker takes the external_id value from a parameter of the ad link. Which parameter counts as external_id is set by the source tokens.

Both identifiers are visible in Logs → Clicks and leads («Логи → Клики и лиды»), in the Subid and External ID columns. You can also search for a click by them, see Click and lead search.

Incoming postback from the affiliate network

The general postback URL is in the Networks («Сети») section, in the Conversion postback URL («URL постбэка приёма конверсий») block:

https://track.example.com/api/v1/postback?subid={click_id}&status={status}&payout={payout}&txid={txid}

Copy the URL into the affiliate network's settings and replace {click_id}, {status}, {payout} and {txid} with that network's macros. A network added to the list has its own URL with its parameters — the Postback URL («URL постбэка») column, the copy («копировать») button. For parameters, tracker responses and secret protection, see Incoming postback.

Three parameters determine how the conversion is counted:

• Status. The tracker's canonical statuses are lead, sale, rejected and hold. A status without a mapping is recorded as it arrived; an empty one as lead. Map the network's status names on the Settings → Conversions («Настройки → Конверсии») tab, see Conversion types.
• Transaction ID. By txid, the tracker tells a repeated postback from a status change of the same conversion. Without txid, a repeated postback is sent to the source and to Facebook again, while in reports the click keeps one conversion with the latest status. For details, see Duplicates and conversion corrections.
• Payout. The amount is taken from the postback or from the payout set in the offer and is converted to USD at the rate from Settings → Currencies («Настройки → Валюты»), see Currencies and rates.

If there is no postback from the network, conversions are uploaded as a file: Conversion import from CSV.

Outgoing S2S postbacks

After recording a new conversion or a change of its status, the tracker sends requests to two lists of URLs. Both lists work at the same time.

• Source postback. Configured in the source card in the Sources («Источники») section, in the S2S postback to source («S2S-постбэк в источник») block: the One URL for all statuses («Один URL на все статусы») or Separate URL for each status («Отдельный URL на каждый статус») mode. The ad network's click ID is inserted into the URL with the {external_id} macro. See S2S postback to the source.
• Campaign postbacks. Configured in the campaign on the S2S postbacks («S2S-постбеки») tab, in the Campaign postbacks («Постбеки кампании») block: up to 20 additional URLs, each with its own status or All statuses («Все статусы»). See Campaign and source S2S postbacks.

Requests are sent with the GET method. The payout in them is always in USD. If after macro substitution the source URL and the campaign URL match, one request is sent. An exact repeat of a postback with the same txid and a payout correction without a status change do not create new sends.

A new or changed URL applies only to subsequent conversions: those already accepted are not sent again.

Facebook Conversions API

To have the tracker send events to Facebook on its own, select the Facebook Conversions API checkbox in the source card and fill in Pixel ID and Access Token. If you leave the fields empty, the values are taken from the click or from the campaign parameters.

The lead status is sent as the Lead event, the sale status as the Purchase event. No events are sent for other statuses. For setup and the data sent, see Facebook Conversions API.

Where to see the result

Owners and admins can see the Logs section.

In the delivery log, each send has a state: Pending («Ожидает»), Processing («Обрабатывается»), Done («Выполнено») or Needs review («Нужна проверка»). On a temporary error at the recipient, the tracker retries the send on its own. In the Needs review state there are no automatic retries. Before a manual retry, check the data with the recipient so as not to get a duplicate.

What happens when the license has expired

Receiving postbacks does not depend on the license: conversions continue to be recorded. Outgoing S2S and Facebook events are not sent and wait in the queue. After renewal, the tracker sends them automatically. For details, see License expiry.

FAQ

The conversion did not appear in the tracker

Go through the steps in Postback not arriving: what to check.

How the source postback differs from campaign postbacks

The source postback applies to all campaigns with this source. Campaign postbacks are additional URLs for one campaign only. A campaign without a source sends only its own postbacks.

Do I need to change the postback URL for each campaign

No. The tracker finds the campaign by the click's subid, so the postback URL does not depend on the campaign. If the source has a Postback/lead secret («Секрет постбэка/лида») set, add the secret parameter to the URL.