Trafficback

The trafficback mechanism allows you to redirect traffic that does not fit in geography to another stream, offer or third-party site. Traffic can be sent via a redirect, an iframe display, or a direct request to the target resource.

How to setup?

Trafficback is configured within the flow or split test. The trafficback field is located below the landing page selection, link shortening and redirect domain selection. Specified as a full link with https:// at the beginning and a complete set of all the necessary parameters. Supports some macros.

If you don't see the trafficback field, there are two options:

  • The offer works for the whole world, so it supports all countries and geo errors are basically impossible.
  • It is forbidden to add trafficback to the offer. You can request trafback permission from your personal manager.

You can also work with traffic back inside split tests. Trafficback is specified in the settings and supports the same macros as trafficback in the stream.

Blocking conditions

You can use trafficback with the help of four basic conditions:

  • Ban bots. Check visitor visits for headers and deny access to those that look like search engine and social media bots.
  • Ban by geo. Visitors from countries that are not supported in the offer will be sent for trafback. This option is always active if a trafficback link is specified.
  • Ban by language. Checks if the user's language matches their country. If none of the browser languages is specific to the selected country, the visitor is blocked.
  • Ban by filters. The visitor's IP address is checked against system traffic filtering blacklists. All known bots and suspicious visits are blocked.

The basic methods of blocking visits are quick to set up, easy to work, but don't allow you to keep track of the number of clicks that went through trafficback. Only targeted visits will be counted.

In some networks, you can access the traffic filtering section with full-featured campaigns and filters. You can create your own traffic filtering campaign and customize it according to the criteria you need: geography, language check, filter blacklists, IP whitelist, junk visits, stop words and required words in the URL.

To link a campaign to the flow, turn off all the basic filtering checkboxes and in the drop-down list, instead of "No filters", select the campaign you need. This way you can keep a complete record of both targeted visits and filtered visitors.

Working methods

You can use several methods to display the trafficback

  • Redirect to link. The system will redirect the visitor to the selected link as standard. 302 Found header is used - temporary redirect.
  • Redirect and glue the domain. The system will redirect using the 301 Moved Permanently header - a permanent redirect. According to rumors, this allows you to glue the source domain with the target one.
  • Redirect via separate page. Before the redirect, the user will see an intermediate browser check page and will be redirected after three seconds. This is rumored to be safer than a simple redirect.
  • Show link in iframe. The trafficback URL will be opened inside a full page iframe. Important! The target site must not disable frames using headers!
  • Show contents by the URL. The server will load the content of the page from the specified link and display it unchanged. Important! If the resources (styles, scripts, images, links) of the landing page use relative paths, they won't work!
  • Show contents by the URL with base replacement. The server will load the page content and add the correct base href tag. This will load all scripts, styles, and pictures, and leave all links working. The best option.

Macros in link

You can add some parameters from the origin request to the link.

  • {geo} - ISO code of the visitor's country.
  • {host} - the domain where the site or flow was opened.
  • {flow} - flow ID.
  • {utms} - utm_source tag.
  • {utmc} - utm_campaign tag.
  • {utmn} - utm_content tag.
  • {utmt} - utm_term tag.
  • {utmm} - utm_medium tag.
  • {subid} - subid parameter from the request.
  • {uuid} - uuid parameter from the request.
  • {uid} - unique click ID from fbclid, gclid, adclid, uid or unique_id.

Note to administrator

These subtleties will be useful to the owners of networks based on AlterCPA. You, as a webmaster, can send this note to your manager so that he can set up the necessary options for you.

  1. You can make generic trafficbacks for TDS and redirect sites. They are configured within these sites and are used if the user has not set their own trafficback.
  2. You can disable using of trafficbacks with the offer. To do this, go to the "Control - Offers" section, find the desired offer, click "Settings" and scroll down to the "Technical Capabilities" section. Uncheck "Work with trafficback".
  3. You can allow certain users to add trafficbacks even in those offers where they are prohibited by the previous paragraph. To do this, go to the "Control - People" section, find the desired user and click "Edit". In the "Access to the site" section, check the box "Always can use trafficback".