Server-to-Server (S2S) Tracking
TL;DR – Server-to-Server (S2S) tracking is a method of recording affiliate conversions where data is passed directly between two servers — without relying on a browser cookie or JavaScript pixel. When a user completes a qualifying action, the advertiser’s server sends conversion data straight to the affiliate platform’s server, using a unique Click ID to match the conversion to the right publisher. It is more reliable than cookie-based tracking in mobile environments, private browsing, and high ad-blocker audiences — and it is one of the two primary tracking methods on Involve Asia.
What Is Server-to-Server (S2S) Tracking?
Server-to-Server (S2S) tracking — also called server-based tracking, postback tracking, or S2S integration — is a conversion attribution method that bypasses the user’s browser entirely. Instead of reading a tracking cookie set in a browser, S2S tracking stores a unique identifier (the Click ID) on the advertiser’s own server and uses it to match conversions back to the originating publisher when they occur.
The term “server-to-server” describes exactly how data moves: from the advertiser’s server to the affiliate platform’s server — a direct, browser-independent communication that is not affected by cookie restrictions, JavaScript settings, ad blockers, or device switching.
Involve Asia tracks conversions via a combination of links, cookies, and postback URLs, depending on each offer. S2S is the most technically robust of these methods — and is the preferred approach for mobile app offers, high-privacy environments, and enterprise-level advertiser integrations.
Why S2S Tracking Exists
Standard cookie-based tracking — where a tracking cookie is set in the user’s browser at the time of the click — works well in most desktop browsing scenarios. But the modern browsing environment has introduced several conditions that make cookies unreliable:
- Browser privacy restrictions: Safari’s Intelligent Tracking Prevention (ITP) limits the lifespan of third-party tracking cookies to as little as 24 hours. Firefox’s Enhanced Tracking Protection (ETP) blocks known tracking domains entirely. These restrictions — introduced to protect user privacy — directly reduce the effectiveness of cookie-based affiliate attribution.
- Ad blockers and privacy extensions: Browser extensions that block tracking scripts prevent cookies from being set in the first place. A user with an ad blocker may click an affiliate link but never have a tracking cookie written to their browser — making attribution impossible with pixel-only tracking.
- Private browsing/incognito mode: Cookies set during private browsing sessions are deleted when the session ends. If a user clicks an affiliate link in incognito mode and then purchases in a regular browser session, the cookie does not persist across sessions.
- Cross-device behaviour: A user who clicks an affiliate link on their phone but completes the purchase on their laptop is browsing on two separate devices with two separate browser cookie stores. The cookie set on the phone does not transfer to the laptop — standard cookie tracking loses this conversion entirely.
- Mobile app environments: Mobile apps do not have a traditional browser cookie store. Cookie-based tracking does not work inside an app’s native environment — conversions from mobile apps require S2S tracking or SDK-based integration.
S2S tracking was developed specifically to address these limitations. By storing the Click ID on the server rather than in the browser, it creates a tracking mechanism that is independent of what the user’s browser does.
Related Terms: Postback URL · Pixel Tracking · Tracking Cookie · Integration · Conversion · Attribution Window · Affiliate Link
Ready to grow with Involve Asia?
Whether you’re a brand looking to scale or a creator ready to monetize — we’ve got the tools, data and network to help you grow.
