Skip to main content

Affiliate – Postbacks

How to set up affiliate postbacks: Offer, Global and Default postbacks, macros and rejected-event notifications

J
Written by Jorge Rubia

An affiliate postback is the notification Aftrad sends to your affiliate's platform each time a conversion is attributed to them. It carries data such as the affiliate's own click ID and the payout, so they can record the conversion on their side in real time.

Postbacks are optional. If no postback is configured, or none of the configured rules match the event, the affiliate is not notified.


How to access it

Go to Performance → Affiliates, open the affiliate and, in the General tab, click Postbacks.

📌 Changes are only applied when you click Save at the bottom right. Cancel discards them.


Postback types and priority

The left panel lists three types of postbacks. When a conversion occurs, Aftrad checks them from top to bottom and fires the first one that matches:

  1. Offer postbacks — rules for specific offers. Use them when the affiliate needs a different URL or setup for a particular offer.

  2. Global postbacks — rules that apply to all offers of this affiliate. Each rule fires only for the event types, attribution models (Click ID, Aggregated ID or both) and classifications (Payable, KPI or both) you select.

  3. Default Postback — the fallback, used when no Offer or Global postback matches. It applies to every event, so its targeting conditions can't be changed.

💡 Tip: for most affiliates, the Default Postback is enough. Add Offer or Global postbacks only when the affiliate needs specific handling per offer or event.

Note: Your affiliates can see their Default Postback URL, and the Rejection URL when rejected-event notifications are on, in their Affiliate Marketplace (My settings → GENERAL). They can copy them but not change them. See Affiliate Marketplace.


Postback rules

Each rule is shown as a summary row:

Column

What it shows

POSTBACK NAME

Label of the rule.

EVENTS

Event types that fire it (e.g. All events).

CLASSIFICATION

Payable, KPI or both.

ATTRIBUTION MODEL

Click ID, Aggregated ID or both.

REPORTED AS REJECTED

Whether the affiliate is notified about events reported as rejected (Do not notify by default).

Click the arrow on the right to expand the rule and edit it. Drag the handle on the left to change the order of the rules, or use the bin icon to delete one.

Postback URL

  • Postback URL (mandatory) — the URL given by the affiliate, where Aftrad sends the notification. Add Aftrad macros to its parameters; Aftrad replaces them with the conversion's values. Example:

https://affiliatepostback.com?click={affiliate_click_id}&payout={payout}

The most common macros are:

  • {affiliate_click_id} — the click ID the affiliate sent with the click.

  • {payout} — the payout the affiliate earns for this conversion.

You can edit the URL as Rich text, Table view (one row per parameter) or Plain text. The icons next to the label copy the URL or open it in a new tab.

Targeting conditions

  • Event setup — which event types fire the postback: All events, or only conversions from payout rules with the selected event types. Each payout rule has an event type, and several rules in the same offer can share one.

  • Attribution model — how the conversion was attributed:

    • Click ID — the advertiser sent the click_id in their postback. This is the standard and most precise method.

    • Aggregated ID — the advertiser sent the aggregated_id instead (a probabilistic exception, used in some mobile flows).

    • Select both to fire the postback in either case.

  • Classification:

    • Payable — events that generate a payout for the affiliate.

    • KPI — tracked events with no payout.

In the Default Postback, these conditions are greyed out: it covers every event that no other rule matched.


Notifying affiliates about rejected events

Some advertisers and attribution platforms (for example, AppsFlyer) report conversions as rejected on their side after they were sent. To tell the affiliate when this happens, turn on Notify affiliate about events reported as rejected.

⚠️ "Reported as rejected" is not the same as Rejected: Rejected events are refused by Aftrad when they arrive (for example, invalid click_id or secure token) and never reach the affiliate.

When the toggle is on, a Rejection URL field appears. Use the same URL as the postback or a different one. Three extra macros are available (shown here in Table view, one row per parameter):

  • {blocked_reason} — main reason for the rejection.

  • {blocked_sub_reason} — more detailed sub-reason.

  • {blocked_reason_value} — value associated with the reason.

To check the exact postback Aftrad sent to the affiliate for a conversion, add the Affiliate postback URL column in Tools → Affiliate attributions. See Affiliate attributions.


Offer postbacks — offer groups

In Offer postbacks, rules are grouped by offer. Each group can hold several rules, checked top to bottom within the group.

  • + Add offer group — creates a group for another offer.

  • + Add new postback rule — adds a rule inside a group (also used in Global postbacks).

For example, a group for the offer Yoga can send its own URL (with &offer=yoga) only for conversions attributed by Click ID, while a Global postback fires only for First time deposit (FTD) events, and the Default Postback covers everything else.


Related articles

Did this answer your question?