Server to Server Tracking that survives the cookie.
S2S postback tracking records conversions server-side using a click ID instead of a browser cookie. Attribution keeps working through Safari ITP, ad blockers, in-app browsers and cross-device journeys — because the browser was never load-bearing to begin with.
Three steps, no browser required.
Server to server tracking replaces the conversion pixel with a direct call between two servers. The browser carries one opaque value forward; everything that matters happens where an ad blocker cannot reach.
1. Click
A publisher sends a visitor through a tracking link. AffClix records the click, mints a unique click ID, and redirects to your landing page in under 50 milliseconds, passing the click ID through in the URL.
2. Store
Your site captures the click ID and holds it alongside the session or order — a hidden form field, a server-side session, or a column on the order record. No cookie is required for attribution to survive.
3. Postback
On conversion, your server calls the AffClix postback URL with that click ID and the sale value. The conversion is attributed, deduplicated, fraud-scored, and reflected in reporting immediately.
One URL, and you are tracking.
A postback is a plain HTTPS GET or POST from your server to ours. It carries the click ID, and optionally a sale amount, an order reference, a currency, and an event name. Anything that can make an HTTP request can fire one.
Начать бесплатный пробный период- Global postback for the whole account, or a per-offer URL where terms differ
- GET or POST, with a signed token so a postback cannot be forged
- Order ID deduplication, so a retried call never double-counts a sale
- Event-level postbacks for lead, sale, and repeat-order in one integration
- Multi-currency values converted at the rate on the conversion date
Pass the data you actually report on.
Macros are placeholders in a tracking link that AffClix substitutes at click time and hands back on the postback. They are what turn a flat conversion count into a report you can optimise against.
Начать бесплатный пробный период- Up to 15 sub-affiliate parameters for placement, creative, or traffic source
- Six advertiser-side parameters for your own internal identifiers
- Geo, device, OS, browser and carrier captured automatically at click time
- Values returned on the postback, so publisher reports match yours exactly
- Consistent macro names across web, mobile app, and ecommerce integrations
Prove it fires before you launch.
Most S2S problems are silent: the postback fires into a typo, or the click ID never made it to the order record, and nobody notices until a publisher disputes an invoice. Test the whole path first.
Начать бесплатный пробный период- Free link tester traces the full redirect chain from a real IP in 100+ countries
- Fire a test postback and see the parsed result before going live
- Postback logs show every inbound call, its parameters, and why it was rejected
- Dedicated test mode that does not pollute production reporting
- Alerts when an offer stops receiving postbacks it previously received
Server to server tracking questions
What is server to server tracking?
Server to server tracking, also called S2S or postback tracking, records conversions through a direct call between your server and the tracking platform rather than through a pixel in the visitor's browser. A click ID issued at click time links the conversion back to the publisher who drove it.
What is an S2S postback?
A postback is the HTTPS request your server sends when a conversion happens. It carries the click ID recorded at click time, and usually a sale value and order reference. Because it runs server-side, no ad blocker, cookie policy, or browser privacy feature can prevent it.
Is S2S tracking better than pixel tracking?
For accuracy, yes. Pixels depend on the browser executing a third-party request, which Safari ITP, Firefox ETP, ad blockers and in-app browsers all interfere with. S2S depends only on your own server, so it is unaffected by any of them and works across devices. Pixels remain useful where a partner cannot fire a server-side call.
Does S2S tracking work without cookies?
Yes — that is the point of it. The click ID travels in the URL and is stored by your application against the session or order. No first-party or third-party cookie is involved, so attribution survives cookie-blocking browsers and cross-device journeys.
How do I stop duplicate conversions?
Send a unique order reference with every postback. AffClix deduplicates on that value inside the attribution window, so a retried or repeated call is recorded once. Without it, a network timeout that triggers a retry can be counted twice.
What if my platform cannot fire a postback?
Most cannot out of the box, which is why AffClix ships adapters for Shopify, WooCommerce, BigCommerce and Magento that fire the postback for you, plus mobile integrations for the major measurement partners. If none fits, the postback is a single HTTPS call any backend can make.
Track conversions the cookie cannot break.
Fire your first S2S postback in minutes and confirm it end to end with the free link tester before a single publisher sends traffic.
