<b>Postback QA — 7-point pre-launch checklist</b>

<b>Postback QA — 7-point pre-launch checklist</b>

A broken postback means you optimize blind for hours. Verify before traffic, not after.

— Fire a manual test conversion from the network panel, confirm it lands in your tracker within 60 seconds
— Confirm the {click_id} / {cid} token in the postback URL matches the exact parameter your tracker reads (a tracker expecting <code>cid</code> ignores <code>clickid</code> silently)
— Check the payout token resolves to a number, not <code>{payout}</code> as literal text — a string breaks revenue math
— Verify the status parameter maps correctly: approved vs pending vs rejected each route to the right event
— Confirm HTTPS on the postback endpoint; mixed protocol calls get dropped by some firewalls
— Test a duplicate fire — your tracker must dedupe on click_id, not double-count
— Check the postback IP isn't rate-limited or whitelisted-out on your server

Log the test conversion ID so you can trace it end to end if numbers disagree later.

Save this SOP. Run this before every launch.