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).

ℹ️ See full list of supported publisher postback macros here

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
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. Decisions

Send postbacks only for conversions with a specific evaluation decision - Passed or Failed. Leave empty to send postbacks regardless of decision.

💡 Decision and Status are related but different. Status (item 6 above) is the conversion's state (Approved, Rejected, Pending.) in Swaarm, while Decision shows if the postback has been sent to the Publisher or not. See Optimization tool overview to know which rules affect both.

8. Failed Status Rules

Send a postback only when the conversion failed at least one of the selected status rules. Leave empty to match any failed status rule.

ℹ️ Postbacks for conversions that didn't fail any status rule are not affected by this setting; it only filters among conversions that did fail one.

9. Failed Evaluation Rules

Send a postback only when the conversion failed at least one of the selected evaluation rules. Leave empty to match any failed evaluation rule.

ℹ️ Postbacks for conversions that didn't fail any evaluation rule are not affected by this setting; it only filters among conversions that did fail one.

💡 Decisions, Status, Failed Status Rules, and Failed Evaluation Rules can be combined. For example, to notify a publisher only when a conversion failed specifically due to VPN detection, set Decisions to Failed and select the VPN rule under Failed Evaluation Rules (or Failed Status Rules, depending on which rule type flagged it).

10. 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.

11. 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