Where to Configure Publisher Postbacks
Go to Publisher page → Postback Links section.
Click +Create Postback Link.
Fill in the required fields as described below.
Click Create to save the postback.
Part 1: Postback Settings Explained
1. Postback URL
The Postback URL is the endpoint where Swaarm sends conversion notifications. Example:
You can add supported macros by clicking Edit Macros.
The most commonly used macros are:
#{click.publisher.clickId}— publisher click ID#{offer.eventTypeId}/#{eventType.name}— event ID / event name#{payout.theyGetInDollars}— publisher payout (TheyGet value)
⚠️ The # symbol is a part of the macro syntax and must not be removed.
The postback URL should include the publisher’s click ID, unless it's configured for PEA (Privacy-Enabled Attribution).
2. Offer
Optional
Allows you to limit the postback to a specific offer
3. Event
Defines which event triggers the postback
Default means the postback will fire for the default event conversion (usually install)
You can select a specific event if your setup includes multiple events
4. Attribution Restriction
Defines which postback is sent based on attribution type:
Click ID + PEA Chain
Click ID
PEA Chain
On default Click ID + PEA Chain is selected
5. Level
Defines which type of conversions trigger the postback:
Default - postbacks are sent only for install / default events.
Event - postbacks are sent only for custom events.
Both - postbacks are sent for both installs and custom events.
6. Status
Defines the conversion status required for the postback to fire:
Approved - for conversions with status Approved
Rejected - for conversions with status Rejected
Rejected by Advertiser - for conversions marked as Rejected by Advertiser
Pending - for conversions with status Pending
You can select multiple statuses if you want to send postbacks for conversions in different states. To pass the postback status to the Publisher in the postback, use the following macro: #{status.state}.
7. Send Only Paid Postbacks
When enabled postbacks are sent only for conversions with a payout greater than zero. Event visibility must be 'Public' for the Publisher to receive the postback.
8. Headers
Optional HTTP headers can be added to the postback request.
Part 2: Common Postback Scenarios
Scenario 1: One Global Postback for Installs and Events
Use case: The publisher has shared 1 global postback -
https://track.pub135.com/postback?click_id=clickid&event_id=eventid&payout=payout&pea_chain=pea.chain
Recommended setup:
Add correct macros
Offer: leave empty
Event: leave Default
Attribution Restriction: leave Click ID + PEA Chain
Level: Default+Event
Status: Approved
Scenario 2: Separate Global Postbacks for Installs and Events
Use case: The publisher handles installs and events differently and shared 2 postbacks. For install Publisher would like to receive event id 'install'.
Install Postback - https://track.pub135.com/postback?click_id=clickid&event_id=install&payout=payout&pea_chain=pea.chain
Event Postback - https://track.pub135.com/postback?click_id=clickid&event_id=eventid&payout=payout&pea_chain=pea.chain
Recommended setup for Install Postback
Add correct macros
Offer: leave empty
Event: leave Default
Attribution Restriction: leave Click ID + PEA Chain
Level: Default
Status: Approved
Recommended setup for Event Postback
Add correct macros
Offer: leave empty
Event: leave Default
Attribution Restriction: leave Click ID + PEA Chain
Level: Event
Status: Approved
Scenario 3: Privacy-Enabled Attribution
Use case: The publisher requires a separate postback setup for privacy-restricted traffic.
Postback for deterministic attribution - https://track.pub135.com/postback?click_id=clickid&event_id=eventid&payout=payout
Postback for privacy-enabled attribution - https://track.pub135.com/peapostback?offer_id=offerid&pub_id=publisherid&event_id=eventid&payout=payout
Recommended setup for Postback 1
Add correct macros
Offer: leave empty
Event: leave Default
Attribution Restriction: Click ID
Level: Default+Event
Status: Approved
Recommended setup for Postback 2 (PEA)
Add correct macros
Offer: leave empty
Event: leave Default
Attribution Restriction: PEA Chain
Level: Default+Event
Status: Approved
Scenario 4: Offer- or Event-Specific Postbacks
Use case: multi-event offers where only certain events should trigger postbacks. For example, Publisher 135 would like to receive specific postback for event 'purchase' for offer 29317 - https://track.pub135.com/postback?click_id=clickid&event_token=purchase
Recommended setup:
Add the correct macros
Select the Offer
Select the required Event
Set Level to Event
Part 3: Publisher-Managed Postbacks (Partner Platform)
In addition, Publishers can configure their own postbacks directly in the Partner Platform, if this option is enabled for them. For details on how publishers configure postbacks in the Partner Platform, refer to this article: 👉 Partner Platform Settings
Important Notes
Always check selected macros.
Double-check the Level setting when using global postbacks.
Avoid creating overlapping postbacks - that may cause duplicates.
Test postbacks before launching live traffic whenever possible - 👉 Test Publisher Postback