Safari limits cookies set by JavaScript to 24 hours after an ad click, or 7 days otherwise. If a conversion happens later, the browser cannot connect it to the traffic source. This window is shrinking across the industry, pushing media buyers and networks toward server-side tracking.
Server-side tracking works without the browser. Instead of a pixel firing in a visitor's browser and reporting the event client-side, one server sends data directly to another. The affiliate network or operator notifies your tracker when a conversion occurs. The data reaches you, not filtered through browser restrictions.
Why browsers lose data
The browser has become unreliable for tracking conversions. Safari's Intelligent Tracking Prevention caps cookies at 7 days or 24 hours after an ad click. Link Tracking Protection strips known identifiers such as gclid and fbclid in Private Browsing, Mail and Messages links, and regular tabs when users opt in. Ad blockers often block third-party tracking scripts. For affiliates, the critical issue is structural: conversions happen on the network's or operator's page, where your pixel was never allowed in the first place.
Each limit alone is manageable. Combined, they explain why pixel-only setups routinely under-report conversions.
Three paths to the tracker
Conversions reach your tracker or an ad platform through three channels. The browser pixel fires on the conversion page and sends the event from the visitor's browser. It installs quickly but applies to every browser limit described above, and only works on pages where you control the code.
Server-to-server postbacks come from the affiliate network or operator to your tracker. The tracker passes its click ID to the offer. When the visitor converts, the network's server calls your postback URL with that click ID, crediting the conversion to the right click.
Conversions APIs send data from your tracker or server to ad platforms so their bidding algorithms learn from the events. Meta's Conversions API, TikTok's Events API and Google's offline and enhanced conversions all work this way.
S2S and CAPI are complementary. One gets the conversion to your tracker, the other from your tracker to the platform. Browser pixels remain useful where you own the page, provided you deduplicate them with server events.
The browser still matters
Server-side tracking does not replace the browser entirely. Your tracker must see the visit itself, either through a redirect or a tracking script on your lander. On-page behavior such as scroll depth or a button click before conversion exists only client-side. Retargeting audiences on ad platforms are still built largely from pixel events on pages you control.
The goal is not to remove the browser from tracking. It is to stop relying on it for the one thing that pays: the conversion. Record the visit in the browser, record the conversion on the server, use pixels as a supplement where you control the page.
Implementation path
Server-side tracking in Voluum follows six steps. Send traffic through a Voluum campaign URL; the tracker records the visit and creates its own click ID, the anchor for server-side tracking that follows. Pass the click ID to the offer by adding Voluum's {clickid} token to the offer URL in the parameter the network expects, such as sub1 or aff_sub.
Set up the postback by giving the network your postback URL with its click ID token in cid, plus payout and, for repeat conversions, a transaction ID. Map the platform's click ID to the external ID so conversions can be matched back on Meta, TikTok and other networks. Send conversions back through a traffic source postback or Automizer's integrations, which feed Meta's Conversions API and TikTok's Events API. For Google, pass conversions tied to the GCLID.
Test one conversion end to end. Check the visit, the conversion in Voluum and the event on the platform. If any step breaks, common tracking issues show where to look.
Expect some differences between Voluum and each platform even when everything works correctly. Platforms add view-through and modeled conversions within their own attribution windows, while a server-side setup counts only what was actually confirmed.