TapBaton
Start free
All free tools

Postback URL Inspector

Review a callback URL locally. Examine its fields and check for unresolved macros or repeated parameter names.

Use the exact parameter name required by your receiver. Leave empty to skip this check.

Nothing is sent. This checks the URL structure, not endpoint availability, provider macro support or conversion delivery.

Read the callback before you troubleshoot the conversion.

When a conversion does not appear where you expect, begin with the values being sent. A postback URL can look plausible while containing an empty identifier, an unresolved macro or a duplicate key. A local inspection helps you separate the URL's contents from questions that only the receiving system can answer.

  1. 1

    Paste the callback URL

    Inspect a configured template or a URL captured by your own integration tools. Remove credentials or personal data before sharing a callback with anybody else.

  2. 2

    Check the returned fields

    Look for the expected click identifier, status and amount. In a template, macro placeholders are intentional. In an actual outgoing callback, those placeholders normally need to have been replaced by values.

  3. 3

    Verify the receiving record

    Compare the URL with the receiving integration's contract, then review its event logs. A syntactically valid URL does not tell you whether the click exists or the event was accepted.

Inspection stays local. Delivery must be checked at the receiver.

The inspector does not make HTTP requests or replay callbacks, so inspecting a URL cannot create a conversion. It cannot inspect request headers, response codes or a JSON body that is not part of the URL. Use the sender and receiver's integration tools to investigate those parts of the exchange.

Understand the path from postback to conversion

Common questions

Is this a live postback tester?

No. It inspects the URL you provide without sending it. Use it before a live integration test to check the fields and avoid accidentally replaying a real conversion.

Is an unresolved macro always an error?

No. A configured callback template is expected to contain placeholders. The same placeholder in a callback that has already been sent can indicate that the sender did not recognise or populate it. Check the sender's supported syntax.

Does a successful HTTP response prove attribution?

No. A response alone does not prove the event was matched to a click or counted in a report. Check the response body and the receiver's conversion record for the outcome defined by that integration.

Can the inspector validate any tracker integration?

It can inspect HTTP and HTTPS URLs, but providers have different contracts. Compare the decoded values with the receiver's required fields, supported statuses and validation rules.

Useful next steps

All free tools

URL Parameter Inspector

Read decoded query parameters, spot repeated keys and check what a campaign URL actually contains.

UTM Campaign URL Builder

Add source, medium and campaign tags to a destination URL. Keep naming consistent before sharing the link.

Postback URL Builder

Map click IDs, conversion status and payout values to a callback URL with the macros your network provides.