Free evaluation kit
Choose visitor identification software with evidence.
A returned profile is the start of the evaluation. Use these templates to check identity, fit, delivery and cost before choosing a subscription.
Created by Leadpipe for comparing any vendor. No email required. Updated September 24, 2026.
Get the trial scorecard →Start with one decision
Write down who will use the output, which accounts and roles matter, and what action follows a match. An account-based advertising team and a sales rep need different evidence. Agree on the required fields and acceptable failure conditions before you see vendor results.
- Choose a representative traffic window and document eligible pages and regions.
- Use equivalent configurations. If a trial ends early, disclose the different exposure.
- Inspect identity, fit and delivery using the scorecard below.
- Compare total cost against accepted output, then follow the cohort into pipeline.
Visitor identification trial scorecard
Record the stages separately. Never divide a company count by a person count, or describe a contact suggested for an account as a confirmed visitor.
| Stage | What to record | Review rule |
|---|---|---|
| Eligible traffic | Unique visitors in the agreed pages, regions and time window. | Document exclusions and measurement differences before comparing providers. |
| Returned records | Unique people or companies returned by each provider. | Keep person and company counts separate; deduplicate repeat activity. |
| Reviewed records | Records actually inspected by your team. | Log sample selection and unknown results. A sample is not the whole population. |
| Accepted records | Reviewed records meeting every required identity, fit and field rule. | Assign a rejection reason to each failure; do not silently drop it. |
| Delivered records | Accepted records reaching the intended destination and owner. | Check duplicates, retries, suppression and missing fields. |
| Business outcomes | Meetings, opportunities and wins linked to the cohort. | Use a defined observation window and separate sourced from influenced pipeline. |
For a reviewed sample, report acceptance as accepted records divided by reviewed records. Report the sample size alongside the rate. Unchecked records remain unknown. Set your own acceptance threshold based on the workflow; this template does not supply a universal benchmark.
Download the editable scorecard (.md) →Review records without losing the unknowns
Use one row per reviewed record. Keep identity evidence, audience fit, required fields, suppression and delivery as separate checks. An email that accepts mail does not prove the person visited your site.
Use internal references instead of names or contact details in a shared review sheet. Delete the clearly labeled example row before use. Keep the same sample-selection rule for each vendor, and record unresolved cases instead of counting them as successful matches.
Download the record review sheet (.csv) →Decision rules: accepted means every required check passed; rejected means at least one required check failed; unresolved means the evidence is incomplete. Report each count alongside the total reviewed.
Vendor questionnaire and RFP template
Send the same questions to each shortlisted vendor. Ask for a source or demonstration with each answer. Keep roadmap promises separate from features available in the quoted plan.
- Identity and coverage
- Does this row represent the actual visitor, the visiting company, or a suggested contact? What changes by region?
- Fields and freshness
- Which fields are included, which can be missing, and what does each timestamp mean?
- Delivery and ownership
- Which plan supports our CRM, webhook or API? How are retries, duplicates and existing owners handled?
- Exclusions and data handling
- How do page exclusions, customer suppression, opt-outs, retention and deletion work? Supply the relevant documentation.
- Commercial terms
- What consumes a credit? How are repeat visits, overages, seats, domains and renewal priced?
- Evaluation evidence
- Which answers are documented, observed in our trial, or only proposed? What remains unresolved?
Use a cost denominator your team can act on
Add subscription, implementation, operator time and any required enrichment for the same period. Divide that total by accepted records to compare operating cost. If there are no accepted records, the ratio is undefined; report the cost and zero output separately.
For illustration, a $500 evaluation with 100 accepted records costs $5 per accepted record. At 25 accepted records it costs $20. These are hypothetical inputs, not vendor performance claims. Neither result proves ROI: that requires attributable financial outcomes.
Use the ROI worksheet and attribution guide for the next stage.
Guides for each buying decision
Write the buying requirements →
Choose the identity level, required fields and destination.
Build a vendor shortlist →
Compare ten tools by workflow and fit.
Define what counts as identified →
Separate visiting people, companies and suggested contacts.
Compare the complete cost →
Include subscription, implementation and operating effort.
Measure business outcomes →
Keep accepted records, pipeline, revenue and profit separate.
Check a multi-site setup →
Validate domain coverage, client boundaries and CRM delivery.
Run the scorecard on your own traffic
Leadpipe Identification helps identify eligible visitors on your site. Try it for 7 days or 500 profiles, whichever comes first, no card. Record what your team can actually use.
Start your free trial →