Back to Integrations

IPQualityScore

The IPQualityScore integration adds real-time phone validation and fraud scoring to LeadExec, blocking invalid or high-risk numbers before they reach your buyers.

Source Type:
Data Validation

Delivery Format:
API

Integration Type:
Phone Fraud Scoring

Website:
IPQualityScore Website

Overview

The IPQualityScore (IPQS) Phone Validation integration enriches LeadExec with real-time fraud-scoring and line-quality checks for every inbound lead. By querying IPQS’ Phone Validation & FraudScore API, LeadExec can automatically reject, flag, or route leads based on risk signals such as fraud_score, VOIP/prepaid, and recent_abuse:contentReference[oaicite:1]{index=1}:contentReference[oaicite:2]{index=2}.

How It Works
  1. Trigger point. After basic field validation but before routing, LeadExec invokes IPQS for campaigns where Enable IPQS Phone Score is toggled on:contentReference[oaicite:3]{index=3}.
  2. Request. LeadExec issues a GET call to
    https://ipqualityscore.com/api/json/phone/{API_KEY}/{PHONE_NUMBER}
    with query params like strictness (0-2) and country:contentReference[oaicite:4]{index=4}.
  3. Parse response. Key fields—fraud_score, valid, VOIP, recent_abuse, etc.—are stored with the lead and exposed to the Criteria Builder:contentReference[oaicite:5]{index=5}:contentReference[oaicite:6]{index=6}.
  4. Decision logic. Default rules reject leads when fraud_score ≥ 85 or valid = false; optional rules flag VOIP or prepaid numbers for QA:contentReference[oaicite:7]{index=7}.
  5. Integration chain. If the lead is rejected and the “Skip remaining integrations” option is enabled, downstream integrations are bypassed:contentReference[oaicite:8]{index=8}.
Benefits
  • Higher Connect Rates. Blocks invalid, VOIP, or recycled numbers before they reach buyers:contentReference[oaicite:9]{index=9}.
  • Fraud & Compliance Layer. Complements hygiene (Trestle) and DNC checks with real-time risk scoring:contentReference[oaicite:10]{index=10}.
  • Cost-Effective Accuracy. IPQS advertises >10× lower cost than competing phone scorers while maintaining high accuracy.
  • Seamless Workflow. Re-uses the same mapping UI and Criteria Builder used by PureCallerID, so admins need no new training:contentReference[oaicite:12]{index=12}.
Auth & Settings
Setting Description
API Key Private key passed in URL or X-IPQS-KEY header:contentReference[oaicite:13]{index=13}
Strictness 0 (default), 1, 2 – controls aggressiveness of fraud scoring:contentReference[oaicite:14]{index=14}
Fraud Threshold Default 85; per-campaign slider controls auto-reject level:contentReference[oaicite:15]{index=15}
Data Exchange
Outbound (LeadExec → IPQS)
Field (LeadExec) Param / Path Required Notes
Phone Number URL path Yes Mapped via field selector
Country Code country query param No Improves accuracy in multi-region campaigns
Strictness strictness query param No Defaults to 0 if omitted
API Key Path segment or request header Yes Header hides key in logs
Inbound (IPQS → LeadExec)
Response Field Purpose / Typical Rule
fraud_score (0-100) Reject or flag (≥ 85 risky, ≥ 90 very high):contentReference[oaicite:16]{index=16}
valid (bool) Reject if false:contentReference[oaicite:17]{index=17}
VOIP, prepaid Optional flag or deprioritize leads:contentReference[oaicite:18]{index=18}
recent_abuse Strong reject signal for “hot” bad numbers:contentReference[oaicite:19]{index=19}
carrier, line_type Stored for reporting only:contentReference[oaicite:20]{index=20}
Example Criteria Rules

IF fraud_score >= 90 THEN Reject
ELSE IF valid = false THEN Reject
ELSE IF VOIP = true THEN Flag (QA)

Amazing support is at the heart of everything we do.

ClickPoint provides 24 hour chat support, extensive product documentation, and weekly training sessions.