Don't just receive lead data. Verify the interaction behind it.
Traditional lead validation can check whether an email address or phone number looks valid. Evidora adds another layer: a record of the digital interaction associated with the submission.
When a visitor completes a form on a publisher's landing page, the Evidora tracking script captures information about that interaction and generates an Evidence Record. The record is associated with an Evidence Record ID that can travel with the lead.
The publisher includes that ID when sending the lead to IntuList. IntuList can then contact Evidora in real time to validate the record and apply the verification rules configured for the receiving list.
This gives lead buyers an additional way to identify missing, invalid, mismatched, or suspicious submissions before accepting them into their system.
A new layer of lead verification
IntuList continues to handle your imports, validation rules, and lead management. Evidora adds supporting evidence about the online interaction associated with a submitted lead.
From a form submission to a verified lead
The integration connects the original form interaction with the lead that arrives in your IntuList account.
Capture the interaction
The publisher adds the Evidora tracking script to the lead landing page. When a visitor interacts with the form, Evidora creates an Evidence Record and provides an Evidence Record ID.
Pass the Evidence Record ID
The publisher includes the Evidence Record ID with the lead data sent to IntuList, using the evidence_record_id field.
Verify during import
IntuList checks the Evidence Record with Evidora and applies the verification settings for the destination list before the lead is accepted.
Verification rules you control
Enable Data Verification for a list and choose which checks should apply to incoming leads.
Evidence Record validation
Confirm that the submitted Evidence Record ID corresponds to a valid record in Evidora. Missing or invalid record IDs can be rejected.
Email and phone matching
Compare the email address and/or phone number submitted with the contact details associated with the Evidence Record.
Bot score threshold
Set the maximum bot score you are willing to accept. IntuList can reject records that exceed the threshold configured for the list.
Interaction time limit
Set a maximum age for the Evidence Record so you can screen out leads submitted too long after the recorded interaction.
List-level configuration
Choose the verification rules that make sense for each list instead of applying one set of requirements to every lead source.
Import rule coordination
Data Verification works alongside your other IntuList import rules, helping ensure leads meet the requirements you have configured.
Keep the evidence for leads you accept.
With Auto Retain enabled, IntuList can retain the associated Evidora Evidence Record after a lead successfully makes it into your IntuList account.
Retention takes place only after the lead passes the applicable IntuList import rules. For example, a lead rejected by another validation step is not retained just because it included an Evidence Record ID.
Auto Retain requires your own connected Evidora account. The IntuList-provided Evidora account supports verification, but does not include evidence retention.
Auto Retain
Retain evidence records for leads that successfully pass your import requirements.
Enable Data Verification in IntuList
Set up the Evidora connection, coordinate with your lead sources, and choose the checks you want to enforce.
1. Choose your Evidora account
Select the IntuList-provided Evidora account to verify records, or connect your own Evidora account. Your own account is required if you plan to use Auto Retain.
2. Set up your lead sources
Your publishers need to add the Evidora tracking script to their landing pages and pass the generated evidence_record_id with each lead post to IntuList.
3. Enable it for a list
Open the list configuration, find Data Verification, and enable it. Once enabled, incoming lead posts for that list must include an Evidence Record ID.
4. Configure your verification rules
Choose whether to match email or phone, set your maximum bot score and interaction time limit, and enable Auto Retain if you have connected your own Evidora account.
Data Verification FAQ
Does the publisher need to do anything?
Yes. The publisher needs to place the Evidora tracking script on the landing page where the lead form is submitted and include the generated evidence_record_id in the lead post sent to IntuList.
Does every IntuList customer need an Evidora account?
No. You can select the IntuList-provided Evidora account for record verification. Connect your own Evidora account only when you need your own account's features, including Auto Retain.
What happens when a lead fails verification?
IntuList applies the Data Verification rules configured for that list. A missing or invalid Evidence Record ID, a contact detail mismatch, an excessive bot score, or an interaction outside your configured time limit can cause the lead to be rejected.
Does Auto Retain save every submitted Evidence Record?
No. When enabled with your own connected Evidora account, IntuList retains the record only after the lead successfully passes the applicable import rules and enters your IntuList account.
Does this replace IntuList's existing validation tools?
No. Evidora adds evidence about the digital interaction associated with a lead. It complements your existing IntuList validation and import rules.
See the IntuList and Evidora integration in action.
Try the interactive demo to see how an Evidence Record is submitted and verified.