--- title: "Visitor ID Accuracy: Evidence and Evaluation Method" description: "Visitor-identification accuracy requires independently verified ground truth about who visited." canonical_url: "https://www.leadpipe.com/blog/visitor-identification-accuracy-independent-test-results/" source_url: "https://www.leadpipe.com/blog/visitor-identification-accuracy-independent-test-results/" md_url: "https://www.leadpipe.com/blog/visitor-identification-accuracy-independent-test-results.md" content_type: "article" pubDate: "2026-03-03T00:00:00.000Z" last_updated: "2026-09-08T00:00:00.000Z" --- # Visitor ID Accuracy: Evidence and Evaluation Method Quick answer Visitor-identification accuracy requires independently verified ground truth about who visited. Match rate measures coverage, while field completeness and sales acceptance measure different outcomes. Do not treat a plausible contact profile as proof of a correct visitor match. Visitor-identification accuracy requires independently verified ground truth about who visited. Match rate measures coverage, while field completeness and sales acceptance measure different outcomes. Do not treat a plausible contact profile as proof of a correct visitor match. This is a Leadpipe-authored buying guide. Product statements are based on the linked vendor references; evaluation steps are recommendations, not reported test results. ## Editorial correction An earlier version of this article presented vendor scores as independent test results. This revision does not reproduce those scores because an inspectable underlying audit report and dataset were not established during the source review. The guidance below is an evaluation method, not a newly conducted benchmark or a certification claim. ## Separate the measures | Measure | Numerator | Denominator | | --- | --- | --- | | Person-level coverage | Unique returned people | Eligible unique visitors under the stated measurement method | | Identity correctness | Independently confirmed correct identities | Reviewed matches with ground truth | | Field completeness | Records containing required fields | Records reviewed | | Sales acceptance | Records meeting agreed fit and usability criteria | Records reviewed | | Delivery success | Accepted records reaching the intended owner | Accepted records intended for delivery | An unknown identity is not a correct or incorrect identity until evidence resolves it. Report the unknown count and how the review sample was selected. Keep company records and suggested account contacts out of person-level correctness calculations. ## Establish ground truth A controlled evaluation can use participating visitors whose identities and visits are independently logged with appropriate permission. Blind the reviewer to vendor identity where practical. Record browser, geography and eligibility constraints so the result is not generalized beyond the population tested. A professional profile matching the returned name confirms that the profile exists. It does not establish that the person made the visit. Agreement between two providers is also insufficient on its own because they may share sources or errors. ## Compare a common observation window Use equivalent page scope and record the exact plan and settings. Disclose if a trial allowance ends early. Deduplicate repeat activity and preserve rejected and unknown results. Publish sample sizes alongside rates and avoid a universal winner from a narrow sample. ## Follow accepted records into the workflow Correct identity is valuable only when the required process can use it. Separately inspect required fields, suppression, CRM association and owner assignment. Follow the accepted cohort into conversations and opportunities using a stated window; those outcomes are distinct from identification accuracy. The [RB2B versus Leadpipe evaluation design](/blog/rb2b-vs-leadpipe-90-day-ab-test/) explains how parallel data observation differs from randomized outreach. The [cost guide](/blog/visitor-identification-pricing/) helps keep the economic denominator honest. ## Where Leadpipe fits Leadpipe supports both account-level and person-level workflows. Its [IP to Company API](/product/ip-to-company/) retrieves stored company information from an IPv4 or IPv6 address; its separate [Identification product](/product/identification/) supplies eligible visitor records and activity. Choose company context for account research and person-level output when the action requires a specific visitor. A company lookup returns no people or visits. Confirm API eligibility and its separate lookup allowance in the [official documentation](https://docs.leadpipe.com/ip-to-company/introduction). Person-level coverage is strongest in the US. EU/UK traffic defaults to company-level identification; person-level requires affirmative consent. Fields can be missing, so judge required output on your actual traffic. If you need research signals from outside your website, evaluate [Orbit](/product/orbit/) separately and check its audience allowances. The [current pricing page](/pricing/) lists Pro 500 at $147/month for 500 identification credits. The trial is **7 days or 500 profiles, whichever comes first, no card**. Confirm the delivery and data-use requirements of your chosen plan. Use the [vendor evaluation kit](/resources/visitor-identification/) to record the same acceptance criteria for every candidate. [Start a Leadpipe trial](https://dashboard.leadpipe.com/auth/signup) when website identification is the requirement you want to measure. ## Related decisions Browse the [comparison directory](/compare/) for alternatives and head-to-head guides. Use the [software buying guide](/blog/b2b-website-visitor-identification-software/) to define requirements and the [person-versus-company guide](/blog/person-level-vs-company-level-visitor-identification/) to interpret identification results. ## Related vendor guides - [FullContact vs Leadpipe: Identity Inputs and Delivery](/blog/fullcontact-vs-leadpipe/) - [Leadpipe vs Clearbit: Visitor Data and HubSpot Workflows](/blog/leadpipe-vs-clearbit/) - [Leadpipe vs Leadfeeder: People, Companies and Sales](/blog/leadpipe-vs-leadfeeder/) ## Sources and review basis Published by Leadpipe. Vendor references support product descriptions; recommendations reflect our assessment of fit. Confirm current plan and contract terms before buying. - [Leadpipe IP to company API](https://docs.leadpipe.com/ip-to-company/introduction) - [Leadpipe product / buying reference](https://www.leadpipe.com/product/identification/) - [RB2B product / buying reference](https://www.rb2b.com/pricing) - [Warmly product / buying reference](https://www.warmly.ai/p/pricing) - [Leadpipe pricing and plan allowances](https://www.leadpipe.com/pricing/) [Explore all comparisons and our evaluation method →](/compare/)