Overview
IPQualityScore (IPQS) is a fraud prevention service that analyzes phone numbers to detect risk indicators such as fraud activity, VoIP usage, prepaid lines, and abuse history.
By integrating IPQS with LeadExec, you can automatically evaluate phone numbers during lead submission and take action based on the results. This helps improve lead quality and prevents fraudulent or low-quality leads from entering your workflows.
Key Functionality
The IPQS integration in LeadExec provides several tools to help validate phone numbers and automate lead quality control.
1. Phone Fraud Detection
Analyze phone numbers using Fraud Score to determine the likelihood of fraudulent activity.
Identify numbers linked to recent abuse, spam activity, or known fraud patterns.
2. Phone Line Intelligence
Detect whether a number is VoIP, prepaid, or a standard carrier line.
Retrieve carrier details such as Carrier Name, Line Type, Country, Region, and City.
3. Automated Lead Filtering
Create criteria rules based on returned data such as Fraud Score, VoIP status, or Do Not Call flags.
Automatically reject leads, route them to quality control.
Before You Begin
Before configuring the integration in LeadExec, ensure the following requirements are completed:
Obtain the API Key
Make sure you have an active API key from the third-party service (IPQS). This key is required for LeadExec to authenticate and send validation requests.Create Required Lead Fields
Any response fields you plan to store (such as Fraud Score, VoIP status, or other returned values) should be created in the Lead Type configuration before setting up the integration. Creating these fields ensures that the returned validation data can be stored and viewed within LeadExec.
How to Set Up IPQS in LeadExec
Step 1: Enable the IPQS Integration
Before configuring the integration, you will need your IPQS API Key from your IPQS account.
To enable the integration:
Navigate to Integrations in the left toolbar within LeadExec.
Locate the IPQS integration.
Click Details.
Toggle the integration On.
Enter your API Key in the required field.
Click Save.
Once saved, the integration will be available for configuration.
Step 2: Configure Settings by Lead Type
After enabling the integration, click Details to open the system-wide settings.
These settings are configured per Lead Type.
To add a configuration:
Navigate to Lead Type Configuration.
Click New.
Select the desired Lead Type / Industry.
Once the Lead Type has been added, you will be prompted to the Request and Response fields window.
Step 3: Configure Request Fields
Request fields determine the data that LeadExec sends to IPQS for validation.
Phone Number (Required)
The phone number that will be validated by IPQS.
Strictness Level
Determines how aggressively the phone number is analyzed.
0 = Loose
1 = Normal
2 = Strict
Country Code(s)
The suspected country for the phone number (for example: US or US,CA).
This field is required if the phone number contains fewer than 10 digits.
Enhanced Line Check
Enables HLR Lookup Service to verify whether the phone line is active.
Values: true / false
Enhanced Name Check
Adds an enhanced name lookup to the phone number validation request.
Values: true / false
Step 4: Configure Response Fields
Response fields store the data returned by IPQS after a phone number is evaluated.
To use these values in LeadExec, you must first create corresponding fields in your Lead Type configuration so the data can be stored and displayed within the platform.
Response fields include:
Valid
Fraud Score
Recent Abuse
VoIP
Prepaid
Risky
Active
Line Type
Country
Region
City
Carrier
Do Not Call
Leaked
Spammer
Active Status
User Activity
These fields allow LeadExec to capture detailed information about each phone number and use that data for filtering, routing, or quality analysis.
Step 5: Create Criteria Rules
Once request and response fields are configured, you can define criteria rules that determine what actions LeadExec should take based on IPQS results.
To create a rule:
Navigate to the Criteria section in the IPQS settings.
Click Add.
Select the response field you want to evaluate.
Define the condition.
For example:
Fraud Score - Less Than - 50
This rule ensures that only phone numbers with a low fraud risk are accepted.
You can then configure the action LeadExec should take when the condition is met, such as:
Sending the lead to Quality Control
Rejecting the lead
This allows LeadExec to automatically filter or route leads based on fraud risk indicators.
Step 6: Enable the Integration at the Campaign Level
After configuring the global integration settings, the integration must also be enabled at the campaign level.
To do this:
Navigate to either the Lead Source List or Campaign List.
Locate the desired campaign.
Open the Integrations tab.
Add the IPQS integration to the campaign.
Once enabled, the integration will run automatically whenever leads are submitted through that campaign.
Note: Campaign-level integration settings are optional and are intended to override the global integration settings when configured. This allows each campaign to apply different validation rules, fraud thresholds, or data requirements depending on its specific needs, providing greater control over how leads are evaluated and routed through that particular campaign.
Step 7: Checking integration results.
Once the integration is set up, and lead start flowing into the system, you can filter results within the main Leads list view by adding the relevant columns and filters to your screen.
You can also review the integration results by opening the lead and navigating to the Integrations tab. From this window, you’ll be able to see the result and status of the integration for that specific lead.
Conclusion
By configuring the IPQS integration in LeadExec, you can automatically evaluate phone numbers and detect potential fraud before leads enter your workflows. This helps maintain higher lead quality, reduce risk, and improve overall lead management efficiency.
Troubleshooting
If the integration is not returning results as expected, you can test the connection directly from the campaign where the integration is enabled.
To test the integration:
Navigate to the Campaign where the IPQS integration has been enabled.
Open the Integration Manager tab.
Locate the IPQS integration and click Edit.
Select Test.
A prompt will open displaying a JSON request. You can enter the values you want to test (such as a phone number) and submit the request. LeadExec will then send the data to IPQS, allowing you to review the response details and verify that the integration is working as expected.
When reviewing the results, check the following:
Verify that the API Key has been correctly entered in the integration settings.
Verify that the response fields exist in the Lead Type, so the returned data can be stored.
Check that the campaign has the IPQS integration enabled in the Integrations tab.
Review the criteria rules to confirm they are not automatically rejecting or rerouting the lead based on the returned values.
If no response is returned, confirm that the IPQS service is active and the API key has not expired or reached usage limits.
Using the test feature allows you to quickly confirm that the request structure, API connection, and response mapping are functioning correctly before processing live leads.
Best Practices
When configuring the IPQS integration in LeadExec, consider the following best practices to ensure accurate validation and optimal lead quality.
Start with a balanced fraud score threshold
A rule such as Fraud Score < 50 is a good starting point. This helps filter high-risk numbers while still allowing legitimate leads to pass.Ensure response fields exist in your Lead Type
Fields such as Fraud Score, VoIP, Carrier, and Line Type should exist in your Lead Type configuration so the data returned by IPQS can be stored and used for filtering or reporting.Test the integration before enabling it on live campaigns
Use the Test feature within the Integration Manager to verify that request values, response fields, and criteria rules are working correctly before processing real leads.