Skip to main content

Advertiser Postback

Send conversion postbacks from an advertiser or website to Trackdesk.

An advertiser postback lets an advertiser or website record a conversion in Trackdesk by sending the Click ID and the conversion type. It can be sent as a GET or a POST request, both described below.

šŸ’” Tip: The AI assistant can walk you through an advertiser postback setup and explain which parameters your advertiser should send. Open the Search or ask AI… bar and switch to AI Chat.


​

Sending a GET postback

Fixed amount offers

To send a GET postback for an offer with a fixed commission amount, use the following URL structure to create your conversion:

https://TENANT_ID.trackdesk.com/tracking/conversion/v1?conversionTypeCode=CONVERSION_TYPE&cid=CLICK_ID

Replace these values:

  • TENANT_ID: your Tenant ID

  • CONVERSION_TYPE: the type of conversion you want to record, such as sale

  • CLICK_ID: the specific Trackdesk Click ID (CID)

Revenue share offers

If your offer uses a dynamic revenue share, you must provide the revenue amount in the postback so Trackdesk can correctly calculate the network and affiliate commissions.

https://TENANT_ID.trackdesk.com/tracking/conversion/v1?conversionTypeCode=CONVERSION_TYPE&cid=CLICK_ID&amount.value=AMOUNT

Replace these values:

  • TENANT_ID: your Tenant ID

  • CONVERSION_TYPE: the type of conversion you want to record, such as sale

  • CLICK_ID: the specific Trackdesk Click ID (CID)

  • AMOUNT: the revenue amount you want to send to Trackdesk, for example 100 for whole numbers or 100.50 for decimals (no quotes in the URL)

Optional: adding extra GET parameters

You can attach up to 9 extra parameters to your conversion to provide additional information.

šŸ’” Tip: You can use the builder tool found in our API documentation to help easily generate your customized postback link.

  1. Adv S1 to Adv S5: Use these 5 available parameters for any general information. Format it as:

    customParams.advS1=VALUE
  2. Customer ID: A general parameter for passing customer details. Format it as:

    customerId=CUSTOMER_ID
  3. External ID: This parameter is used for deduplication. Only one conversion per Conversion Type can have the same External ID (for Network accounts, per Conversion Type and Revenue Origin), so a duplicate request does not create a second conversion. This is typically an Order ID or another internal transaction identifier. Format it as:

    externalId=EXTERNAL_ID
  4. Currency: Specifies the conversion currency, applicable only for revenue share cases. Format it as:

    currency.code=CURRENCY_CODE

    Replace CURRENCY_CODE with an ISO 4217 format currency code (e.g., USD, EUR or GBP).

  5. Status: Dictates the initial status of the conversion. Format it as:

    status=VALUE

    Check the API documentation for supported options like CONVERSION_STATUS_APPROVED or CONVERSION_STATUS_PENDING.

Sending a POST postback

Fixed amount offers

To send a POST request for a fixed amount offer, direct your payload to the tracking endpoint:

POST https://TENANT_ID.trackdesk.com/tracking/conversion/v1

{
"conversionTypeCode": "CONVERSION_TYPE",
"cid": "CLICK_ID"
}

Replace these values:

  • TENANT_ID: your Tenant ID

  • CONVERSION_TYPE: the type of conversion you want to record, such as sale

  • CLICK_ID: the specific Trackdesk Click ID (CID)

Revenue share offers

For dynamic revenue shares, include the revenue value inside your payload so the system can calculate commissions properly.

POST https://TENANT_ID.trackdesk.com/tracking/conversion/v1

{
"conversionTypeCode": "CONVERSION_TYPE",
"cid": "CLICK_ID",
"amount": {
"value": "AMOUNT"
}
}

Replace these values:

  • TENANT_ID: your Tenant ID

  • CONVERSION_TYPE: the type of conversion you want to record, such as sale

  • CLICK_ID: the specific Trackdesk Click ID (CID)

  • AMOUNT: the revenue amount you want to send to Trackdesk, formatted as a string, for example "100" for whole numbers or "100.50" for decimals

Optional: adding extra POST parameters

You can include the same 9 optional extra parameters in your POST payload.

šŸ’” Tip: A payload builder tool is also available in the API documentation.

Here is how to format each extra parameter inside your JSON payload:

  1. Adv S1 to Adv S5: General parameters for any information. There are a total of 5 of these parameters. Use the following format to add them to the postback (example for Adv S1 shown):

    "customParams": {
    "advS1": "VALUE"
    }

    To use multiple Adv S parameters, use the following format:

    "customParams": {
    "advS1": "VALUE",
    "advS5": "VALUE"
    }
  2. Customer ID: General parameter for any information.

    "customerId": "CUSTOMER_ID"
  3. External ID: Parameter used for deduplication. Only one conversion per Conversion Type can have the same External ID (for Network accounts, per Conversion Type and Revenue Origin), so a duplicate request does not create a second conversion. It is typically an Order ID or other internal transaction identifier.

    "externalId": "EXTERNAL_ID"
  4. Currency: Specifies the currency for the conversion, applicable only for revenue share cases.

    "currency": {
    "code": "CURRENCY_CODE"
    }

    Replace CURRENCY_CODE with an ISO 4217 format currency code (e.g., USD, EUR or GBP).

  5. Status: Parameter used to specify the conversion status that the conversion will be created with. Use the following format to add this parameter to the postback:

    "status": "VALUE"

    Check the API documentation for supported options like CONVERSION_STATUS_APPROVED or CONVERSION_STATUS_PENDING.

Did this answer your question?