Postback Tester
Provides the transcript you need for escalations.
Open tool >Postback troubleshooting
Postback Not Received
Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.
Introduction
This scenario is about transport and validation. Your tracker logs successful deliveries, but the network sees nothing. The only way out is evidence from each hop.
Why the problem happens
Networks add antifraud defenses constantly; a new rule can silently drop callbacks.
- Partner WAF blocks your new IP range.
- TLS or cipher requirements changed and the handshake fails.
- Shared secrets rotated but the tracker still signs with the old key.
Common causes
- Firewall policies block outbound IPs.
- Rate limits throttle bursts after queues drain.
- Partners introduce new mandatory fields like currency or status.
- Payloads exceed size limits and get dropped.
Step-by-step troubleshooting
-
Export tracker logs
Capture timestamps, endpoints, response codes, and error bodies.
-
Replay with Postback Tester
Send the identical payload manually and log the response.
-
Verify infrastructure
Confirm outbound IPs, TLS, and firewall rules match partner documentation.
-
Sync timelines
Share transcripts and request partner logs for the same window.
Tools that help solve the problem
Postback URL Builder
Keeps macros and tokens accurate when recreating payloads.
Open tool >UTM Builder
Regenerates clean URLs so you can capture new click IDs for testing.
Open tool >Conclusion
Implement delivery monitoring for every scaled offer and keep an audit trail of IP, token, and endpoint changes.