Skip to content
Newv6.18.0Generated values for buyer deliveries, a safer Google Sheet connection, and a post log filter step that explains itself.Read the changelog
Fraud & validation

Catch the bad lead before your buyer does.

Screen every lead on IP, email, phone, DNC, and credit as it arrives — then accept, reject, or enrich it on rules you write. Bad traffic never reaches the buyers you are trying to keep.

Start Free Trial
Book a Demo
Checks at ingest
Your rules, not a black box
DNC hard gate
Integration settings showing blacklist, IP, email, phone and credit validation providers with active rules
What gets checked

Every lead, before it costs you anything

Screening happens at ingest — before distribution, before a buyer sees the record, and before a bad lead becomes a refund conversation.

IP, VPN, proxy, and bots

Score the connection before you trust the form. Fraud score, VPN, proxy, Tor, data-centre traffic, and known bot signatures — the traffic that costs you buyer relationships, caught at the door.

Email that will actually deliver

Disposable addresses, spam traps, honeypots, dead servers, invalid MX. A lead whose email bounces is a lead your buyer will ask for a refund on.

Phone, carrier, and line type

Is the number live, is it reachable, is it a mobile or a landline, and has it been ported. A buyer paying for calls cares about the difference.

DNC, litigator, and blacklist

Federal and state DNC, wireless, suppression lists, and known TCPA litigators. This one is a hard gate — a lead that fails it is rejected at ingest, not routed and argued about later.

Soft credit qualification

Run a soft credit inquiry and qualify the lead against real offers before you sell it. A soft inquiry, not a hard pull — and a far better idea of what the lead is actually worth.

Rules you write, not a black box

Reject when the fraud score hits 85 or above. Reject when VPN and proxy are both true. Accept when it is 30 or below. Conditions combine with AND or OR, the first matching rule wins, and nothing is decided by a vendor’s opaque verdict.

The rule engine

You set the threshold. Not the vendor.

A provider returns numbers; you decide what they mean. Build conditions on any field a provider returns, combine them with AND or OR, and choose whether a match accepts the lead or rejects it. The first matching rule wins, and if nothing matches the lead passes.

  • Reject when fraud score ≥ 85, or when VPN and proxy are both true
  • Accept when the score is under 30 — and let everything else through
  • Per-campaign overrides on top of one global provider account
Fraud checkLOW RISK
6
IPQS fraud_score
vpn: falseproxy: false
IPQSAnuraDNC
verdict → ACCEPTED
Beyond accept and reject

A check that only says no is wasting the answer

The interesting part is not the verdict. It is that the provider told you the credit score, the carrier, and the line type — and that all of it lands on the lead in time to be useful.

A check writes its findings onto the lead — credit score, fraud score, carrier, line type
Those values land before your filters run, so filters and buyer rules can gate on them
Buyers can be sent the enriched values, or filtered by them, without any extra plumbing
The same values are available to postbacks and templates, so partners see what you saw
FAQ

Frequently asked questions

Each provider has its own timeout, and you set it. The credit check runs longer than the rest, because a credit pull genuinely takes longer. If a provider is slow or down, that shows in its usage log — every call is recorded with its latency and error rate, so a degrading provider is visible before it becomes your problem.

You will see the rule that did it, the value that failed, and the threshold it failed against — and the usual cause is a rule set too aggressively rather than a bad lead. The most common example is a fraud score threshold set near zero, which rejects almost everything. Rejections are visible and reversible; you are not guessing.

Both, and that is the useful part. A check can be a gate, or it can simply enrich the lead with what it found and leave the decision to your filters, your buyers, or your pricing. The DNC and blacklist scrub is the one that can only be a gate — a lead that fails it is rejected, never merely flagged. Everything else is yours to decide.

No. Each provider declares the countries it supports, and a lead from outside that list simply skips it rather than burning a call and returning nonsense. A US-only credit check will not run on a Dutch lead.

Yes. Credentials are set once globally, and any campaign can override the settings and rules on top of them. One aggressive campaign and one permissive one can share the same provider account without fighting each other.

Fourteen, spanning IP, email, phone, blacklist and DNC, credit, CRM, and conversion tracking. The full list — and what each one returns — is on the integrations page.
Further reading

More on stopping bad leads before they cost you

Stop paying for leads your buyers will reject.

Start your 14-day trial. Full platform access. Card required, no charge if you cancel during the trial.

Start Free Trial
Book a Demo