Send a real test conversion to your postback URL and see the exact HTTP status and response body the tracker returns - 200 OK, 1, JSON, or an error. Build the URL with the Postback URL Builder and generate a test id with the Click ID Generator.

The Postback Tester fires a real request to your postback URL from our server and shows you exactly what the tracker returns: the HTTP status code, the response body (200 OK, 1, JSON, or an error message) and the response time. It is the quickest way to confirm a server-to-server integration works before you send live traffic.
Yes. A real GET request is sent to your postback URL from our server, so a test conversion may be recorded in your tracker. Always use a test click id when checking.
A 200 status (and any 2xx) means the tracker accepted the request. Many networks also return a short body such as “OK” or “1” to confirm the conversion was logged - check the response body against your network’s documentation.
A non-success status usually means a wrong URL, missing or invalid parameters, an unreachable endpoint, or the tracker rejecting the click id. The response body often explains what went wrong.
Generate a conversion pixel - image tag, JS snippet or S2S postback URL - with parameters.
Open tool →Fire a tracking pixel and check whether the request is sent and works.
Open tool →Build a server-to-server postback URL with parameters and macros like {clickid} and {payout}.
Open tool →