Time to read: 3 min.

The article covers the following topics:

⚠️ Server Parallel Tracking is available by request. Contact your Affise account manager to get the feature.

What is Server Parallel Tracking?

When an end-user makes a click and goes to a website with an offer, his browser is responsible for all redirects the end-user needs to face until the offer page is reached. Unstable Internet connection, too many redirects visible in the browser, high ping - all of that can result in the situation when the end-user doesn't reach the offer page at all. Traffic is lost. Affise Server Parallel Tracking allows hiding the number of redirects for the end-user so he can reach the offer page much faster. Also there is no dependence on the user's browser. As a result, you won't lose traffic: the end-user will get to the webpage with the offer without interruption or long time waiting.

Technically Affise allows the end-user to get to the offer page right after he was redirected to the Affise tracking URL. All in-between redirects are not visible for the end-user, despite they're actually performed in parallel. When the end-user came to the Affise tracking URL, Affise servers send information about the registered click to the Advertiser via the Advertiser tracking URL. The end-user doesn't participate in this process, he goes directly to the offer page.

Affise Server Parallel Tracking

Let's see how it works in the user interface in Affise. To start using Affise Server Parallel Tracking you need to go to Offers section -> Settings of a particular offer -> Tracking tab:

tracking.png

Where:

  • Tracking URL: insert the link to the page where the offer is located. Put the {clickid} macro there to ensure the further conversion will be matched with the click.

  • Parallel tracking URL: insert the tracking link given by the Advertiser. Put all necessary parameters or macros, including the mandatory one - {clickid}.

The list of all relevant macros is here.

In case your advertiser works with Appsflyer, you have to add one more mandatory parameter: &redirect=false.

For Branch one more mandatory parameter is &%24s2s=true.

❗ You need to add the &clickid= parameter to your postback link to be able to match clicks and conversions correctly.

The way of the end-user looks like:

Affiliate's tracking URL -> Affise tracking URL (click is registered in Affise) -> the offer page.

Affise sends information about the click to the advertiser's tracking URL after the end-user reached the offer page.

The end-user won't see all redirects after he followed Affise tracking link, but your advertiser will receive all the information about the click and pass it further if needed.

Targeting restrictions you have in the offer in 'Targeting groups' tab are taken into account. Once click comes to Affise, the system decides whether to pass it further or not.

FAQ

1. Does the system take into account targeting restrictions?

Targeting is taken into account as with the standard flow: for example, when condition on country is not met, the click will be sent to the trafficback URL. Server parallel tracking doesn't work in this case.

2. Can I use the Additional URL while using Affise Server Parallel Tracking?

Yes. If you use the Additional URL, you can put an additional link for Server Parallel tracking as well. The logic of the Server Parallel tracking is applied to the pair of additional links.

Both links work in tandem. One pair of links have a common weight.

Let's suppose, you have the following settings in the offer (both main and additional links):

30% of traffic go to the pair of additional links according to the general logic of server parallel tracking work.

70% of traffic go to the pair of main links according to the general logic of server parallel tracking work.

Thus, if you want to use Additional URLs and Affise Server Parallel tracking, you should have both the pair of main links and the pair of additional links.

3. Can I use the Landing page while using Affise Server Parallel Tracking?

When the click is registered in Affise, the system initiates the request by the link you've inserted in the Parallel tracking URL field. It doesn't depend on where the user will be redirected to:

a. To the link in the Landing field:

landing.png

b. To the link in the Tracking URL field:

Let's suppose the link in the Tracking and in the Landing fields is the same link, but for different application languages.

Once Affise registers the click, it will go further according to Landing settings. At the same time Affise will send information about the click to the link in the Parallel tracking URL. As a result the advertiser will receive one click for this application.

❗ The advertiser should have one campaign for all languages of the same application, which the campaign is dedicated to. Thus, traffic won't be split according to different languages.

You may also find the following articles helpful:


If you still have any questions left on Affise Server Parallel Tracking, feel free to address them to Affise Technical Support Team via [email protected] as long as to contact your Dedicated Account Manager.

Did this answer your question?