This feature is connected to the Refuse Leads setting. By default, when a lead is refused, PalDock marks it as STATE:fail without any further action. Such leads are not shown in standard reports (they appear only in the Leads log) and are not processed further.
In some cases, however, you may still want to process a lead even if it was rejected. You can include or exclude specific affiliates from this feature if needed.
What a Lead Must Pass Before Approval
You can configure what a lead must pass before being approved:
- Everything – validation, filters, and pingtree processing.
- Validation – only field and external validation.
- Filters – only the Offer filters.
- Pingtree – only acceptance by at least one channel in the pingtree.
Processing Refused Leads
If Process Leads is enabled, PalDock will still execute follow-up actions (such as redirects or distribution) even though the lead is rejected and not counted as valid/paid.
Examples:
- Embedded Form Lead – A lead passes form validation but is rejected by filters (e.g., duplicate). It won’t increase the accepted lead count in reports, but with Process refused Leads enabled, you can still redirect the user (for example to finish a previously unfinished application).
- API Lead – A lead submitted via API fails validation and the partner cannot correct the data. It remains rejected in the system (no payout, no reporting increase), but you can still process it (for example by lead distribution)
Enable Process refused Leads if you want rejected leads to still trigger follow-up actions (such as redirects or alternative flows), without counting them as valid/paid leads.
