Skip to main content
A postback is a server-to-server (S2S) HTTP request that reports a conversion — a sign-up or a sale — from one system to another. Because the request travels between servers, it is unaffected by ad-blockers, cookie restrictions, or cross-device journeys. Partnero supports postbacks in both directions:

​
How the two directions work together

Both directions share the same click record, created the moment a visitor clicks a partner’s referral link:
  1. Click — a visitor clicks a referral link such as https://go.yourdomain.com/john?clickId=TRACKER_CLICK_ID. Partnero records the click, captures any trackable query parameters (sub-IDs like clickId above), and generates its own click ID — appended to the landing URL on redirect links, or stored in a first-party cookie by PartneroJS on direct links.
  2. Conversion (inbound) — your server calls the Partnero postback URL with that click_id when the visitor signs up or purchases. Partnero attributes the conversion to the right partner.
  3. Notification (outbound) — Partnero fires the partner’s affiliate postback, echoing the captured sub-IDs back to the partner’s tracking platform so the conversion appears in their tracker too.
You can use either direction independently. Inbound postback tracking is an alternative to PartneroJS and the REST API; outbound affiliate postbacks work with any tracking method, including PartneroJS and billing integrations.

​
When to use postbacks

  • Your partners run paid traffic through tracking platforms and need conversions reported back automatically — use affiliate postbacks.
  • You want cookieless, blocker-proof attribution without embedding an API key in any client — use postback URL tracking.
  • You already use the REST API server-side — you may not need inbound postbacks; compare in the S2S tracking guide.

​
Next steps

Postback URL tracking

Report sign-ups and sales to Partnero with a keyless postback URL

Affiliate postbacks

Send conversion notifications to your partners’ tracking platforms