Refuse leads

Users with access to a specific Offer can view its details together with allowed propagation options (Link, iFrame, API).

For iFrame or API submissions, the Admin can configure whether unwanted leads should be rejected. This can be applied to iFrame only, API only, or to both.

How leads can be rejected

If rejection is enabled in the Offer settings (under Form or API), a lead may be refused based on:

  1. Validation – The lead must pass:
    • Field type + regex validation (fixed rules)
    • External validation (custom logic or external service)
  2. Offer Filters – The lead must satisfy the Offer’s filter conditions to be eligible for processing.
  3. Lead Processing Result – The lead must be successfully accepted by at least one channel.
    • If no channel accepts the lead, it is marked as refused.

You can choose what the lead must pass before being approved:

  • Everything – the lead must pass validation, filters, and pingtree processing.
  • Validation – the lead must pass field and external validation.
  • Filters – the lead must pass the Offer filters.
  • Pingtree – the lead must be accepted by at least one channel in the pingtree.

You can include or exclude specific affiliates from this feature if needed. Alternatively, you can duplicate the offer just for them if you want to apply a different setup.

Lead Approval and Rejection

If lead refusal is disabled:

  • The status is always approved. All leads are marked as approved, even if they do not meet the defined criteria.

If lead refusal is enabled:

  • The status initially starts as pending until processing is completed.
  • If the lead meets the defined criteria → the status changes to approved.
  • If the lead does not meet the criteria → the status changes to rejected.

Sample API response:

{  "id": "9e886baa-6804-4dfe-baf9-a065b66d7f87",  "status": "pending",  "redirect_url": "https://api.paldock.com/api/tenant/processes/12345"}

Tracking Lead Status (Approved or Rejected)

Affiliates may want to track the status of each lead, whether it was successfully processed (approved) or refused (rejected). PalDock provides several ways to obtain this information. For full details, see the API Integration page.

Verification

When a verification step is required, the sale process is temporarily paused. In these cases:

  • The lead cannot remain in pending status, because the user must still be redirected.
  • The lead is therefore set to approved while the verification is in progress.
  • If the verification later fails, or if the lead is not accepted by any channel, the status will remain approved.

You might also want to check out the Process refused leads feature, which enables you to process even leads you rejected.

Insights that
helps you grow

  • Release notes 2025/12/19
    We added country-based categorization. You can now categorize offers, integrations, and other items by a specific country, or keep them global across all markets. We also…
  • Release notes 2025/12/17
    More flexible lead rejection: based on validation rules, filters, or pingtree sales results, by source (iframe, API) or by partner (include / exclude). It is now possible to…
  • Case study: How Lender Orka Ventures Scaled Affiliate Operations
    Orka Ventures, an online lending group that wanted to scale fast across countries and onboard affiliates quickly. Their custom affiliate API and tracking layer soon…