Postbacks Overview
Postbacks allow affiliates to receive real-time server-to-server notifications when specific conversion events occur, such as signups or purchases.
By integrating postbacks with your tracking system, you can automatically receive conversion data and match it to the original click. This ensures accurate attribution and consistent reporting in both your system and ours.
When a user clicks your affiliate link, we record the parameters you pass (such as click_id). You can view the full list of supported parameter macros in the table here: [Link].
When a conversion occurs, we send a server-to-server request to your configured postback URL, allowing your system to match the conversion to the original click.
Types of Postbacks
We currently support two types of postbacks:
Dynamic Postbacks (Recommended)
- Supports dynamic parameters in the postback URL
- Compatible with major tracking platforms (e.g., Voluum)
- Allows separate URL endpoints per conversion type (signups and purchases)
- Provides greater flexibility and detailed reporting
Static Postbacks (Legacy)
- Does not support dynamic parameters in the postback URL
- Returns a limited set of predefined data points
Both options are fully supported. There are no plans to deprecate Static Postbacks.
How to Set Up Dynamic Postbacks
- Navigate to:
https://chaturbate.com/affiliates/devkit/dynamic_postback/ - Select “Add New URL” under the Dynamic Postbacks tab.
- Enter your postback URL and append supported macros to receive specific data. For example:
https://example.com/postback?click_id={click_id}&payout={payout}&country={country} - Select the Transaction Type (Signup or Purchase) if you want to differentiate events.
- (Optional) If your tracking platform supports checksum validation, enter a Validation Salt to verify postback authenticity.
- Choose your delivery method: GET (most common) or POST.
How Dynamic Postbacks Work
- A user clicks your affiliate link.
-
We record your
click_idand any additional URL parameters you pass. - When the user completes a signup, we send a server-to-server postback to your specified URL, including the macros you defined.
- If the user makes a future purchase, we send a purchase postback using the same parameters saved at signup, ensuring accurate attribution.
Macros List and Definitions
These macros can be used within Dynamic Postbacks in the Affiliate Program.
Some macros are system-generated at the time of conversion (such as {payout} or {currency}), while others are affiliate-supplied passthrough parameters that originate from your affiliate link (such as {click_id} or {track_id}).
Dynamic Postback Parameters
| Category | Macro | Description | How its populated |
| Conversion | {click_id} |
Unique ID for each ad click used to track the specific user interaction that led to a conversion. Character limit: 1024 |
Affiliate-supplied passthrough |
| Conversion | {source} |
Traffic source specified in affiliate link Character limit: 255 |
Affiliate-supplied passthrough |
| Track | {track} |
Used for bucketing traffic by a handful of traffic sources from your side, e.g. "websiteA", "websiteB" Character Limit: 255 |
Affiliate-supplied passthrough |
| Transaction Identification | {transaction_id} | Unique ID of the conversion event (signup, purchase) | System generated |
| Campaign Identification | {campaign_id} | Unique ID of the campaign | System generated |
| Offer Identification | {program_id} | Unique ID of the program/offer | System generated |
| Offer Identification | {program_name} | Name of the program/offer (e.g., $1.00 Pay Per Registration + $50.00 Per Broadcaster + 5% Referred Affiliate Income, etc.) | System generated |
| User Identification | {user_id} | Unique ID of the referred user | System generated |
| Conversion | {type} |
The type of conversion that took place. Possible values: tokens_signup-referral, tokens_broadcaster-referral, ppr_signup-referral, ppr_broadcaster-referral, revshare_signup-referral, revshare_broadcaster-referral, revshare_purchase, revshare_webmaster-commission, and revshare_payout-adjustment |
System generated |
| Conversion | {payout} | Amount of money credited to the affiliate for this conversion (Negative for chargebacks) | System generated |
| Conversion | {currency} | The currency in which the payout is made | System generated |
| Conversion | {amount} | The amount spent by the user | System generated |
| Conversion | {token} | Number of tokens credited to the affiliate for this conversion | System generated |
| User Action | {timestamp} | The timestamp of when the conversion was performed | System generated |
| User Action | {date} | The date the conversion was performed | System generated |
| User Action | {time} | The time the conversion was performed | System generated |
| Geolocation | {country} | The country of the user | System generated |
| Device and Browser | {device} | The device used by the user (mobile, desktop) | System generated |
| Device and Browser | {language} | The language setting of the user's browser | System generated |
| Referral | {referral} | The URL of the referrer | System generated |
| Retries | {attempt} | The number of attempts a request was sent before receiving a proper response (Up to 6 attempts) | System generated |
| Geolocation | {region} | The region or state of the user | System generated |