Server-to-server postbacks
Record every paid order, even when the buyer's browser blocks cookies or scripts.
- No cookies required
- Macros like {click_id}
- Order ID deduplication
- Log of rejected postbacks
21 days with every live feature. No card needed.
Your server reports a paid order
Your backend calls
https://trk.example.com/t/postback
- From the click
- Order value
- Stops duplicates
- Matched click
clk_7Q2M, partner#104- Conversion
- Created,
$49.00 - Commission
$9.80pending- Cookie needed
- No
Teams that work with us
Server-to-server postbacks in detail
Report conversions from your server to trackspot.ai with a postback URL, so browser limits and ad blockers cannot stop them.
What a postback is
A postback is an HTTP request that your server sends to trackspot.ai when a conversion happens. It carries the click ID that you saved at the time of the click. The request goes from server to server, so ad blockers, cookie limits and browser privacy settings have no effect on it.
Build the postback URL
A conversion postback looks like https://trk.example.com/t/postback?click_id={click_id}&amount={amount}&order_id={order_id}. Your backend replaces each macro with the real value before it sends the request. trackspot.ai matches the click ID to the original click and creates a conversion for the partner who sent it, with the commission for that offer.
{click_id}: the ID saved from the click{amount}: the order value for commission{order_id}: your order reference{currency}: an ISO code that matches your account currency{status}: approved, pending or rejected
Duplicates and security
Send an order ID with each postback so trackspot.ai can reject a second request for the same order. Add your postback secret to the URL, so only your server can create conversions. Rejected requests appear in the conversion error log with an error code, so you can see why a conversion was not created.
Set it up in 4 steps
Each step names the screen in your dashboard. Guides with screenshots are in the help center.
Go to Settings → Tracking → Postbacks and copy your conversion postback URL.
Save the click_id parameter from the landing page URL on the visitor's session or order.
Make your backend call the postback URL when an order is paid, with the macros replaced.
Send a test conversion and confirm it in Reports → Conversions.
What partner teams tell us
We will publish named customer stories here once customers approve them. Until then, this is a sample quote.
“We moved our postbacks to server-side and stopped arguing with partners about missing sales.”
Questions about server-to-server postbacks
Do postbacks need a cookie?
No. The click ID travels in the landing page URL and your server stores it. The postback sends it back, so no browser cookie is involved.
Can I decline a conversion after a refund?
Yes, before the commission is paid. Call POST /v1/conversions/status-by-order with the order ID and the new status, for example refunded, and trackspot.ai declines the commission. A second postback with the same order ID does not do this: it returns a duplicate_order_id error.
Works well with
Tracking links
Give every partner a unique link that records the click, assigns a click ID and sends the visitor on to your site.
IP allowlisting for postbacks Planned
Accept conversion postbacks only from server IP addresses you trust, so no one can create a fake conversion.
Postback and error logs
See why an incoming postback failed, and inspect every outgoing postback with its response code and retry history.
JavaScript tracker
Add one script to your site to save the click ID in a first-party cookie and record conversions from the browser.
Try server-to-server postbacks on your own program
It is in the 21-day trial with every other live feature. Send your first server-to-server postback and see real conversions on day one.