Flows are the backbone of the tracker. We pass all traffic through flows. The number of available flows is strictly limited by your tariff plan, you will not be able to create more flows than allowed. The amount of traffic has no strict limitations - if you overflow leads or clicks, they will be processed by the tracker in any case.
Working with flows is done in the "Flows" section of the tracker.
It presents a table with created flows, which indicates:
To add a flow, click on "Create new flow" above the table. You need to enter its name and set up the first way that traffic will go to. The way can be site or a link with the selected working method.
After creating a flow, you will be redirected to its settings page. Here you can add new ways, configure traffic filters, setup integration with affiliate network, add postbacks and tags.
A flow consists of one or several ways. The first way is added automatically when the flow is created. To change its link, site or method of operation, click on the edit button in the list of ways.
To add a way in the flow, click on "Create new way" below the table. You will need to provide a title, select site from the repository or provide a link and its working method.
The following settings are available for the way:
You can also configure the "next step" of the path. If you are working with a prelanding-landing link, your prelanding will be the main step of the path, and the landing page will be the next one. Don’t forget to get the next step link on the prelanding page via the {next} macro in the link or site code. The parameters of the next step are similar to the main:
Below the table with the list of ways are way rotation settings. You can choose an algorithm by which the tracker will choose the best way for the visitor using the "multi-armed bandits" method. By default, the selected way is assigned to the client, but you can activate the rotation and show the client a new way each visit.
There are two main methods for using a flow: working with a link and working with a local file.
Both a local file, a link through the main server, and a link through the site store work the same way and use the same implementation mechanism. You can use any option you like with the same result.
When using a link, it is not recommended to use the system domain - it may be blacklisted by advertising networks. Be sure to park your own domains to send traffic.
Select a parked domain in the flow settings and the link will be changed to the new domain. You can also bind a domain to a flow. This will open the flow on the main page of the domain without specifying additional characters in the way.
Learn more about domain parkingYou can enable traffic filters in the flow and send unwanted visits to trafficback.
Available filtering options:
The main task of the tracker is receiving notifications about successful actions in target networks. To do this, you need to set up links and sites to pass the click ID, and postback to the target affiliate network.
Select the affiliate network you need in the "Integration" section and check the "Automatically add click ID to link" checkbox. Copy the received postbacks and install them in the affiliate network.
If your network doesn't support server postbacks, you can enable tracking using pixels. To do this, check the "Allow tracking via pixels" box and copy the pixel code to your network.
Learn more about incoming postbacksIn the flow settings, you can specify tags and macros to track traffic. The following parameters are available to you, which are collected in statistics:
subid.utm_source.utm_campaign.utm_content.utm_term.utm_medium.cpc parameter and its currency in the currency parameter.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.
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:
fbclid, gclid, adclid, clid, adid.data1 or d1.data2 or d2.Tags can be used in postbacks for integration with ad networks. You can set postbacks in the flow settings for the following events:
In the URL field in ways and trafficback, you can use macros. They will be replaced by the corresponding parameters at the time of transition.
{click} - character identifier of the click.{flow} - character identifier of the flow.{geo} - ISO code of the country of the click.{query} - the line of GET-parameters.{next} - the link to the second step of the flow.{utm_source} - UTM Source tag.{utm_campaign} - UTM Campaign tag.{utm_content} - UTM Content tag.{utm_term} - UTM Term tag.{utm_medium} - UTM Medium tag.{host} - domain.{subid} - SubID tag.{adid} - click ID in the ad network.{data1} - additional data field 1.{data2} - additional data field 2.{esub} - encrypted SubID tag.{eutms} - encrypted UTM Source tag.{eutmc} - encrypted UTM Campaign tag.{eutmn} - encrypted UTM Content tag.{eutmt} - encrypted UTM Term tag.{eutmm} - encrypted UTM Medium tag.{ed1} - encrypted additional data field 1.{ed2} - encrypted additional data field 2.Lifehack: when working with local files, you can use the {geo} parameter in the link to open different files depending on the visitor's country, for example: pages/{geo}.html.