The Affiliate Postback configuration defines the URL where Aftrad will send a notification each time a conversion is confirmed for that Affiliate. This allows the Affiliate's platform to receive real-time conversion data — including their click ID and the payout amount — and attribute it correctly on their end.
Postback configuration is optional. If no postback is configured, or if none of the configured postbacks match the event, no notification is sent to the Affiliate.
How to access it
Go to Performance >> Affiliates, open the Affiliate's profile, and navigate to General > Postbacks.
Postback types and priority
There are three types of postbacks, listed in the left panel. When a conversion occurs, Aftrad evaluates them from top to bottom and applies the first one that matches:
Offer postbacks — postbacks configured for a specific Offer. Use these when an Affiliate requires a different postback URL or setup for a particular Offer.
Global postbacks — postbacks that fire for all Offers assigned to this Affiliate. Use these when you need a postback that applies across all Offers but with specific targeting conditions.
Default Postback — the fallback postback applied when no Offer postback or Global postback matches. This is the most common starting point.
💡 Tip: For most Affiliates, configuring just the Default Postback is sufficient. Add Offer postbacks or Global postbacks only when the Affiliate requires specific handling per Offer or event type.
Postback configuration
Each postback rule has the following fields:
Postback name — an internal label to identify this postback rule.
Postback URL (mandatory) — the URL provided by the Affiliate where Aftrad sends the conversion notification. Include the Affiliate's required macros directly in the URL. Example:
https://affiliatepostback.com?click={affiliate_click_id}&payout={payout}
The most commonly used macros are:
{affiliate_click_id}— replaced at runtime with the click ID originally sent by the Affiliate.{payout}— replaced at runtime with the payout amount the Affiliate will receive for this conversion.
Targeting conditions
Event setup — defines which events trigger this postback. Set to All events to fire on every conversion, or select specific event types.
Attribution model — defines how the conversion was attributed:
Click ID — used when the Advertiser sends the
click_idin their postback. The most precise method.Aggregated ID — used when the Advertiser sends the
aggregate_idinstead.If the Advertiser sends both, Aftrad first tries to match via
click_id. If it doesn't match, it falls back toaggregate_id.
Classification — defines which event classifications trigger this postback:
Payable — fires only for events that generate a payout for the Affiliate.
KPI — fires for informational events that do not generate a payout.
Notifying Affiliates about rejected events
Some platforms, such as AppsFlyer, can report conversions as rejected. If you want to notify the Affiliate when this happens, enable the Notify affiliate about events reported as rejected toggle.
Once enabled, a Rejection URL field appears. You can use the same Postback URL or a different one specifically for rejected events. Three additional macros are available for rejection notifications:
{blocked_reason}— the main reason the event was rejected by the Advertiser.{blocked_sub_reason}— a more detailed sub-reason for the rejection.{blocked_reason_value}— the specific value associated with the rejection reason.
Offer postbacks — additional options
When configuring Offer postbacks, you can group multiple postback rules under a single Offer. Within each group you can add multiple rules — Aftrad evaluates them top to bottom within the group.
Use + Add new postback rule to add a rule within an existing Offer group.
Use + Add offer group to create a new group for a different Offer.