Data Verification
Data Verification helps you verify incoming leads before they are imported into an IntuList list. Using data captured by the Evidora tracking script on your publisher’s forms, IntuList can validate lead information, assess the likelihood that a submission came from a human, and enforce lead freshness requirements.
You can configure verification rules for each list to help ensure the leads you accept meet your quality requirements.
Important: You need to activate your Evidora Integration in your IntuList account before using this feature.
How It Works
The process starts when a publisher adds the Evidora tracking script to their website, where it monitors and analyzes visitor interactions with the lead form. Evidora captures detailed information about the session, including the data submitted, submission timing, and signals that help assess whether the interaction was legitimate or automated. Evidora generates an evidence record and automatically injects its unique Evidence Record ID into the form as a hidden field. When the lead form is submitted, the publisher passes this ID along with the lead data to IntuList through their existing list integration. From there, IntuList takes over, connecting to Evidora to retrieve and validate the evidence record against the verification rules configured for the list. This allows IntuList to verify the lead’s authenticity, identity, and freshness before accepting it.
Enabling Data Verification
To enable verification for a list, open the list’s settings and expand the Data Verification section. Turn on Enable Data Verification to activate the feature, then configure the rules you want to apply.
Data Verification uses information collected by the Evidora tracking script on your publisher’s lead forms. Before using this feature, make sure your Evidora integration is active and that your publisher is passing the associated evidence record ID along with each lead submitted to IntuList.
Identity Matching Rules
These settings determine whether the contact information submitted with a lead must match the information captured in the original form submission.
Match Email Address
When enabled, IntuList verifies that the email address on the incoming lead matches the email address recorded by Evidora.
If the email addresses do not match, or the evidence record cannot be validated, the lead fails verification.
Enable this option when you want to confirm that the email address being delivered matches the one entered on the publisher’s form.
Match Phone Number
When enabled, IntuList verifies that the phone number on the incoming lead matches the phone number recorded by Evidora.
If the phone numbers do not match, or the evidence record cannot be validated, the lead fails verification.
Enable this option when phone number accuracy is important to your lead acceptance requirements.
Note: Email and phone matching can be enabled independently. If both are enabled, both values must match the evidence record for the lead to pass verification.
Quality & Age Thresholds
These settings help you control the quality and freshness of incoming leads.
Max Bot Score
The bot score estimates the likelihood that a form submission was automated rather than performed by a human. Lower scores indicate a greater likelihood of human activity, while higher scores indicate a greater likelihood of bot activity.
Select the maximum bot score you are willing to accept. Leads with a bot score above the configured threshold fail verification.
For example, setting the maximum bot score to 20 allows leads with scores up to 20 to pass this check while rejecting leads with higher scores.
Choose a threshold that balances lead quality with your tolerance for potentially automated submissions.
Max Lead Age (Minutes)
This setting limits how old a lead can be when it is submitted to IntuList, helping you enforce lead freshness requirements.
Enter the maximum permitted age in minutes. Leads older than the configured limit fail verification.
For example, setting the maximum lead age to 2.5 minutes means a lead must be no more than 2.5 minutes old to pass the age check.
This is particularly useful when you require real-time or near-real-time lead delivery and want to reject leads that were captured too long before being submitted.
How Verification Works
When Data Verification is enabled, IntuList evaluates incoming leads against the rules configured for the list.
Depending on your settings, verification can include:
- Evidence validation: Confirming that the supplied evidence record exists and can be validated.
- Identity matching: Checking that the lead’s email address and/or phone number matches the information captured during the original form submission.
- Bot detection: Rejecting submissions whose bot score exceeds your configured maximum.
- Lead freshness: Rejecting leads that exceed your maximum permitted age.
A lead must pass all applicable verification checks to be accepted. If a lead fails verification, IntuList rejects it and records the appropriate import result so you can identify why it was not accepted.
If Data Verification is disabled, these verification rules are not applied.
Best Practices
- Start with the fields that matter most. Enable email matching, phone matching, or both based on your lead acceptance requirements.
- Set an appropriate bot score threshold. A stricter threshold can help reduce automated submissions, but avoid assuming that a score alone proves whether a submission is legitimate.
- Set a realistic lead age limit. Use a short window for real-time lead delivery, or a longer window if your workflow allows for delays.
- Confirm your integration is working. Make sure your publisher’s forms use the Evidora tracking script and that the resulting evidence record ID is included with each lead sent to IntuList.
- Review failed imports. Use import results to understand which verification checks are failing and adjust your rules if necessary.
Data Verification gives you control over the evidence, identity, quality, and freshness requirements that incoming leads must satisfy before entering a list.