Skip to content

Affiliate postback setup: send Rastro conversions to your tracker or ad platform

How affiliates receive their conversions by postback in Rastro: global, per-offer and per-goal postbacks, GET, POST or HTML pixel, macros and testing.

Updated on 22 Oct 2026

Affiliates usually track their campaigns in their own tracker (Keitaro, Binom, Voluum…) or optimise ads on platforms like Facebook or TikTok. For that, they need to know about each conversion as it happens. In Rastro, every affiliate configures their own postbacks and receives conversions automatically.

Where to set it up

As an affiliate, go to Integration → Postback and add a postback. Each one has:

  • a scope: all offers (global), a single offer, or a single goal of an offer;
  • a method: a URL called with GET, a POST with the values in JSON, or an HTML pixel (for platforms that only accept a script or image tag);
  • the statuses that trigger it: approved, pending, rejected or reversed.

Each conversion uses the most specific postback: goal first, then offer, then global. This lets you send, for example, registrations to one place and deposits to another.

Macros

The URL (or JSON body) can include macros, replaced with each conversion's values:

Macro Value
{click_id} The click identifier
{conversion_id} Rastro's conversion ID
{txn_id} The advertiser's transaction ID
{goal} The goal code (empty for the offer's main event)
{payout} and {currency} Your earnings for this conversion
{status} approved, pending, rejected or reversed
{campaign_id}, {affiliate_id} The offer and your public ID
{sub1}, {sub2}, {sub3} The sub IDs from the click

A typical setup with an external tracker passes the tracker's click ID in sub1 when sending traffic, and sends it back in the postback:

https://your-tracker.example/postback?cid={sub1}&payout={payout}&status={status}

Unknown macros are flagged when you save, so typos don't go unnoticed.

Testing and delivery

Use Send test to call the postback with sample values and see the response from your server straight away. The Recent deliveries list shows every real call, its HTTP response and errors.

If a delivery fails (your server is down or answers with an error), Rastro tries again up to 5 times over the next 15 hours, waiting longer between attempts.

Good to know

  • Postbacks only go to public addresses: calls to private or internal networks are blocked for security.
  • Changes in a conversion's status (for example a refund marked as reversed) trigger the postback again if you chose that status.
  • You can also receive conversions on your phone with Telegram notifications in your account settings.