InfutorData Identity Scoring integration

Feature Snapshot

Summary:
The InfutorData Identity Scoring integration adds a verification step to your LeadConduit flow. It verifies lead identities with InfutorData ID scores, appending an overall verification score plus validity and risk scores, and it can filter leads that fall below a confidence threshold you set.

Key Benefits:

• Scores how confidently a lead’s identity was verified, on a 0 to 100 scale.
• Filters out leads below the confidence level you choose before they move through the flow.
• Runs inside the flow as a step you configure with its own credentials and failure handling.

Typical Use Cases:

• Stopping low-confidence identities before you deliver to a buyer.
• Appending a verification score so downstream steps can route on it.
• Screening for validity and risk on incoming leads from a single identity graph.

How Identity Scoring works

InfutorData offers more than one integration. Identity Scoring is the one that verifies identities and appends an ID verify score along with validity and risk scores. You add it as an integration step, authenticate with your InfutorData credentials, set the minimum ID verify score to filter against, decide what happens when the filter has no data, and choose what the flow does when InfutorData returns a failure response.

The ID verify score runs from 0 to 100, and higher is better. Leads InfutorData returns no score for are not stopped by the filter.

Step‑by‑Step Instructions

Step 1. Add an integration step to your flow

• Goal: Open the step picker and start adding an integration.
• Context: Identity Scoring runs as a step inside an existing flow, so you begin from the flow you want to score.

Instructions:

1. Open your flow.
2. Click Add to Flow in the top right.
3. Under Steps, click Integration.

Expected Result:
The “Add an Integration” search dialog opens.

Step 2. Find and select InfutorData

• Goal: Locate the InfutorData integration.
• Context: The search matches on the vendor name, so a few letters are enough.

Instructions:

1. In the search box, type InfutorData.
2. Select the InfutorData tile.

Expected Result:
The InfutorData integration is selected and you move to the integration selector.

Step 3. Choose the Identity Scoring integration

• Goal: Pick Identity Scoring from InfutorData’s available integrations.
• Context: InfutorData offers several integrations (Identity Completion and Attributes among them). Identity Scoring is the one that verifies identities and appends ID scores.

Instructions:

1. Select InfutorData Identity Scoring.
2. Click Next.

Expected Result:
The InfutorData authentication dialog opens.

Step 4. Enter your InfutorData credentials

• Goal: Authenticate the integration with your InfutorData account.
• Context: Enter the credentials provided by InfutorData into the integration configuration screen in LeadConduit.

Instructions:

1. Enter your Account Code (lac).
2. If you have them, enter the optional Audit Profile Key (lak) and Agency Code.
3. Click Confirm.

Expected Result:
InfutorData accepts the credentials and moves you to the score filter. If you need help finding these values, use the How do I get my InfutorData credentials? link in the dialog.

Step 5. Set the minimum ID verify score

• Goal: Choose the confidence threshold that leads must meet.
• Context: The ID verify score grades how confidently the lead’s identity was verified, from 0 to 100. Leads below your chosen level are filtered out. Leads InfutorData returned no score for are not stopped by this filter.

Instructions:

1. From the Minimum ID verify score dropdown, choose a level (for example, Low confidence or better (50+) stops leads with a score below 50), or leave it on Don’t filter.
2. Click Continue.

Expected Result:
The no-data handling step opens.

Step 6. Choose what happens when the filter has no data

• Goal: Tell the flow how to treat a lead when InfutorData returns no data for an active filter.
• Context: InfutorData omits fields it has no data for. This setting also applies to the stop-on-failure step.

Instructions:

1. From the dropdown, choose Let the lead through or the stop option.
2. Click Continue.

Expected Result:
The failure-handling step opens.

Step 7. Set the failure behavior

• Goal: Tell the flow what to do when InfutorData returns a failure response.
• Context: This controls whether a failed verification stops the lead or lets it keep moving through the flow.

Instructions:

1. Choose one option:
   • Stop processing the lead and mark the lead as failure — the lead does not continue past this step.
   • Continue processing the lead — the lead moves on even without a score.
2. Click Add to Flow.

Expected Result:
The integration is configured and added to your flow.

Step 8. Confirm the step was added

• Goal: Verify Identity Scoring now appears as a step.
• Context: The new step shows in the flow’s Steps list. If you set a score filter, a companion Filter step is added below it to stop leads below your threshold.

Instructions:

1. Look for InfutorData - Identity Scoring in the Steps list.
2. Click it to review its module, field mappings, and other settings.

Expected Result:
InfutorData - Identity Scoring appears as a numbered step in your flow, with a Filter step below it if you set a threshold.

Step 9. Save the flow

• Goal: Make the new step live.
• Context: Adding the step stages it in the flow builder. Saving is what deploys the change to your running flow.

Instructions:

1. Click Save in the top right.

Expected Result:
Your flow is saved and now runs with the InfutorData Identity Scoring step in place.

Validation & Monitoring

• Test the Setup: Use Test Flow to send a sample lead and confirm InfutorData appends the ID verify score and applies your threshold.
• Where to Monitor: Open the step to check its field mappings, and watch the flow’s events to see the score and filter results on live leads.

Best Practices

• Pick a threshold that matches how strict you need to be. A higher minimum stops more leads.
• Remember that leads with no returned score are not stopped by the filter, so add a no-data rule if you want to catch them.
• Keep the failure behavior on Stop processing when the score is required for the buyer or later steps, so unscored leads do not move forward.

Troubleshooting

Frequently Asked Questions (FAQ)

Q: Which InfutorData integration should I choose for identity verification?
A: InfutorData Identity Scoring. It appends an ID verify score plus validity and risk scores. Identity Completion and Attributes are separate InfutorData integrations for different jobs.

Q: What does the ID verify score mean?
A: It grades how confidently the lead’s identity was verified, on a 0 to 100 scale where higher is better.

Q: What happens to leads with no score?
A: They are not stopped by the score filter. Use the no-data setting if you want to stop them.

Q: Why is there a second Filter step in my flow?
A: When you set a minimum score, LeadConduit adds a companion Filter step below the integration to stop leads below your threshold.

Glossary

• infutordata-identity-scoring-integration-01-add-integration.png200 KB
• infutordata-identity-scoring-integration-02-search-infutordata.png200 KB
• infutordata-identity-scoring-integration-03-select-identity-scoring.png200 KB
• infutordata-identity-scoring-integration-05-minimum-id-verify-score.png200 KB
• infutordata-identity-scoring-integration-04-enter-credentials.png200 KB
• infutordata-identity-scoring-integration-06-no-data-behavior.png200 KB
• infutordata-identity-scoring-integration-07-failure-behavior.png200 KB
• infutordata-identity-scoring-integration-08-step-added.png200 KB