Outgoing postbacks

You can send postback requests to third-party services when leads change. This is useful for integrating with various ad networks and optimizing ads. Postbacks are configured within the flow.

Available tags

In the flow settings, you can specify tags and macros to track traffic. The following parameters are available to you, which are collected in statistics:

Statistics are generated only for these six tags. Other parameters and tags are ignored when recording a visit and do not participate in the creation of statistics. It makes no sense to use some sub1 or s2, we will ignore them.

Tags and postbacks

You can also use additional parameters that are not used in statistics, but can be used in postbacks, for example, to optimize mobile applications or ad networks:

Available events

You have several options for setting up postbacks within a flow:

Available macros

Data is inserted into the postback using macros in curly braces:

Facebook events

The server pixel for Facebook is installed in the "New" postback and can look like this:


In this link you need to set your data instead of texts:

Specifying the pixel ID and token is mandatory; changing the event is optional.

Sending leads

You can send leads from the tracker to the affiliate network. Please note that this submission format will not be guaranteed or traceable. We do not recommend using this method in your work.

Create a "Thank you" page that will request a standard postback and submit the data provided by the user in a form on the site. To send leads, fill out the "New lead" postback and include all the lead data that you collect on the "Thank you" page. For example, such a postback will send a lead to a network based on AlterCPA:

https://domain.com/api/wm/push.json?id=TOKEN&offer=1&flow=2&name={name}&phone={phone}&ip={ip} &country={geo}&sub1={click}

This submission format may not be suitable for you, as the target network only accepts POST requests. To implement them, use the following instructions.

POST request

By default, postbacks are sent as GET requests. If absolutely necessary, you can split the postback into a link and a POST part of the request. To do this, in the middle of the link, insert the macro |POST|, before which there will be a link (the GET part of the request), and after which the data will go. For example:


Data is transmitted in the classic URL Encoded format, sending JSON using this method is not supported.

If for some reason you need to send a request in JSON format, instead of the |POST| macro, use the |JSON| macro with the same principles. For example:


This macro will split the link into the link and the JSON part and send a request with the header Content-type: application/json.

Important! Please note that this functionality was created for fun and we do not think that you will seriously use it in your work. You won't? Is it true? Oops.

Postbacks log

All postbacks that are sent from the tracker via links in the flows are stored in the "Outgoing postbacks" subsection of the "Logs" section. The following information about postbacks is available to you:

You can view detailed information about the request if you click on "Show" in the "Info" column: