At a Glance: This article is about how you can set up server-side click tracking for networks on Trackier Panel.
The Trackier Server-Side Click Tracking Guide explains how networks can enable Server-to-Server (S2S) click tracking to improve click accuracy, reduce fraudulent activity, and hide advertiser tracking links from publishers.
Unlike traditional browser-based redirects, S2S tracking processes clicks directly between servers, making the redirection faster and more secure.
Why Server-Side Click Tracking is Important
In some cases, advertisers or MMPs may report:
More clicks on their platform
Fewer clicks on Trackier
This can indicate:
Tracking loss
Redirect issues
Fraudulent or manipulated traffic
Server-side click tracking helps solve these problems by:
Improving click accuracy
Reducing dependency on browser redirects
Hiding advertiser URLs from publishers
Improving tracking reliability
Supporting secure attribution workflows
How do I 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 the other two questions.
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. Certain changes need to be made to this URL based on the method you will be using with your advertiser to send the clicks.
Using GAID and IDFA Value
In server-side click tracking, parameters and macros play a crucial role in passing and capturing information about a click or user interaction. The Gaid (Google Advertising ID) or IDFA (Identifier for Advertisers) are unique identifiers associated with mobile devices. These identifiers are important for tracking and attributing user actions in the context of mobile advertising.
Here's a brief overview of Gaid/IDFA parameters and macros in the context of server-side click tracking:
Gaid/IDFA Parameters:
Gaid (Google Advertising ID): A unique identifier associated with Android devices. It is used by advertisers to track and measure user activity for advertising purposes.
IDFA (Identifier for Advertisers): Similar to Gaid, but associated with iOS devices. It allows advertisers to track and attribute user actions for advertising campaigns.
Macros in Server-Side Click Tracking:
Macros are placeholders in tracking URLs that get replaced with actual values when a click occurs. They are used to dynamically insert information about the click, such as device information, timestamps, or identifiers.
Examples of Macros:
{gaid}: This macro could be used to represent the Google Advertising ID.
{idfa}: This macro could be used to represent the Identifier for Advertisers.
Note:
MMP (Mobile Measurement Partner) Requirement: To facilitate S2S tracking for networks and websites, it's crucial to have an MMP in place between Trackier and the landing page. This intermediary step is essential for ensuring seamless communication and data accuracy.
S2S Functionality for Networks and Websites: It's important to note that S2S won't work directly for networks and websites. The presence of an MMP becomes a critical element to bridge the gap and make the S2S process effective.
Broaden your Knowledge:
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.
