Feature Snapshot
Summary:
IPQualityScore integrations enable real‑time validation of email addresses, verification of phone numbers, and detection of proxy/VPN activity through robust API endpoints—helping you filter out high‑risk or fraudulent leads and improve overall lead quality.
Key Benefits:
- Validate the authenticity, deliverability, and risk level of email addresses
- Verify phone numbers for proper format, carrier reliability, and potential fraud
- Detect proxy, VPN, and suspicious IP activity to mitigate fraud risks
- Enhance lead quality by appending risk scores and detailed validation outputs in real time
Typical Use Cases:
- Screening and filtering leads before they enter your CRM or marketing automation system
- Reducing chargebacks and fraud by verifying contact information quality
- Enriching lead data with real‑time risk scores for improved segmentation and decision‑making
How the IPQualityScore integrations work?
Step‑by‑Step Instructions
-
Add the Integration:
In your LeadConduit flow editor, navigate to “Add to Flow > Integration” and select the IPQualityScore integration. -
Choose an Action Option:
Based on your needs, choose one of the following actions:- Email Validation: To assess email deliverability, check for disposable or fraudulent addresses, and flag risky emails.
- Phone Validation: To verify the phone number’s format, determine carrier details, and evaluate risk.
- Proxy & VPN Detection: To analyze IP addresses for proxy, VPN, and suspicious activity.
-
Configure Credentials:
Enter your unique IPQualityScore API Key to authenticate the integration. -
Map Required Lead Fields:
- For Email Validation: Map the lead’s email address (required).
- For Phone Validation: Map the lead’s phone number (required).
- For Proxy & VPN Detection: Map the lead’s IP address (required).
-
Review Optional Mapped DatA:****
Optionally, map additional fields (such as extra identifiers or contact details) to provide enhanced context to the risk analysis. -
Finalize and Save the Configuration:
Save your integration settings to ensure the step is activated in your flow. -
Test the Integration:
Submit a test lead that meets the configured requirements and review the returned JSON response for fields such as “risk_score” and validation status.
Expected Result:
You will see the lead data enriched with specific risk parameters and validation outcomes from IPQualityScore—for example, the email and phone validation steps will return scores, indicators like “is_disposable” or “invalid,” and the Proxy & VPN detection will return fraud ratings.
Validation & Monitoring (optional)
-
Test the Setup:
Submit test leads for each action (Email, Phone, or Proxy/VPN) and verify that the returned JSON includes expected properties such asrisk_score,is_disposable, orproxyindicators. -
Where to Monitor?:
Check the LeadConduit Events tab to review detailed integration responses and monitor for successful validations or any error conditions that require attention.
Best Practices
- Ensure your IPQualityScore API Key is entered accurately to avoid authentication errors.
- Always include all the required fields (email, phone, or IP address) for the selected action to ensure proper validation.
- Map any additional optional fields that might enhance contextual risk assessment and improve filtering accuracy.
- Familiarize yourself with IPQualityScore’s response parameters and error codes by reviewing their official API documentation.
- Use downstream filter steps to act on risk scores—for instance, to block leads with a risk score above a defined threshold or to reject disposable emails.
- Regularly test the integration with varied test leads to validate both successful and error outcomes.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| HTTP response is 200 but the JSON response includes an error field | A required lead field (such as email, phone, or IP address) is missing or misconfigured | Verify that the required lead field is correctly mapped and that the submitted lead data is complete. |
| Authentication failure (e.g., “Unauthorized”) | Incorrect or expired IPQualityScore API Key | Double-check your API Key and update it if necessary to ensure proper authentication. |
| No risk score or validation details returned | Integration misconfiguration or selecting the wrong action endpoint | Confirm you have selected the correct IPQualityScore action (Email, Phone, or Proxy/VPN) and review the mapping and API endpoint. |
| Unexpected response status (e.g., HTTP 400 or 500) | Malformed lead data or invalid characters in the submission | Examine the raw lead data for formatting issues and ensure all input values meet the required format criteria. |
Frequently Asked Questions (FAQ)
What actions do IPQualityScore integrations support?
They support Email Validation, Phone Validation, and Proxy & VPN Detection—each designed to assess different aspects of lead data quality.
How do I decide which action to use?
Use Email Validation if your primary concern is verifying email deliverability and detecting disposable emails; use Phone Validation to check the format and risk associated with phone numbers; use Proxy & VPN Detection to analyze IP addresses for suspicious behavior.
What happens if a lead fails IPQualityScore validation?
You can configure downstream filters to block or flag leads that return a high risk score or an explicit error, ensuring that only high‑quality leads continue through your flow.
How can I test my IPQualityScore integration setup?
Submit test leads with valid (and intentionally invalid) data and verify that the JSON response in your LeadConduit Events tab includes the expected risk scores and validation status indicators.
Where can I find more information about error codes and response parameters?
Consult IPQualityScore’s official API documentation for a complete list of error codes, response parameters, and detailed explanations of each returned field.
Glossary
| Term | Definition |
|---|---|
| API Key | A unique identifier provided by IPQualityScore to authenticate API requests. |
| Email Validation | An action that checks an email’s deliverability, format, and risk of being disposable or fraudulent. |
| Phone Validation | An action that verifies the phone number’s format, carrier details, and risk factors including fraud indicators. |
| Proxy & VPN Detection | An action that analyzes IP addresses to detect the use of proxies, VPNs, or other anonymizing technologies. |
| Risk Score | A numerical value returned by IPQualityScore that estimates the likelihood of fraud or data inaccuracy. |
Comments
0 comments
Please sign in to leave a comment.