Skip to main content

Affiliate Postbacks

Track conversions server-to-server, ensuring accurate and reliable updates sent directly to your affiliate tracker.

Written by Sasha Gerold
Updated over a week ago

Affiliate postbacks allow Trackdesk to notify an affiliate's tracking platform automatically and instantly when a conversion occurs. Unlike traditional browser-based tracking, this is a server-to-server (S2S) request. This method ensures that conversion data is accurate and reliable by communicating directly between servers, bypassing common browser limitations such as cookie blocking, privacy settings, or ad-blockers.

1. The Logic: How Affiliate Postback Tracking Works

Postback tracking relies on a unique Click ID, which is a specific identifier generated for every individual click. This ID serves as the "anchor" that connects a user's initial interaction to a final conversion.

The Prerequisite: Passing the Click ID in the Link

For the automated system to function, the affiliate must construct their tracking link to pass their unique Click ID over to Trackdesk. Trackdesk uses specific parameter fields, such as affS1 through affS5, to receive this data. Example link structure::
​

https://exampleAffiliateTrackingLink.com?affS1={placeholderForClickId}


In the example above, when a user clicks the link, the affiliate platform replaces {placeholderForClickId} with the real Click ID, allowing Trackdesk to capture it on the landing page.

The Automated Operational Flow

Once the link is configured correctly, the following server-to-server journey occurs automatically:

  1. Click ID Generation: When a user clicks the affiliate tracking link, the affiliate's tracking platform generates the unique Click ID.
    ​

  2. Data Transmission: The affiliate tracking system redirects the visitor to the offer's landing page. During this redirect, the Click ID is appended to the URL. Example:
    ​

    https://example.com/?affS1=CLICK_ID


    Trackdesk captures this CLICK_ID and stores it, associating it with that specific visitor's session.
    ​

  3. Conversion Recording: When the visitor completes a conversion event (such as a purchase, deposit, or registration) Trackdesk records the event and retrieves the Click ID stored during the initial visit.
    ​

  4. Postback Execution: After the conversion is created in the system, Trackdesk sends an automated request (the Postback) to the affiliate tracking platform’s server to notify about the conversion. Example Postback URL:
    ​

    https://affiliate.tracker.com/postback?clickid={affS1}&amount={payout}

    Before sending, Trackdesk replaces the placeholders with the actual transaction values.

2. Configuring an Affiliate Postback in Trackdesk

To establish the connection between Trackdesk and an external tracking platform through the Postback, follow these steps:

  1. Navigate to the Affiliate Postbacks section in Trackdesk.
    ​

  2. Click Add New Postback.
    ​

  3. Configure the Postback fields according to the Postback Configuration table below:

Postback Configuration

When creating an affiliate postback, configure the following fields.

Field

Description

Affiliate ID

Select the affiliate for whom the postback is being created. The postback will only fire for conversions attributed to this specific affiliate.

Scope

Defines for which offers the postback should be triggered.
​
​ Global scope – Fires for all offers (except those explicitly excluded).. This also applies to offers created later.
​
​ Offer scope – Fires only for specifically selected offers.

Conversion type

Select the specific events (e.g., Sale, Lead, Registration, Deposit) that should trigger the postback. More than one can be selected.

Conversion statuses

Select the conversion statuses that should trigger the postback. If multiple statuses are selected, the postback will fire when the conversion changes to any of the selected statuses.

Custom currency

Allows the payout value to be sent in a selected currency. If not specified, the default conversion currency is used.

HTTP method

Defines how the postback request is sent:

GET: Parameters are included in the URL (most common).

POST: Parameters are sent in the request body. Some affiliate tracking platforms require this method

URL

The endpoint provided by the affiliate's tracker, containing placeholders for Trackdesk to fill.

3. URL Parameters and Placeholders

The postback URL template uses placeholders that are replaced with actual conversion data the moment the postback is triggered.

Example URL template:

https://affiliate.tracker.com/postback?clickid={affS1}&amount={payout}

Example request sent by Trackdesk:

https://affiliate.tracker.com/postback?clickid=12345&amount=50

Common Placeholders

Variable

Description

{affS1} - {affS5}

Affiliate tracking parameters

{conversionId}

Conversion identifier

{conversionType}

Conversion event type

{conversionStatus}

Conversion status

{conversionCreatedAt}

Timestamp of the conversion

{payout}

Affiliate payout value

{conversionCurrency}

Currency of the conversion

{cid}

Click identifier

{externalCid}

External click identifier

{revenue}

Conversion revenue

{saleAmount}

Sale amount value

Enabling Revenue and Sale Amount Parameters

If an affiliate requires revenue or sale amount data in the postback URL, you must enable this feature manually:

  1. Navigate to Settings → Affiliates → Data visibility.
    ​

  2. Set the Revenue or Sales amount visibility to Global (for all affiliates) or to Individual (for specific affiliates).

4. Testing and Monitoring

Testing the Integration

It is highly recommended to test the setup before launching a campaign:

  1. Click a real affiliate tracking link that includes a test Click ID in the affS1 parameter.
    ​

  2. Verify that the Click ID is visibly present in the landing page URL.
    ​

  3. Complete a test conversion (e.g., a test purchase).
    ​

  4. Confirm that the affiliate tracking platform correctly receives the postback and attributes the test sale.
    ​

Monitoring and Troubleshooting

  • Affiliate Postback Tracking Log: Trackdesk provides a detailed log of every postback request sent. This is the primary tool for troubleshooting integration issues, checking HTTP response codes, and verifying successful data transmission. You can read more about it here.

AI Postback Assistant

Trackdesk features an AI Postback Assistant designed to simplify the setup of affiliate postbacks. The assistant provides step-by-step guidance through the configuration process, helping you identify the specific parameters required by various affiliate tracking platforms

To get started, navigate to the Affiliate Postbacks page and click AI Postback Assistant.

5. Common Questions

What if the Click ID token format is different?

Different platforms use various token formats. Examples: 

{aff_sub}
#s2#
{sid}
!!!sid!!!

Always refer to the affiliate platform's documentation to ensure the placeholder you place in the Trackdesk Postback URL matches exactly what their receiving server expects.

Can multiple conversion types trigger postbacks?

Yes. You can select multiple conversion types and statuses within a single configuration. Trackdesk will fire the postback whenever any of the selected conditions are met.

Practical Tips

  • Always verify parameter names with the affiliate’s tracking platform documentation.

  • Ensure the affiliate tracking link correctly passes the click ID parameter.

  • Run a test conversion before launching the integration.

Related Articles
Redirect tracking
Advertiser Postback
Connect 3rd-Party Affiliate Networks and Platforms
AppsFlyer integration
Affiliate Postback Tracking Log
Did this answer your question?