Setting Up S2S Server-to-Server Postback Tracking with Keitaro & Voluum for Facebook/TikTok

Server-to-Server (S2S) postback tracking is the non-negotiable tracking backbone for professional affiliate media buyers. Relying on client-side pixel fires or browser cookies leaves media operations blind to 30% or more of completed conversions due to browser ad-blockers, tracking prevention policies, and network drops. Integrating trackers like Keitaro, Voluum, or RedTrack ensures 100% conversion attribution fidelity directly into Meta and TikTok ad managers.

🔍 Zoom 4K

1. S2S Postback Tracking Architecture & Flow

When a shopper clicks an ad, the tracking platform intercepts the click, records the platform-specific click identifier (e.g. fbclid or ttclid), generates a unique subid tracking parameter, and forwards the visitor to the landing page. Upon purchase completion on the affiliate network or e-commerce gateway, a server-side HTTP GET request (postback) notifies the tracker, which in turn calls Meta’s Conversions API directly.

🔍 Zoom 4K

2. Production Postback URL Configuration Parameters

Configure your affiliate network postback endpoint with standard tracking macros to ensure complete parameter handoff across systems.

# Standard Keitaro / Voluum S2S Postback URL Format
https://tracker.nolimit.shopping/postback?subid={subid}&payout={payout}&currency=USD&status={status}&txid={transaction_id}

🔍 Zoom 4K

3. Event Deduplication: Pixel + CAPI Synchronization

To avoid double-counting conversions when running both client-side pixel and server-side CAPI, pass an identical event_id parameter in both payloads. Meta’s event processing pipeline compares incoming events within a 48-hour window and deduplicates matching IDs automatically, preserving accurate reporting.