TapBaton
Start free
All free tools

Postback URL Builder

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

Paste the receiving URL from your tracker. Existing query parameters are preserved.

Map what the sender returns

Parameter names belong to your receiving tracker. Macros belong to the network sending the postback. These editable examples are not a provider preset.

Clear both fields to omit a row. Braces, double braces, brackets and percent-wrapped macros are preserved; ordinary text is URL-encoded.

Keep the click identifier connected to the conversion.

A postback tells a receiving system about an event recorded by a partner or destination. The URL has two sides: parameter names expected by the receiver, and values or macros supplied by the sender. Build that mapping deliberately so that a returned event can be connected to the original click.

  1. 1

    Start with the receiving URL

    Use the callback endpoint supplied by your tracker or conversion integration. Keep any required existing parameters and use the parameter names documented by that receiver.

  2. 2

    Map the sender's macros

    Enter the click ID macro that your network or partner documents. Add the status and payout fields you need. Macro names and delimiters vary between systems; a generic example is not a provider configuration.

  3. 3

    Review the complete mapping

    Compare every field with both sides' documentation. Copy the generated URL into the sending platform, then use that platform's test procedure and check the receiving event record.

Building the URL does not send an event.

This tool assembles a URL locally. It does not contact the endpoint or confirm delivery, attribution, authentication or deduplication. Some integrations require a JSON request body, headers or a signature instead of a query-string callback; use the receiving system's documented contract in those cases.

Read the postback and conversion event guide

Common questions

Which network macros should I use?

Use the exact macros documented by the platform that sends the callback. Do not copy a click ID or payout macro from another provider unless that provider explicitly supports the same syntax.

What is the click ID used for?

It is the identifier passed through the click journey and returned with the conversion. The receiver needs the expected identifier to associate that event with a recorded click. Campaign names alone are not a substitute.

Can I send a test conversion from this builder?

No. The builder only prepares the URL. Send tests through the integration's documented procedure and check the receiving system for the event and any validation errors.

Should I add a payout and currency?

Include them when the receiving contract expects them and the sender can supply them. Confirm the expected number format, currency field and meaning of the amount. An event count and its monetary value are different measurements.

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 Inspector

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