Postback Tracking (S2S): Click IDs, Conversions & Payouts
A practical explanation of server-to-server postback tracking for affiliate and performance marketing.
- A postback returns conversion information from one system to another using a shared identifier.
- Click IDs are the bridge between the visit and later conversion.
- Validate macros, encoding, payout fields, and duplicate handling.
The basic pattern
The tracker generates or stores a click ID, passes it to the offer or affiliate network, and records the visit. When the conversion occurs, the network calls the tracker’s postback URL and includes that click ID plus allowed conversion details.
Why affiliates use it
The affiliate often cannot place a browser pixel on the merchant’s checkout. A server-to-server callback lets the network report a conversion directly to the affiliate’s tracker.
ClickMagick currently offers a 14-day trial. Use it to validate your real conversion paths before committing.
See ClickMagick Affiliate link. Tracking Compass may earn a commission if you purchase.Fields to test
Confirm the click-ID macro, conversion type, transaction ID, payout/revenue, currency, status, and any sub-ID fields. URL-encode values correctly and never assume two networks use the same macro names.
Troubleshooting
If conversions are missing, trace the click ID from outbound link to network and back to the postback. If conversions duplicate, inspect transaction IDs and retry behavior. Reconcile against the network before making commission decisions.
What to do next
If this topic describes your current tracking problem, move one step closer to a software decision: compare the relevant tracking category, shortlist products against your actual data path, and validate a real campaign before migrating the rest of your stack.