S2S (Server-to-Server)
S2S (Server-to-Server) passes conversions directly between servers via postback, without a browser pixel. For delayed deposits it is more reliable than browser tracking.
How S2S works
On a conversion the network server fires a postback to the tracker server, passing the click id and status. Nothing depends on the user's browser, so the event is not lost to blockers or a closed tab.
Why S2S in PWA
A gambling deposit often happens hours after the click. By then the browser pixel may lose the session, while an S2S postback delivers the conversion by click id at any time.
FAQ
- Why is S2S better than a pixel?
- It does not depend on the browser or blockers, so it is more reliable for delayed conversions like a deposit.
- What do I need for S2S?
- An end-to-end click id (subid) and a configured postback between network and tracker, then the event into CAPI.
- Does S2S fully replace the pixel?
- They are often used together with event_id deduplication: the pixel for instant events, S2S for reliable delivery.
Build your PWA in APEX in minutes
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free