Skip to main content

Postback Reversal

How to use postback reversal in Swaarm - reject or revise a previously approved conversion by adding special parameters to your postback

A reversal postback tells Swaarm that a previously approved conversion should be undone or revalued. Common use cases include chargebacks, refunds, fraud take-downs, and price adjustments that happen after the fact.

When a reversal postback is received, Swaarm looks up the original conversion and either:

  • Rejects it - status changes to REJECTED, decision to FAILED

  • Revises it - WeGet is updated to a new value and TheyGet scales proportionally, conversion stays APPROVED

The original conversion row is not deleted. Instead, a postback modification is produced - the same mechanism used for all other corrections in Swaarm. The Conversion Report and revenue reports reflect the reversal automatically.

ℹ️ Reversal postbacks are counted as postbacks and contribute to your platform usage.


How to trigger a reversal

Option 1 - Full reversal

Add &reversal=true (or &reversal=1) or &status=reversal to the postback URL. All three are equivalent - once such postback is received, the original conversion will be set to status REJECTED and decision FAILED.

https://track.{yourdomain}.swaarm-clients.com/postback?click_id=<original-click-id>&event_id=<event-id>&reversal=true

Option 2 - Partial reversal (revise the amount)

Add &reversal=true together with &revised_amount=<value> to update WeGet to a new value instead of fully rejecting the conversion. TheyGet scales proportionally and the conversion stays in status APPROVED.

https://track.{yourdomain}.swaarm-clients.com/postback?click_id=<original-click-id>&event_id=<event-id>&reversal=true&revised_amount=4.25

How TheyGet is scaled: If the original was WeGet=$10.00 / TheyGet=$8.00 and revised_amount=5.00 is sent, the result is WeGet=$5.00 / TheyGet=$4.00 (the same 80% ratio applied to the new WeGet).

⚠️ revised_amount must always be combined with reversal=true. Sending revised_amount without the reversal flag is not supported.

ℹ️ Negative values in revised_amount are treated as their positive equivalent - revised_amount=-2 is the same as revised_amount=2.

ℹ️ revised_amount=0 is valid - WeGet and TheyGet both become $0, conversion stays APPROVED.


How matching works

Swaarm looks up the most recent non-rejected evaluated postback for the given click_id and event_id (our_event_type_id)

  • If the same click fired the same event type more than once, the latest one is matched

  • Postbacks already in REJECTED state are ignored when searching for the original


What you see in reports

Postback Log

Every reversal attempt - whether matched or not - creates an entry in the Postback Log. Use the Errors field to filter and see all reversal attempts for an offer, publisher, or time window:

Situation

Log entry

Matched - conversion rejected

Reversal rejected original postback <id> (weGet=<value>)

Matched - WeGet revised

Reversal revised postback <id> weGet X → Y, theyGet A → B

No click_id or event type

Reversal missing click_id or event_id

No matching original found

Reversal with no matching original postback for click_id=… event_id=…

Original already rejected

Original postback already REJECTED; reversal skipped

Conversion Report

Matched reversals surface as postback modifications in the Conversion Report. To find them, add the Postback Modification Description column and filter by REVERSAL.

  • Full rejection → conversion flips to status REJECTED anddecision FAILED

  • Revised amount → conversion stays APPROVED with the updated WeGet/TheyGet values.


Edge cases - Q&A

  • What if the advertiser sends the reversal twice for the same conversion?

    The second reversal is ignored - the conversion is already rejected. A log entry is still written so you can see the attempt.

  • What if the reversal arrives before the original postback?

    It will be dropped - there's nothing to match yet. The advertiser should resend the reversal once the original postback has been processed.

  • What if revised_amount is sent without reversal=true?

    Not supported. Always combine revised_amount with reversal=true.

  • What if revised_amount is a negative number?

    Treated as its positive equivalent — revised_amount=-2 behaves the same as revised_amount=2.

  • What if revised_amount can't be parsed (e.g. a typo)?

    Treated as if revised_amount wasn't sent - a full rejection is applied instead.

  • What if both reversal=true and status=reversal are sent at the same time?

    No problem - they're equivalent and the reversal is processed once as normal.


Related articles

Did this answer your question?