Postback and error logs
Fix a tracking problem yourself in minutes instead of waiting on a support ticket.
- Request URL and parameters
- HTTP response codes
- Clear error reasons
- Retry history
21 days with every live feature. No card needed.
Why a conversion did not appear
Incoming request
https://trk.example.com/t/postback
- Unknown click ID
- Response
400, click ID not found- Outgoing to partner
500, retried- Retry 1
200, delivered
Teams that work with us
Postback and error logs in detail
See why an incoming postback failed, and inspect every outgoing postback with its response code and retry history.
Incoming postbacks
Each server-to-server call that trackspot.ai rejects gets a row in the conversion error log. The row shows the parameters that arrived and the reason, for example an unknown click ID, a duplicate order ID or a conversion outside the attribution window.
- Parameters of the request
- Error code for each rejection
- Time of the call
Outgoing postbacks
When trackspot.ai sends a postback to a partner or a network, the delivery log shows the URL it called and the response code. If the partner server does not answer with a success code, trackspot.ai retries the call on a schedule. Each retry is listed, so you can see if the call went through later.
Why it matters
Most lost conversions come from a small mistake, such as a wrong parameter name or an expired click ID. The log shows you the exact request, so you can fix the setup and test it again at once. You can also send a partner the log entry as proof.
Set it up in 3 steps
Each step names the screen in your dashboard. Guides with screenshots are in the help center.
Open Logs in the trackspot.ai dashboard.
Select the conversion error log or the delivery log, and set the time range.
Read the parameters, the response code and the retries in each row.
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 postback and error logs
How long does trackspot.ai keep postback logs?
The conversion error log keeps each row for 180 days. The account owner can delete older rows sooner.
How many times does trackspot.ai retry a failed outgoing postback?
trackspot.ai retries up to seven times, with a longer wait between each try. After the last try, the call is marked as failed. A resend button is planned.
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.
Tracking for third-party networks
Work with networks and media buyers that use their own tracker, and send each conversion back to them with an outbound postback.
Admin alerts Planned
Get an email or in-app alert when a metric crosses a limit you set, such as a drop in conversions or a spike in clicks.
Webhooks
Send event data to your own systems when conversions, partners or payouts are created or change.
Try postback and error logs 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.