Setting up postback for Affiliate Top

How to set up postback

Click “Add” to start the postback setup process and fill out required fields based on your preferences.

 

1. Postback name – enter a clear and unique name to each of your postbacks to avoid confusion. (e.g., "FTD_YT_BR")
2. Event – select from dropdown (Registration, First deposit, etc.)
3. Postback URL – paste URL from your tracker (check examples above)
4. Parameters – click on blue presets below “Postback URL” field ("Click ID", "Deposit amount") to automatically add parameters
5. Method – GET (by default)
6. Currency – select $ or ¢ for amounts

7. Segmentation filters

This setting lets you decide when the postback should be sent — depending on which campaign or subaccount it relates to. You can fill in one or both of these fields.

Why use segmentation filters?

They help you manage traffic more precisely:

• Optimize different traffic sources independently – if you use more than one performance monitoring tool, you can send basic events to one and events with extra parameters to another.
• Run A/B tests – segmentation helps you see which sources bring more conversions and how different campaigns, creatives, or landing pages perform.
• Test or migrate tools safely – you can start sending postbacks to a new performance monitoring tool in parallel with the old one and compare the numbers before fully switching.

How the system decides when to send the postback:

1. Neither campaign nor subaccount specified
   The postback is sent for the selected trigger event regardless of campaign or subaccount.
2. Only campaign specified
   The postback is sent for the trigger event only if the trader’s tracking link includes this specific campaign.
3. Only subaccount specified
   The postback is sent only if the trader’s tracking link includes this specific subaccount, no matter what campaign it belongs to.
4. Both campaign and subaccount specified
   The postback is sent only when both values in the trader’s link match the campaign and subaccount you entered.

(Activation note: after the postback is activated, it’s sent within 15 seconds whenever the selected event and conditions are met.)

8. Activate if needed and click "Add"

Postback Statuses

Postbacks go through several statuses during their lifecycle. Here's what each means and what triggers status changes:

• Checking (~15 seconds) – we examine your postback for any issues when it first created, edited, or copied
  • If postback is correct → it becomes Active.
  • If it has errors → postback switches to Inactive status with an error message shown in the interface.
  • Postback can’t be edited or paused – only deleted
• Active – postback is working correctly and collecting data.
  • If edited → temporarily returns to Checking status.
  • If receives 10 consecutive 3xx/4xx HTTP errors → automatically disables, shows error in interface, and sends email notification.
• Inactive – postback is disabled due to validation failure, manual deactivation, or error threshold reached. Must be fixed and revalidated to become Active again.
  
   

Key behaviors:

• After 10 failed validation attempts, activation requires manager assistance
• Active postbacks self-monitor and protect against persistent delivery failures

Postback Logs

Here you can find  all postbacks made in the last 30 days. It helps you identify setup issues and understand what needs to be fixed, for example.

List of possible errors:

When postbacs fail, check the Logs section for the status code.

Error 3xx – Redirection errors

The server says: "Go to this other address instead."

Result:  Your postback gets sent somewhere else.

Top causes:

- Postback URL automatically redirects (HTTP→HTTPS, www/non-www, tracking links)

- Server or tracker forwards requests to another address

- Your server secretly changes the URL along the way

How to fix it?  

1. Copy your postback URL 

2. Paste it into a browser address bar and hit Enter  

3. Wait for it to load (or stop redirecting)  

4. Copy what you see in the address bar now — this is  your postback URL

Error 4xx – Client errors

The server says: "Something's wrong with your request." 

Result: Usually it’s a setup issue.

Top causes:

- 404: Postback URL doesn't exist (typo in path, domain, or parameters)

- 400/422: Missing or invalid parameters (clickid, status, amount)

- 403/401: Server blocks the request (firewall, IP whitelist, auth required)

How to fix it?  

1. Copy your full postback URL (with all parameters like clickid)
2. Check it character by character against your server setup
3. Try opening it in a browser — does it show "page not found"?
4. Fix the wrong part (domain, path, or missing info) and update it