Held or rejected traffic: what it means for you
Rejected and held mean different things for your money. A rejected user’s conversions pay $0 and send no postback. A held offer means our team is looking at your traffic on it. A conversion in review pays nobody until a person approves it. None of them changes what you’ve already been paid, except a take-back, which arrives as a normal reversal.
See also: Fraud Defense
On this page
| What you see | Covers | Money | Postback | Where it shows |
|---|---|---|---|---|
| Rejected user | One of your users, on every offer, for 30 days | Their conversions pay $0 | None | Traffic Quality, and rejected on Conversions |
| Held offer | Your traffic on one offer, while our team reviews it | The users behind the flagged taps are rejected. Everyone else is paid as normal. | As normal for everyone else | The rejected users show on Traffic Quality |
| Paused offer | Your traffic on one offer, after our team decides | New taps on it stop. Conversions from taps already sent still settle. | As normal for those | The offer stops taking your taps |
| Conversion in review | One conversion | Nobody is paid until it’s approved | Sent once approved | Nowhere in your reports until approved |
A user goes on your reject list when their traffic fails our checks. Reporting, then Traffic Quality lists each one: their ID, the offer (or Every offer), the reason in plain words, when it started and when it expires. On the Hosted Offerwall the ID is the uid you opened the wall with.
While the rejection lasts:
- Their conversions are recorded with the status
rejected. They pay $0, send no postback and don’t count in your totals. - Their new taps show “This offer isn’t available for your account”.
- On the Hosted Offerwall, they can’t start another offer.
We keep comparing your traffic on each offer with other traffic and with your own history. When it looks wrong, your traffic on that offer is held. The users behind the flagged taps are rejected straight away; your other users keep converting and are paid as normal.
Then a person on our team decides:
- Release: the hold ends, and the users it rejected are paid again.
- Reject: that offer is paused for your account. Conversions from taps already sent still settle.
For some publishers and offers, a conversion waits for a person to approve it before it settles. While it waits, it pays nobody, sends no postback and doesn’t appear on Conversions, in the API or in your totals. Approved, it settles at the price it had when it came in, with its normal postback. Rejected, it is never paid and never appears in your reports.
Some rejections also reach back into conversions you were already paid for, from the days before the rejection: 7 days for “Multiple accounts detected on the same device”, 30 days for “Emulated devices”, “Duplicate accounts detected” and “IP mismatch / VPN or proxy detected”. Each one arrives as a standard reversal: a postback with status=reversed, the original action_id and that reason in reason. Deduct what you credited.
- Check Traffic Quality each week, and look at the accounts behind the IDs: several of them on one device or one address is usually one person.
- Dedupe postbacks on
action_idandstatustogether, so a take-back or a late payment lands once. - If you think we rejected a real user, send us their ID and the offer. Our team can lift a rejection.
Networks: the same rules apply to each of your publishers’ traffic.