Postbacks

How incoming conversion postbacks and outgoing postback templates work in Axalot Tracker.

What postbacks do

A postback is an incoming conversion signal from a partner or network. It tells Axalot that a tracked click later produced an event such as registration, purchase, lead, hold, decline, or repeat deposit.

Click matching

Postbacks must include the click id passed through the offer link.

Status mapping

Partner statuses are normalized through affiliate network settings.

Revenue

Revenue can come from the offer or from the incoming postback.

Outgoing templates

Matched conversions can trigger Facebook, HTTP GET, or Telegram callbacks.

Console path

Console / Tracker / Postbacks
Console / Tracker / Reports / Postbacks

Basic flow

Campaign sends traffic through an offer link.

The offer link passes the Axalot click id to the partner URL.

The partner sends a postback to Axalot after a conversion event.

Axalot matches the postback to the original click.

Axalot stores status, revenue, currency, and event metadata.

Configured outgoing pixels or callbacks can receive the event.

Click id is required for reliable attribution

If the partner does not return the tracked click id, Axalot cannot reliably connect the conversion to the original campaign, stream, and offer link.

Outgoing template macros

Console / Tracker / Postbacks uses the same outgoing macro format as Offer Links. HTTP GET URLs and Telegram Message Templates accept only these single-brace tokens:

{click_id}
{currency}
{creative_id}
{ad_campaign_id}
{source}
{keyword}
{utm_source}
{utm_medium}
{utm_campaign}
{utm_content}
{utm_term}
{sub1}
{sub2}
{sub3}
{sub4}
{sub5}
{sub6}
{sub7}
{sub8}
{sub9}
{sub10}

Examples:

https://example.com/pb?cid={click_id}&sub1={sub1}
<b>{click_id}</b> {sub1} {currency}

Do not use {event.*}, {campaign.name}, {offer.name}, {fbp}, {fbc}, {cost}, or {{macro}} in Postbacks templates.

HTTP GET URL rules

HTTP GET templates must be valid external http:// or https:// URLs. Query keys may be partner-specific, but query values may contain only URI-safe text and allowed Axalot macros.

https://partner.example/pb?clickid={click_id}
https://partner.example/pb?cid={click_id}&campaign={ad_campaign_id}