How to verify leads: lead validation checks and when they run
To verify leads, you check that the contact details are real and reachable, that the person exists and matches what they entered, and that a valid consent record goes with the lead. These lead validation checks run at different points: on the form, before the lead is offered to buyers, and after the sale.
Key points
- A verified lead has a reachable phone and email, a plausible identity and address, and a consent record that matches the submission.
- Some checks run on the form as the person types; others run before distribution; some only show after the buyer calls.
- Validation removes bad data, but it does not prove intent: a real person can still be a poor lead.
- Leads that fail validation after a sale are a common reason for returns.
What is a verified lead?
A verified lead is a lead that has passed checks on its data and its consent. Lead validation (also called lead verification) is the process of running those checks. Buyers set the checks they require; sellers and networks run them so that fewer leads are rejected or returned.
Validation answers "is this lead real and contactable, and do we have permission?" It does not answer "will this person buy?" That depends on intent and follow-up. See lead conversion rate.
The lead validation checks
| Check | What it confirms | What it catches |
|---|---|---|
| Phone format and line type | The number is a valid format and is a working line; whether it is mobile or landline | Typos, fake numbers, disconnected lines |
| Phone ownership or reachability | The number is in service and can be reached | Numbers entered for someone else, dead numbers |
| Email syntax and domain | The address is well formed and the domain accepts mail | Typos, throwaway and invalid domains |
| Address standardization | The address exists and matches the ZIP code and state | Made-up addresses, wrong state for the filter |
| Identity consistency | Name, phone, email and address plausibly belong together | Mixed or stolen details, form stuffing |
| Duplicate check | The same person has not been submitted recently | Double submissions, resold leads |
| Consent record check | A consent record exists for this submission, with page, time and the number entered | Missing or mismatched consent |
| Answer logic | Form answers are consistent (for example, a recent accident date) | Leads outside the buyer’s criteria |
Consent records are covered in TCPA consent record-keeping. Duplicates and how they happen are covered in duplicate leads.
When each check runs in the lead flow
On the form
Format checks on phone, email and ZIP code as the person types, so mistakes are fixed before submit.
At submission
The consent record is created and stored with the lead. Duplicate checks run against recent submissions.
Before distribution
Reachability, address and identity checks run before the lead is offered to buyers, so buyers bid on clean data.
At the buyer
The buyer may run its own checks on the post, and reject leads that fail.
After the sale
Contact attempts show wrong numbers and people who did not ask to be contacted. These become returns under agreed terms.
How to validate leads: a step-by-step setup
- Write down what a valid lead means for each buyer: required fields, states, criteria and consent format.
- Add format checks to the form itself, with clear error messages.
- Store a consent record for every submission, tied to the phone number entered.
- Run duplicate checks across a window that matches your buyers’ terms.
- Run reachability and identity checks before the lead is offered for sale.
- Track rejections and returns by source and by reason, and fix the source, not only the lead.
Sending traffic to Summit landers? Consent is captured on every lead, and leads carry consent certificates.
Who validates leads: sellers, networks or buyers?
Validation can run at each step, and the best results come when each party knows what the others check:
- Lead sellers and publishers check their own forms and traffic, because invalid leads are rejected or returned and earn nothing.
- Networks and brokers check leads before offering them to buyers, so buyers bid on clean data and returns stay low.
- Buyers check on delivery against their own rules and see the final signal: whether the person answers and wants the service.
Put the checks and the return rules in writing between each pair, so a lead that fails a check is handled the same way every time.
Validation and lead fraud
Validation catches many signs of fraud, such as made-up details and recycled data, but some fraud passes basic checks. Bots can enter well-formed data, and real details can be submitted by someone else. Fraud detection adds signals about how the form was filled in and where the traffic came from. See fake leads and lead fraud and bot and fraud traffic: how networks detect it.
Common mistakes
- Validating only after the sale. Buyers pay for bad leads and then return them; check before distribution.
- Treating a passed check as intent. A real, reachable person can still not want the service.
- Over-strict rules on the form. Rejecting valid entries for minor format differences loses real leads.
- Not storing the consent record with the lead. Without it, a buyer cannot show consent later.
Frequently asked questions
How do you verify a lead?
Check that the phone and email are real and reachable, that the name, address and other details are consistent, that it is not a duplicate, and that a consent record exists for the submission.
What is the difference between lead validation and lead verification?
The terms are used to mean the same thing: checking that a lead’s data and consent are real before it is sold or called.
Does validation stop all fake leads?
No. It removes bad data, but some fraud passes basic checks. Fraud detection adds behavioral and traffic signals.
Who pays for lead validation?
It depends on the arrangement. Sellers and networks often validate before selling, and buyers may run their own checks on delivery.
Related guides
- Fake leads and lead fraud: Types of fraud and how each is detected.
- Lead quality standards: The fields and records buyers should require.
- Why leads get returned: The common return reasons.
- Consent record-keeping: What records to keep and for how long.
- Sell your leads: For lead generators with their own forms.
Run the traffic. We handle the rest.
Every publisher is reviewed before going live. Email us your verticals, traffic sources, states and expected volume.
Or write to team@summitleads.ai. We reply by email.
What happens next
- Step 1: You email us.
- Step 2: We reply by email.
- Step 3: Every publisher is reviewed, and return and payment terms are agreed during onboarding, before you go live.
Already generating leads on your own forms? Sell your leads instead.