What Is S2S Tracking, and Why Would You Actually Need It?

# What Is S2S Tracking, and Why Would You Actually Need It?

If you've spent any time around affiliate programmes, you've probably seen "S2S" mentioned somewhere and moved on without really knowing what it means. It sounds technical, but the idea behind it is simple, and understanding it explains a lot about why some affiliate programmes track sales more reliably than others.

The old way: tracking through the customer's browser

Most affiliate tracking has traditionally worked through something called a cookie. Here's the basic idea: someone clicks an affiliate link, a small file called a cookie gets stored in their browser, and if they buy something shortly after, that cookie tells the system which affiliate should get credit for the sale.

It's a clever system, but it has a weak point: it depends entirely on the customer's browser cooperating. And browsers, increasingly, don't.

• Safari, Firefox, and Chrome have all been tightening restrictions on this kind of tracking, specifically because it raises privacy concerns.

• If someone clicks on their phone and buys later on their laptop, the cookie doesn't follow them — so the sale often doesn't get tracked at all, even though the affiliate genuinely caused it.

• Ad blockers and privacy tools can block these cookies outright.

• The system can be manipulated. Because the tracking happens visibly in the browser, it's relatively easy for bad actors to fake it and claim credit for sales they had nothing to do with.

None of this means the sale didn't happen or that the affiliate didn't deserve credit. It just means the tracking failed to catch it.

The better way: server-to-server tracking

Server-to-server tracking, or S2S, solves this by removing the customer's browser from the equation entirely.

Here's what happens instead: when someone completes a purchase, the merchant's own server sends a message directly to the affiliate network's server, confirming the sale happened and which affiliate should get credit. This message travels quietly in the background, server to server, completely invisible to the customer and completely independent of their browser, their cookies, or whatever privacy settings they have turned on.

Think of it like the difference between mailing someone a letter and hoping it arrives, versus calling them directly to confirm. The cookie method hopes the message survives the trip through the customer's browser. S2S just delivers the message directly, server to server, with nothing in between that can lose it along the way.

Why this actually matters

A few concrete things change once a programme switches to S2S:

More sales get counted accurately. Since nothing depends on the customer's browser, conversions that used to slip through the cracks — blocked cookies, cleared browsers, someone switching devices between the click and the purchase — now get tracked properly. This usually shows up as a meaningful jump in tracked conversions, not because more sales are suddenly happening, but because the ones that were already happening are finally being counted.

It follows customers across devices. Someone can click a link on their phone and buy later on their laptop, and S2S can still connect the two, because it isn't relying on a cookie stuck in one specific browser.

It's much harder to fake. Because the confirmation happens server to server instead of visibly in the browser, it's far more difficult for someone to fraudulently claim credit for a sale they didn't actually influence.

It holds up as privacy rules keep tightening. Cookie tracking keeps getting more restricted every year. S2S doesn't rely on cookies in the first place, so it isn't affected by most of these changes.

The honest trade-off

S2S isn't automatically the right call for every situation, and it's worth being upfront about that. Setting it up takes more technical work than simply adding a tracking pixel to a page — someone has to build the connection between the merchant's server and the affiliate network's server, which is why plenty of programmes still default to the simpler cookie method even though it's the less reliable one long-term.

There's also a common mistake worth knowing about: some programmes run S2S and pixel tracking at the same time without a way to tell the two apart, which ends up double-counting the same sale. The fix is straightforward once you know to look for it — treat S2S as the source of truth, and ignore any pixel record that matches a sale S2S already caught.

Why this is worth knowing, even if you're not technical

You don't need to understand the technical implementation to understand what's at stake: if a programme is still relying only on cookies, it's very likely undercounting real sales, particularly from partners like content creators or review sites whose customers often browse on one device and buy on another. That undercount isn't just a reporting inconvenience — it means partners aren't getting properly credited for the sales they're actually driving, which is exactly the kind of gap worth checking for in any tracking setup.