Skip to main content

Server-to-server clicks with Branch

This article would help you if you want to setup S2S clicks in the campaigns running through Branch

Overview

The Trackier platform is capable of recording server-side clicks from your affiliates and will also be able to mask your advertiser's tracking link.

If you want the redirection to be fast-paced and also want to hide the advertiser's branch link from the publishers, you can do that by configuring S2S clicks. This configuration is advisable in the case that you see that there are more clicks on Branch and fewer on Trackier, indicating there has been some fraudulent activity.

What are server-side clicks (S2S clicks)?

Server-side clicks (often called S2S tracking) are a way of tracking user clicks where the click information is passed directly between servers, instead of relying on the user’s browser.

In a normal tracking flow, a click is recorded using:

  • browser cookies

  • pixels

  • JavaScript tags

In S2S tracking, the flow is different:

  • User clicks a tracking link

  • The click is recorded on a server (not the browser)

  • A unique identifier (like a click ID) is passed through URLs or APIs

  • That identifier is later used to match conversions and attribute performance

Why S2S clicks are used

  • More reliable than browser-based tracking

  • Not affected by ad blockers or cookie restrictions

  • Better for mobile apps and deep linking

  • Reduces data loss in attribution systems

In short:
S2S clicks = server-to-server communication that ensures tracking doesn’t depend on the user’s browser.

There are multiple ways to do that, and all of them are mentioned below. All the ways have their own requirements.

Please contact your account manager to enable this feature.

How to set it up?

You will find this setting on your campaign settings page. Once you enable the server-side clicks option, you will be asked for some more information.

1. Whitelist publishers for server-side clicks: You will get the option to restrict the server-side clicks only to specific publishers. If no publisher is selected in this section, it will automatically consider all the publishers.

2. S2S redirect URL: This is the section where you will have to add the landing page, where you want your publishers to redirect. This will be the final landing page.

S2S tracking

Method of adding S2S click tracking

Using GAID/IDFA Parameters

In this case, the device IDs will play their role in identifying the server-side clicks. You can find the tracking URL formats for this method down below.

Your advertiser's default campaign URL has to be in the format mentioned below.

Note: s2s=true is mandatory to be passed in the tracking link.

And the S2S URL that needs to be implemented in the Trackier panel will be the direct URL of the Play Store; there will be no changes needed in this URL since the GAID and IDFA values will be passed to the advertiser directly and you will receive those values from your publishers. An example URL is below.


Conclusion

S2S integration between Trackier and Branch provides a reliable and scalable way to track clicks and attribution across platforms. Correct setup of links, postbacks, and validation steps ensures accurate data flow and minimizes tracking loss.


We're thrilled to have put together a top-notch team of qualified experts who are available to handle any of your concerns and respond to any inquiries you may have. You can contact us at any time by sending an email to support@trackier.com or using the in-platform chat feature.


Did this answer your question?