IP allowlisting for postbacks Planned
Stop anyone who finds your postback URL from creating conversions you did not record.
- Single IPs or CIDR ranges
- Rejects unknown sources
- Rejected calls are logged
- Works with secret tokens
21 days with every live feature. No card needed.
Only your servers can create conversions
- Allowed
198.51.100.10- Allowed range
198.51.100.0/24
| Source IP | Result |
|---|---|
198.51.100.10 | Accepted |
198.51.100.42 | Accepted |
192.0.2.44 | Rejected, not on list |
Teams that work with us
IP allowlisting for postbacks in detail
Accept conversion postbacks only from server IP addresses you trust, so no one can create a fake conversion.
Why limit postback sources
Anyone who learns your postback URL could call it with a guessed click ID and create a fake conversion. An IP allowlist stops this. trackspot.ai accepts a postback only if it comes from an address on your list, and it rejects every other request with an error response.
What to add to the list
Add the public IP addresses of the servers that send postbacks, such as your backend or your billing provider. You can add single addresses or CIDR ranges like 203.0.113.0/24. Rejected requests stay in the postback log with the source IP, so you can see when a valid server is missing from the list.
- Your application servers
- Your billing or payment provider
- Any job server that confirms orders
Set it up in 4 steps
Each step names the screen in your dashboard. Guides with screenshots are in the help center.
Find the outbound IP addresses of the servers that send postbacks.
Go to Settings → Tracking → Postbacks → IP allowlist.
Add each address or CIDR range and save.
Send a test postback and check that it shows as accepted in Reports → Postback logs.
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 IP allowlisting for postbacks
What if my server IP changes?
Postbacks from the new IP are rejected until you add it. The rejected requests appear in the postback log, so you can add the address and send them again.
Does the allowlist affect the JavaScript tracker?
No. The allowlist applies to server postbacks only. Browser calls from the tracker come from visitors' devices.
Works well with
Server-to-server postbacks
Report conversions from your server to trackspot.ai with a postback URL, so browser limits and ad blockers cannot stop them.
Postback and error logs
See why an incoming postback failed, and inspect every outgoing postback with its response code and retry history.
Fraud detection Planned
Find and stop fake clicks, self-referrals and suspicious conversions before you pay commission on them.
Webhooks
Send event data to your own systems when conversions, partners or payouts are created or change.
Try trackspot.ai on your own program
IP allowlisting for postbacks is planned. Tracking, commissions, payouts and the partner portal are in the 21-day trial today.