Rejection reasons: affiliates know why a conversion was rejected
Every rejected conversion shows the affiliate why (repeated IP, country, too fast, cap…), with a note from the team or the advertiser. Fewer disputes, cleaner traffic.
Updated on 2 Nov 2026
A bare "rejected" starts arguments and doesn't help the affiliate improve. In RastroAff, every rejected conversion has a reason, and can have a written explanation.
Where the affiliate sees the reason
- On the Conversions page: each rejected conversion shows the reason and the explanation, if there is one.
- At the top of the same page, a "Why they were rejected (30 days)" summary counts rejections by reason, so the affiliate knows what to fix first.
- On the Dashboard, in recent activity.
Next to each rejection there is a Dispute link that opens a claim with the click ID already filled in.
Where the reasons come from
| Source | Reason |
|---|---|
| The offer's cap was reached | Cap, filled in automatically |
| The team rejects in Conversions | The team picks the reason and can write an explanation for the affiliate |
| The team confirms a fraud alert and rejects the conversions | The alert type: repeated IP, repeated device, too fast, country different from the click, datacenter or VPN IP… |
| The advertiser rejects in the postback | Rejected by the advertiser, with the text they send in reason |
Reasons the team can choose
- Duplicate conversion
- Repeated IP
- Country not allowed on the offer
- Too fast (a few seconds after the click)
- Low-quality traffic
- Traffic source not allowed
- Rejected by the advertiser
- Test conversion
- Other reason (manual rejection)
For advertisers: sending the reason in the postback
When rejecting, add the reason parameter:
https://track.rastroaff.com/postback?token=TOKEN&click_id=CLICK_ID&txn_id=ORDER&status=rejected&reason=KYC%20failed
The text (up to 300 characters) is shown to the affiliate in quotes. See Advertiser postback.