Voluum S2S Tracking: The Postback Contour From Click to Platform

The Voluum S2S tracking loop is a single circuit: a token rides the click out to the offer, the affiliate network returns it in a postback when the visitor converts, and Voluum matches the two - turning a form fill or a sale into a reportable, deliverable conversion. Simple contour; keeping it closed is where the work lives. This guide walks the loop stage by stage: the cid parameter and its echo, token propagation through the offer, platform integrations on the delivery side, and the verification that proves every conversion completes the circuit.

General anatomy of such chains - and the failure modes they share - lives in the network postback to CAPI guide; this page stays on Voluum's implementation.

The Loop: Token Out, Postback Back

Two halves complete the loop:

1. Outbound. The offer URL carries a Voluum token resolving to the click's unique identifier. Whatever arrives in that parameter, the network stores - this is the value it will echo back.
2. Inbound. Voluum's postback URL - copied into the network - carries the identifier home in the cid parameter. In practice the network's own token feeds it: the documented pattern is cid=#s2#, where #s2# is the network-side macro holding the value Voluum passed (Voluum S2S postback documentation).

When the echo arrives intact, Voluum matches the conversion to the click - the identifier completing the circuit - and the report lights up. Arriving empty - the offer link lost the token, or the network's postback template never included the macro - the click and the conversion never reconnect, and that conversion is invisible everywhere downstream. This is the same subid-echo contract as Keitaro's S2S postbacks and Binom's postback contour, under Voluum's names.

Building the Postback URL

Setup sequence:

1. Copy the S2S postback URL from Voluum for the offer or campaign.
2. Replace the network-token placeholder in the URL with the network's actual macro - in the documented pattern, cid=#s2# where #s2# is whatever holds the click ID on that network.
3. Where the network supports it, extend the postback with the event name and payout fields so each conversion arrives typed and valued.
4. Save the URL in the network's postback settings.

Each network has its own macro vocabulary, and Voluum's tracker-comparison-era documentation is explicit that the mapping step is where setups fail: the token in, the token back - both ends must resolve to the same value.

From Voluum to the Ad Platforms

Once conversions live in Voluum, delivery to ad platforms runs through its platform integrations: Voluum documents a Facebook conversion integration and a TikTok full integration among others. These integrations follow the platform-side pattern described in the postback-to-CAPI guide: the matched conversion is forwarded as a server event with the identifiers the platform requires.

Receiving platforms' acceptance rules are not Voluum's to bend: Meta's Conversions API enforces its required fields and the seven-day event_time window (using the API), and its deduplication rules only pair browser and server events. Confirmation lag from the network consumes that window - the same timing math as the hold status guide.

Verifying the Loop

1. Click through the real ad and confirm the token reached the offer link.
2. Convert for real - network test postbacks do not carry real identifiers.
3. Check Voluum's reports: the conversion should appear on the click's row.
4. Confirm the platform-side leg: the integration's logs or the platform's test tooling show the delivered event (get started with the Conversions API documents Meta's Test Events and the roughly 20-minute Events Manager visibility).

If step three fails, the gap is in the echo - the postback troubleshooting checklist walks the joint-by-joint diagnosis.

Voluum S2S Tracking: Frequently Asked Questions

Sources