Take your app to the next level with Affise MMP (Mobile Measurement Partner)
Join Now ⚡

Updates — 08 May 2023

Server Parallel Tracking is Coming to Affise

  • Blog
  • Updates
  • Affise Releases Server Parallel Tracking

Affise Releases Server Parallel Tracking

Almost three years passed since Google announced their solution of parallel tracking. The “blink of an eye” time reduction has turned into a completely new era for all market players. And the benefit of the parallel tracking as the concept evidently became widely popular. Thus, its presence is no longer considered as a privilege but as a must for more and more companies. What’s more, advertisers and networks are looking for solutions that provide server-to-server parallel tracking and doubt those that don’t.  

However, there is a challenge we want to address today. How often upon clicking an ad do you get irritated with a pacing sequence of changing links or a failure to reach the desirable destination because of internet connection loss? For many users it is just a matter of convenience, but what if we talk about brands and networks whose revenue depends on traffic and respectively decreases when a user doesn’t land on the final page.

It's time to use server parallel tracking! And here are reasons why:

  • Broken or weak internet connection may hamper reaching the final landing page
  • The redirect chain unload enhances user experience 
  • Redirect time significantly influences conversion rate. The less time a user spends going through redirecting, the higher the CR is.
  • Chances to work with more reliable and profitable affiliates are much higher

Affise has no intention to stay behind the scene. We aim at being a solid player in the affiliate marketing field, thus, we’re coming with our server parallel tracking solution.

Standard S2S vs. Server Parallel Tracking

For most marketers the principle of operation is quite familiar and understandable, instead of following through all subsequent redirect chain elements, a user lands immediately on the final landing page. At the same time, you don’t lose any redirects data from now on all redirects are made server-side. 

In short, server-side tracking implies that the server makes a direct request to a destination endpoint rather than hold the client’s browser responsible for making that request.

Thus, if a regular redirect scheme for a user looks like:

  1. http://client.go2affise.com/click?pid=1&offer_id=1
  2. https://app.appsflyer.com/xxxx
  3. https://some.tracking/
  4. https://apps.apple.com/

With Server Parallel Tracking it’ll look like:

  1. http://client.go2affise.com/click?pid=1&offer_id=1
  2. https://apps.apple.com/

While the 2nd and the 3rd steps are called directly on the server, and the user is redirected straight to the App Store or to any other final landing tracking URL of the offer.

Setting Up a Parallel Tracking URL

From the integration point of view, a parallel tracking URL doesn’t pose any difficulty for Affise users. At the offer preview page users generate a tracking link and give it to partners, the same integration flow runs with advertisers. To start server parallel tracking just fill in the field “Parallel tracking URL”.

The “Tracking URL” field in this case is for a direct landing URL (a user needs to reach) and “Parallel tracking URL” field is for the advertiser’s tracking link (the one generated at the advertiser’s platform). 

Moreover, no need to worry about the targeting. All targeting rules are taken into account the same as with the standard flow. 

For example, when the condition on an offer geo is not met, the click will be sent to the Trafficback URL without enabling server parallel tracking. Quite a simple rule: if there’s a click on our tracking URL, and it wasn’t redirected to the Trafficback or no clickid was generated, the redirect is hooked via Parallel tracking URL.

Work with Other Trackers

When working with other trackers, do not forget to add the required by trackers’ conditions parameters. For example, while working with AppsFlyer do not forget to add &redirect=false to the link placed in the field “Parallel tracking field”

Conversion Tracking

The Affise user will receive a postback as usual – from his direct advertiser. Though to be sure that the final landing page’s tracker could properly match the info on a real click with its clickid value, and descend it via all the chain’s elements in postbacks, one must indicate {clickid} both in the Tracking URL and Parallel tracking URL. Each subsequent element needs to pass it in its own corresponding parameter.

Discover More Opportunities with Server Parallel Tracking

It’s worth mentioning the current version is not the only variation of parallel tracking. Further, we are about to introduce an opportunity to reach the advertiser’s final page without following an Affise tracking URL. Thus a fascinating journey only begins enabling Affise users to plunge into a powerful world of Parallel Tracking.

The feature is available for Custom plans. Should you have questions regarding the set-up, contact your Customer Success manager.

Your company is searching for a full technology stack to drive affiliate business?

This article is reffered with:

Share this article
Affise Academy

Written by

Affise Academy

Affise is a partner marketing platform for brands, advertisers and agencies to scale via all possible performance marketing channels. Synergy of technology and our long standing experience lets you expand your partnerships, automate every step of the campaign lifecycle and make data-driven decisions.

See all articles →

Sign up to receive our newsletter

Stay on top of the competition. Let us keep you updated with news, insights, and more

email envelope