How Affiliate Tracking Works: Links, Click IDs and Postbacks

Tracking answers an attribution question

Affiliate tracking associates activity with a campaign and an affiliate so that a qualifying result can be evaluated for commission. It is separate from the question of whether the result is valid. A system may know which affiliate referred an event while still rejecting the event under campaign rules.

Tracking designs vary. This guide explains common concepts and the inspected ClicksBounty flow at a high level; it does not publish private destinations, partner credentials or a production integration specification.

The authorised link starts the path

An affiliate receives or generates an authorised link for an approved campaign. When a visitor follows a ClicksBounty redirect, the platform records the visit and sends the visitor to the configured campaign destination. The redirect token resolves the relevant account and campaign internally.

Changing the destination, copying another affiliate’s token or manipulating attribution can break tracking and violate policy. A link is not a substitute for approval. Campaign access, traffic rules and current availability still apply.

Three identifiers with different jobs

Identifiers are useful only when their meaning is clear. A click ID identifies a particular referral event. A transaction ID identifies a conversion reported by a campaign partner. A Sub ID, where supported, can help an affiliate distinguish placements or traffic sources.

Use a neutral label such as a placement code rather than a consumer’s email address or other sensitive information. Not every field displayed in a user interface is necessarily supported by the complete partner integration. Confirm the actual fields and supported macros before relying on them.

• Click ID: connects a reported result with a specific recorded visit.
• Transaction ID: distinguishes a conversion and helps prevent duplicate credit.
• Sub ID: an optional source label where the network and campaign support it.

What a postback does

A postback is a server-to-server notification that communicates conversion information. Depending on the integration, it can carry identifiers, a campaign reference, status and payout data. The receiving system must authenticate the notification and validate that the information can be attributed consistently.

A retry should not create a second commission for the same transaction. Later status information may need to update the existing record with appropriate history. Server-to-server delivery reduces dependence on a browser executing a conversion script, but it does not guarantee accurate attribution when identifiers are missing or incorrect.

Cookies and server records are different

Some affiliate systems use browser cookies, while others combine browser and server-side methods. The current ClicksBounty redirect handler creates a server-side click record and does not set an affiliate-attribution cookie. Campaign destinations can have their own technologies and privacy practices.

Calling a flow server-to-server does not mean it processes no personal information or has no privacy obligations. Request metadata and identifiers may still matter. Consult the Cookie and Privacy policies and the actual campaign implementation, not a general label.

Troubleshooting a missing conversion

Start with the event definition: did the person complete the qualifying action, including any confirmation step? Then verify approved access and the correct link, without creating payable artificial events. If testing is authorised, use the designated test process.

Next, compare the click and transaction references and check whether the report is Pending, Rejected or Reversed rather than absent. Provide the relevant campaign identifier and timing to support. Never send postback secrets, passwords or unnecessary consumer data in a screenshot.

• Confirm the campaign was active and the traffic was permitted.
• Check the exact link and required identifier mapping.
• Distinguish a missing event from a rejected or pending event.
• Check for an existing transaction before assuming a retry is new activity.
• Keep the evidence and ask for review through the approved contact route.

Reporting is part of the audit trail

Conversions and financial adjustments should remain understandable over time. In ClicksBounty, conversion status and ledger records distinguish the reported upstream amount from the affiliate commission. Changes to a campaign’s future commercial terms should not silently rewrite an earlier record.

Good identifiers make an investigation possible; they do not replace clear campaign requirements or honest traffic. Read the commission and policy documents alongside the technical flow.