Reachoz MediaA visitor uses your coupon code. The order goes through. Does the network know that happened? Not automatically — and the gap between "a code was used" and "a sale was confirmed" is where a lot of publisher earnings quietly disappear. There are two ways this gets bridged: pixel-based tracking, and server-to-server (S2S) postback. They are not equally reliable.
Pixel and cookie tracking
The traditional method: a click sets a cookie in the visitor's browser, and a tracking pixel fires on the advertiser's confirmation page to report the sale back. It works, until it doesn't — and increasingly, it doesn't.
- Ad blockers and privacy extensions block a meaningful share of tracking pixels outright.
- Browsers increasingly limit or delete third-party cookies, especially across sessions or devices.
- A visitor who clears cookies, switches from mobile to desktop, or closes the tab before the confirmation page fully loads breaks the chain.
None of these failures are the publisher's fault, but they all show up the same way: a redemption that happened, with no record of it.
Server-to-server (S2S) postback
Instead of relying on the visitor's browser to report back, the advertiser's own server sends a direct confirmation to the network the moment an order is placed — no cookie, no pixel, no browser involved. The visitor's device does nothing extra; the two servers talk to each other directly.
S2S doesn't depend on anything the visitor's browser is willing to allow.
This is why S2S is the preferred method for any campaign with real money attached. It's also the only reliable option in categories where sales complete outside a browser entirely — in-app purchases, phone orders following a lead, or offline redemptions tied to a code.
Where coupon codes fit in
A dedicated coupon code (unique per publisher) is not a tracking method on its own — it's an identifier. What makes it useful is what happens after the order: if the advertiser's checkout reports which code was used back to the network (via S2S, or at minimum a matched sales report), the code becomes reliable proof of attribution. If it doesn't, the code alone tells you a discount was applied — not who should get credit, or whether the order stuck.
| Method | Survives ad blockers | Survives device switching | Confirms refunds |
|---|---|---|---|
| Pixel / cookie | No | No | Rarely |
| Coupon code alone | Yes | Yes | No |
| S2S postback | Yes | Yes | Yes, if configured |
What to ask for, on either side
As an advertiser, offering S2S tracking (even alongside a coupon code) is the single biggest thing you can do to make a campaign trustworthy to publishers — it removes the "did my sale even get counted" doubt entirely. As a publisher, it's reasonable to ask whether a campaign supports S2S before committing a major placement to it; a code-only campaign in a category with high cart abandonment or refund rates is a real risk to your reported earnings.
The takeaway
A coupon code is a good identifier. It's a weak tracking method on its own. Server-to-server postback is what actually closes the loop between a click and a confirmed, refund-adjusted sale — which is why every campaign on Reachoz Media is encouraged to connect it before launch.