Partner postbacks (outgoing)

A partner postback is a URL (or pixel, or HTML snippet) that TrackCrown calls when a partner's conversion is recorded, so the partner's own tracker, network or ad platform learns about the conversion. You can set postbacks up for partners, and partners can manage their own in the partner portal.

Where postbacks are managed#

Conversion-API destinations (Meta, TikTok, Microsoft) are configured on Integrations, not here.

Create a postback#

1. Click New postback.
2. Affiliate (network only): the partner whose conversions trigger it. Leave it on All affiliates (workspace-wide) for a postback that fires for every partner's conversions (for example your own BI endpoint).
3. Offer: one offer, or All offers.
4. Event: one event code, or All events (staff see "All non-private events").
5. Optional: Start from a preset (see Presets).
6. Type:
   • Server-to-server (S2S) — our server calls your URL (recommended);
   • Image pixel — our server requests the pixel URL with GET, for trackers that only accept image pixels;
   • HTML / iframe pixel — a snippet rendered in the buyer's browser, only on iframe or JavaScript pixel conversions.
7. HTTP method (S2S): GET or POST.
8. Postback URL / Pixel URL with macros, for example https://tracker.example.com/postback?clickid={sub1}&payout={payout}&txid={conversion_id}.
9. POST body (S2S + POST) or HTML snippet (HTML type).
10. Fire on (below), Skip conversions with a zero payout, and for S2S optionally Custom headers.
11. Leave the switch on Active and check Preview with sample values. Unknown macros are flagged ("Unknown macros are sent literally").
12. Click Create postback.

URL rules#

• Must start with http:// or https://, have a host name, contain no spaces and be at most 4,096 characters.
• Macros cannot be used in the host name.
• Partner-created postbacks may not point to private or local addresses. In any case the sender delivers only to public IP addresses.

Which conversions fire it#

A postback fires for a conversion when all of these hold:

• it is Active;
• its affiliate is the conversion's partner, or it is workspace-wide;
• its offer matches (or is All offers) and its event matches (or is All events);
• private events: only workspace-wide postbacks that name the private event explicitly fire — never a partner's postback and never an "All events" postback;
• the conversion's status matches Fire on;
• Skip conversions with a zero payout is off, or the payout is not 0;
• the conversion is not a duplicate.

Each postback fires at most once per conversion, however often the conversion changes.

Fire on#

POST bodies#

The Content-Type is application/json when the body starts with { or [ (macro values are JSON-escaped; put quotes around them in the template), otherwise application/x-www-form-urlencoded (values form-encoded):

{"click_id":"{sub1}","event":"{event}","payout":"{payout}","currency":"{currency}","order":"{adv_txid}"}

Custom headers#

S2S postbacks can send up to 10 static headers, one Name: value per line, for example Authorization: Bearer abc123. Names use HTTP token characters (max 64); values max 1,024 characters without control characters. Host, Content-Length, Transfer-Encoding, Connection, Keep-Alive, Proxy-Authorization, Proxy-Connection, TE, Trailer, Upgrade, User-Agent, Cookie and Expect cannot be set. Every request carries User-Agent: ArcTrack-Postback/1.0.

Partner self-service#

Partners create postbacks in the portal under Postbacks with the same form, limited to:

• their own conversions (no Affiliate field);
• offers they can run (public, or approved for them) and non-private events;
• macros without network-only money: {revenue}, {advertiser_id} and {old_revenue} are refused in the form, and always expand to an empty value in partner-created postbacks.

When every delivery of a postback fails for more than 72 hours it is paused automatically and the partner is notified — see Postback delivery.

Presets#

Start from a preset fills the type, method, URL (and body/headers) for common platforms. Replace the UPPER_CASE placeholders. Presets assume the partner passes their click ID into sub1 of the tracking link.

Example (Voluum):

https://YOUR-VOLUUM-DOMAIN/postback?cid={sub1}&payout={payout}&txid={conversion_id}

Import postbacks from CSV#

Use it when moving partners from another tracker.

1. Go to Import partner postbacks (Affiliates area).
2. Choose file or paste CSV; Insert example shows the format.
3. Click Preview: every line is validated (partner, offer, event, method, URL).
4. Click Create N postbacks.

affiliate_code,offer_code,event,method,url
partner7,SHOP01,sale,GET,https://tracker.example.com/pb?cid={sub1}&payout={payout}
partner9,,,GET,https://t.example.net/postback?clickid={sub1}&status={status}

Imported postbacks are active S2S postbacks. At most 2,000 lines per import.

Test it#

Use the row menu → Send test, then Recent results — see Postback delivery, testing and retries.