Postbacks and Click IDs Explained: How a Conversion Reaches Your Tracker

Editorial team of Affiliate Index · Published October 30, 2026

The role of a click ID

A click ID is a unique value a tracker assigns to a visitor’s click. It helps connect an action, such as a signup or purchase, to the campaign that brought the visitor there. Without that link, a tracker may know a conversion happened but not which click should receive credit.

The ID is usually added to the destination link or passed along as a tracking parameter. The tracker records it with details about the click, such as the campaign and traffic source. The advertiser or affiliate network must then preserve the ID as the visitor moves through its landing pages and conversion process.

A click ID is not the same as personal information. It is a tracking reference used to join records between systems. Its exact format and handling depend on the tracker and partner program, so check their documentation and terms before setting up a campaign.

How a server-to-server postback works

When a visitor clicks an ad, the tracker creates and stores a click ID. The visitor is then sent to the advertiser or network, usually with that ID included in a parameter they can retain.

If the visitor later completes a qualifying action, the advertiser or network sends a server-to-server notification, known as a postback, to the tracker. The notification includes the click ID and may include other details, such as a conversion event or status. The tracker uses the ID to find the original click and associate the conversion with the relevant campaign.

Because this notification travels between servers, it does not rely on the visitor’s browser returning to the tracker. That can make the method useful when browser-based tracking is limited. However, a postback still depends on correct setup and on the partner system sending the expected information.

Why conversions can go missing

A lost or altered click ID is a common cause. If the ID is not passed to the partner, is removed during a redirect, or is not saved with the conversion, the postback may arrive without the value the tracker needs to match it. Review the full click path, including intermediate pages and redirects, rather than checking only the first link.

A wrong macro can produce a similar problem. Partners often use a placeholder, or macro, that is replaced with the actual click ID when a conversion occurs. If the wrong placeholder is used, or the partner expects a different parameter name, the postback may send a blank value or an unrelated one. Confirm the required macro and parameter names with both systems.

The request itself may also fail to reach the tracker. Network rules, security settings, incorrect configuration, or an unavailable endpoint can prevent delivery. In other cases, the request arrives but the tracker rejects it because a required field is missing or its format is unexpected.

Finally, the systems may disagree about conversion status. A partner might report an event as pending, approved, rejected, or reversed, while the tracker is configured to accept only particular statuses. Check how each status is handled and whether later changes are expected to update an earlier conversion.

Testing before sending traffic

Set up a controlled test before launching a campaign. Use the tracker’s test tools, if available, or generate a test click through the intended flow. Confirm that the click ID appears in the tracker and is passed to the partner in the expected parameter. Avoid relying on a manually typed link that skips redirects or other steps in the real path.

Next, trigger a test conversion through the partner’s approved testing process. Check whether a postback is sent, whether it contains the same click ID, and whether the tracker records the event against the intended campaign. Review the conversion status and any available request logs on both sides. A request can be delivered successfully yet still fail to match, so verify the recorded result rather than delivery alone.

If the test does not match, check each handoff in order: click capture, parameter passing, partner-side storage, macro substitution, postback delivery, and status mapping. Change one setting at a time where practical, then repeat the test. Keep a record of the final configuration so later edits can be reviewed.

Keeping tracking reliable

Confirm tracking requirements with the partner before launch, including which events qualify, how click IDs should be passed, and whether test conversions are supported. Keep campaign links and postback settings consistent, and recheck them after redirects, landing pages, or partner settings change.

Treat tracking records as operational data, not proof that every conversion is payable. Reconcile tracker reports with the partner’s reporting and payment terms, and investigate discrepancies promptly. A well-tested postback helps explain where conversions came from, but accurate attribution still depends on each system preserving and interpreting the same information.