XTRACKER

S2S postback macros reference

Every macro you can use in an outbound S2S postback url_template — uid, value, campaign fields and more — plus method and expected-status configuration.

This is about outbound postbacks — XTRACKER firing a URL to an affiliate network when a conversion happens. (For inbound postbacks from a network into XTRACKER, see the Pocket Option guide.)

Configuration

An s2s_postback destination takes:

{
  "url_template": "https://aff.example.com/pb?cid={uid}&type={event}&payout={value}",
  "method": "GET",
  "expected_status": 200
}
  • url_template — the URL with {macro} placeholders.
  • methodGET (default) or POST.
  • expected_status — the status code that means success (default 200). Anything else is treated as a failure.

Available macros

Every macro is URL-encoded automatically. Missing values render as an empty string.

Macro Value
{uid} the click id
{event} the mapped target name (from your event map)
{canonical} the canonical event (deposit, …)
{value} deposit amount (empty for non-deposits)
{currency} currency code
{occurred_at_ms} event time, epoch ms
{tg_id} Telegram user id
{fbclid} Facebook click id
{campaign_id} / {campaign_name} campaign attribution
{adset_id} / {adset_name} ad-set attribution
{ad_id} / {ad_name} ad attribution
{placement} placement

Example

A network that wants the click id, an event type, and a payout on deposits:

https://aff.example.com/postback?clickid={uid}&goal={canonical}&sum={value}&cur={currency}

On a $25 deposit for uid abc123 this fires:

https://aff.example.com/postback?clickid=abc123&goal=deposit&sum=25.00&cur=USD

Success and retries

If the response status equals expected_status, the event is sent. A 408/429/5xx is retried with backoff; any other mismatch is permanent. So if your network returns 204 on success, set expected_status to 204 or it'll look like a failure.

Next

  • Destinations — how outbound delivery, retries and proxies work.
  • Event maps — control the {event} macro per destination.