Voluum Glossary

What is Postback URL

A postback URL is a web address that one server calls to report a conversion to another server. Most often, an affiliate network calls a tracker's postback URL to report a sale, lead or deposit, passing the tracker's click ID so the conversion can be attributed to the original click without browser cookies or pixels.

Postback URL: A postback URL is a web address that one server calls to report a conversion to another server. Most often, an affiliate network calls a tracker’s postback URL to report a sale, lead or deposit, passing the tracker’s click ID so the conversion can be attributed to the original click without browser cookies or pixels.

Definition

A postback is a server-to-server (S2S) HTTP request that carries conversion data from one platform to another. The postback URL is the address that receives it. Because the request is sent between servers, it does not depend on the visitor’s browser, so ad blockers, cookie restrictions and in-app browsers do not affect it. Postbacks are the standard method of conversion tracking in affiliate marketing and in verticals such as iGaming.

The same mechanism is also called S2S tracking, server-to-server tracking, server postback or callback URL.

Two Click IDs, Two Postbacks

A typical affiliate setup involves two separate click IDs, and each is used by a different postback.

The traffic source click ID is created by the ad network when a visitor clicks an ad. The traffic source adds it to the campaign URL, and Voluum stores it as the external ID.

The Voluum click ID is created by Voluum itself, when the offer URL is activated in a campaign with a lander, or when the campaign URL is activated in a campaign without one. Voluum passes this ID to the affiliate network in the offer URL.

These two IDs connect two postbacks. The affiliate network postback reports the conversion from the network to Voluum, using the Voluum click ID. The traffic source postback is optional and reports the conversion from Voluum to the traffic source, using the external ID in the {externalid} token. It lets the traffic source match the conversion to its own click and use it for optimization.

Sequence diagram: the traffic source click ID is saved as the external ID, Voluum creates its own click ID and passes it to the offer, the affiliate network sends a postback with that click ID, and Voluum can send an optional traffic source postback with the external ID

How S2S Postback Tracking Works

  1. Ad click. A visitor clicks an ad. The traffic source sends the visitor to the Voluum campaign URL with its own click ID, which Voluum saves as the external ID.
  2. Voluum click ID. Voluum records the visit and creates its click ID when the visitor is sent to the offer, through the offer URL if the campaign uses a lander, or through the campaign URL if it doesn’t.
  3. Offer. Voluum redirects the visitor to the offer and adds its click ID to the offer URL, in the parameter the affiliate network uses, such as sub1 or aff_sub.
  4. Conversion. The visitor converts. The affiliate network links the conversion to the click ID it received.
  5. Affiliate network postback. The network calls Voluum’s postback URL with the click ID and, usually, the payout. Voluum attributes the conversion to the original visit, including its traffic source, campaign, lander, offer and GEO.
  6. Traffic source postback (optional). Voluum calls the traffic source’s postback URL with the external ID, so the conversion is also recorded inside the traffic source.

Postback URL Parameters

A Voluum postback URL, with an affiliate network’s tokens filled in, looks like this:

https://your-tracking-domain.com/postback?cid={sub1}&payout={payout}&txid={transaction_id}&et={event}

Each parameter is paired with a token that the network replaces with a real value at conversion time. Token names differ by network and should be copied from the network’s documentation. Voluum supports these postback parameters:

ParameterWhat it carriesRequiredExample network token
cidVoluum’s click ID from the original visitYes{sub1}, #AFF_SUB_ID#, [subid]
payoutThe revenue for the conversionNo{payout}, #PAYOUT#
txidA transaction ID that makes repeat conversions from the same click uniqueNo{transaction_id}, #TID#
etThe conversion type, such as registration or depositNo, requires custom conversions{event}, #TYPE#

Voluum rejects a second postback with the same click ID unless it is made unique, and the same combination of cid and txid is counted only once. Upsells and repeat deposits therefore require a transaction ID, and separate conversion types such as registrations and deposits require custom conversions with the et parameter. The setup for iGaming is described in the guide to tracking first-time deposits.

Postback vs. Pixel

A conversion pixel fires in the visitor’s browser on the conversion page. It requires access to that page and can be blocked by browser settings. A postback is sent from the network’s server and requires neither. Where a network supports both, the postback is generally the more reliable option. A comparison of the two methods is available in the article on the tracking pixel and postback URL.

The same server-side principle is used by ad platform APIs, such as Meta’s and Google’s Conversion APIs and TikTok’s Events API, described in the TikTok ads tracking guide.

Postbacks and Dynamic Parameters

Postbacks and dynamic parameters are sometimes presented as alternatives. They are not. A dynamic parameter is a name and value pair in a URL that changes from visit to visit, such as device=iphone or country=de. A postback URL is built from dynamic parameters: every element after the question mark in the example above is one.

Dynamic parameters are also used outside postbacks. On the way to the offer, they carry ad network data such as campaign, placement or creative into the tracker for reporting, and they can personalize landing pages. In a typical setup, dynamic parameters carry information out with the click, and the postback returns the conversion.

Common Postback Errors

  • Click ID not passed to the offer. The offer URL does not include the click ID token, or a redirect removes it.
  • Incorrect token. The network’s token for the click ID is misspelled, so the postback sends the placeholder text instead of a value.
  • Postback configured at the wrong level. Some networks require a postback per offer, others a global one.
  • Duplicates rejected. Repeat conversions from the same click without a transaction ID are discarded by design.
  • External ID not mapped. The traffic source’s click ID is not mapped to the external ID, so the traffic source postback has no value to send.
  • Numbers that differ from the network. Often caused by different counting rules or time zones rather than a broken postback. See attribution window and attribution models.

A broader checklist is available in the article on the most common tracking issues. Reliable postbacks are also the basis for the affiliate marketing KPIs calculated from conversion data.

Postback Tracking With Voluum

Voluum creates a click ID for every visit, generates the postback URL and attributes each conversion to its visit, traffic source and campaign, with support for payouts, transaction IDs, custom conversion types and traffic source postbacks. Compare Voluum plans.

Frequently Asked Questions

What is a postback URL?

A postback URL is an address that receives a server-to-server conversion report. In affiliate marketing, the affiliate network calls the tracker’s postback URL with the tracker’s click ID and details such as payout, so the conversion is attributed to the original click without cookies or pixels.

What is an S2S postback?

An S2S postback is a server-to-server conversion report. Instead of a pixel firing in the visitor’s browser, one server sends an HTTP request directly to another. Because the browser is not involved, the report is not affected by ad blockers, cookie restrictions or in-app browsers.

What is the difference between the click ID and the external ID in Voluum?

The click ID is created by Voluum for each visit and is passed to the affiliate network, which returns it in the postback. The external ID is the traffic source’s own click ID, passed to Voluum in the campaign URL. Voluum sends it back to the traffic source in the traffic source postback URL.

What is a traffic source postback URL?

A traffic source postback URL is an address provided by the ad network that Voluum calls when it records a conversion. It includes the traffic source’s click ID, stored in Voluum as the external ID, so the conversion is also attributed inside the traffic source and can be used for its optimization.

Why is my postback not working?

Common causes are a click ID that was not passed to the offer, a misspelled token in the postback URL, a postback configured at the wrong level, duplicate conversions rejected because no transaction ID was passed, or an external ID that was never mapped for the traffic source postback.

×
Oops!