Setting up server-to-server postbacks
Receive a real-time HTTP ping on every conversion so your own analytics stay in sync with the network.
Updated 2026-05-21
A postback is a server-to-server HTTP request the network sends to your URL whenever one of your clicks converts. Postbacks are how you keep your own dashboards, billing, and audience tools up to date without polling the network's API.
Configure one postback per campaign
- Sign in to your publisher portal.
- Open the campaign you want postbacks for.
- Scroll to Postbacks → Add postback.
- Paste your endpoint URL with the macros you need (see below).
- Pick which events fire it (click, install, purchase, signup, etc).
- Save. Future conversions on this campaign will hit your URL within a few seconds.
Available macros
The network substitutes these tokens into your URL before sending the ping:
| Macro | What it resolves to |
|---|---|
{click_id} | The network-generated click ID |
{transaction_id} | Your own transaction_id that you passed on click |
{payout} | Payout amount in cents (integer) |
{payout_dollars} | Payout amount as 1.23 |
{event} | The event name (install, purchase, ...) |
{sub1} – {sub5} | Sub-IDs you passed on click |
{currency} | ISO 4217, e.g. USD |
{timestamp} | UTC ISO 8601 string |
Example:
https://my-tracker.example.com/conv
?cid={click_id}
&txn={transaction_id}
&pay={payout_dollars}
&evt={event}
Your endpoint must respond with an HTTP 2xx status. If we get a 4xx or 5xx, the postback is queued and retried with exponential backoff. After ~24 hours of failures, retries stop and the postback is logged as failed in your dashboard.
Test before going live
Use the Postback test tool in your publisher portal. Pick a campaign, an event, fill macro values, and the network will fire a sandbox request to your endpoint. You'll see the resolved URL, response status, response body (truncated to 8KB), and total latency — exactly what production will look like.