Website Visitor Identification Tool: The One Spec That Decides It
Nearly every product in the category calls itself visitor identification. The label doesn't tell you which of two very different things it does.
A website visitor identification tool installs a pixel on your site, matches incoming visitors against an identity graph, and returns real contact records for the share it can resolve. Choosing between them comes down to one specification most buyers never ask about: whether the tool resolves individual people or only the companies their IP addresses belong to. Nearly every product in the category is accurately described as "visitor identification," and they mean two completely different things by it. Exact Match's Site ID resolves at the individual level: a single install pixel identifying 25–40% of verified human visitors, bots excluded, with full contact and demographic profiles delivered in real time.
Last updated: September 2026
Hardly anyone raises that distinction on a demo call. The teams who do end up with a tool that fits what they sell. The teams who don't often pay for company names they can't use.
Match rate is the wrong first question
Match rate is the number on every comparison page, and the first one to distrust, not because vendors lie about it, but because the denominator is almost never stated.
"We identify 40% of your traffic" can mean 40% of raw sessions, crawlers and uptime monitors included. Or 40% of verified human visitors after bots are excluded, which is a materially harder result. Both get written as 40%.
Then there's what counts as an identification. A tool that maps an IP to "Acme Corp" logs a match. So does a tool that returns a named person with a working email. Same tally, wildly different value, and the chart flattens them into one column.
The truth is you're not being sold something false. You're being sold a number whose unit was never defined. If a previous visitor ID pilot came in under its quoted match rate, that's why. Your measurement wasn't the thing that was wrong.
What "usable output" actually means
Define the finish line before shopping, because it isn't a match. It's a follow-up that actually happens.
That means a person with reachable contact details, not a company name you then have to research. The record arriving while the visit is still fresh. And the file landing in your CRM or ESP in a shape someone can import, because the most common way these tools die inside a company is that identified visitors pile up in an export nobody wants to hand-clean. Anyone who's bought data has lived this: exports never map cleanly, and someone always remaps columns after every pull.
Exact Match handles that last mile with background export jobs and CRM-specific column templates, so the file arrives import-ready rather than clean-up-ready. Unglamorous, and frequently the difference between a tool that gets used and one that gets cancelled at renewal.
The specification hardly anyone asks about
Here's the distinction that decides the whole purchase.
Company-level tools work by reverse IP lookup. They map the visitor's IP to a corporate network and report the organization. If you sell enterprise B2B into named accounts, this is legitimately useful: it feeds account-based outreach.
Individual-level tools match against a consumer identity graph and return the person. Different data source, different mechanism, different answer.
The market leans heavily toward the first kind and the labels don't warn you. Clearbit's visitor product was company-level reverse-IP only, and it's no longer independently developed: sunset and absorbed into HubSpot Breeze. Warmly does B2B-only company-level visitor identification. Both are accurately described as visitor identification tools. Neither will tell you who the individual consumer on your DTC storefront was.
If you sell to consumers, individual-level resolution isn't a premium tier of the same thing. It's the only version that answers your question. Site ID identifies 25–40% of verified human visitors (bots excluded) with full contact and demographic profiles in real time. Matching is deterministic, verified against multiple identity anchors including name, email, phone and address, against 250M+ verified U.S. consumer profiles that refresh daily.
Freshness matters more than it sounds. A graph that updates quarterly and one that updates daily both hand you an email address. Only one hands you an address that still receives mail.
For the mechanism-level walkthrough rather than this buyer's-guide framing, see identify anonymous website visitors; for how the tag behaves once installed, visitor identification pixel.
What you're actually paying for
If you're tired of pricing models that bill you more precisely when the product is working, read this part as carefully as the feature list.
The tracked competitive picture: ZoomInfo runs $15K+/yr on multi-year commitments with sales-gated pricing. Cognism is enterprise-only at roughly $15K–$50K/yr, built around EMEA GDPR-verified B2B contact data. Apollo.io is per-seat and credit-metered. Lusha prices per user seat against a narrower B2B contact database. RocketReach is per-seat and limited to B2B professional contacts. None of these are scams. They're models where usage drives cost, which means the finance conversation eventually becomes an argument about whether your team should look things up less.
Exact Match is one flat Unlimited plan: $999/mo or $6,999/yr, every product included (Audience ID, Clean ID, Predict ID and Site ID), with unlimited credits, no per-seat fees, no tier upgrades and no overage charges. Monthly cancels anytime. API and MCP access defaults to 30 requests per minute, raisable by agreement.
Visitor identification stops being a metered resource you ration. Install the pixel once and every resolved visitor is already paid for. You could identify twice as many next month and the invoice doesn't move.
Reading a vendor's spec sheet
Identity graph: the map of which identifiers belong to the same person. Every capability a visitor ID tool has is bounded by the graph behind it, which is why "how big and how fresh" beats almost any feature question.
Deterministic vs probabilistic matching: verified against real identity anchors, versus statistically inferred. Ask which one, in exactly those words, and notice whether the answer is direct.
Entity resolution and entity enrichment: turning a partial identifier into a full profile, then attaching attributes to it. Exact Match exposes both as API tools, and the same surface runs natively as an MCP server, so the graph can be queried from Claude, Claude Code or a Slack bot instead of only through a dashboard.
Subaccounts: scoped child identities under one parent API key, each with its own isolated rate limit and export concurrency, and billing visibility hidden from them. For an agency reselling to clients, that's the feature that decides whether it's operable at all.
Cleaning what you already have is the natural companion to identifying who's new, covered in crm data cleansing tool. The category definition lives at website visitor identification.
Frequently Asked Questions
What does a website visitor identification tool actually do?
It installs a pixel on your site, matches each incoming visitor against an identity graph, and returns a record for the share it can resolve. What comes back depends on the graph behind it: a company name for reverse-IP tools, or a named person with contact and demographic detail for individual-level tools like Site ID, which resolves 25–40% of verified human visitors with bots excluded.
How do I compare match rates between vendors fairly?
Ask two questions: what's the denominator, and what counts as a match. A percentage measured against raw sessions including bot traffic isn't comparable to one measured against verified human visitors, and an IP-to-company hit isn't comparable to a resolved individual with working contact details. Get both answers in writing.
Is a visitor identification tool worth it for a consumer business?
Only if it resolves individuals. Company-level reverse IP returns a residential ISP for consumer traffic, which isn't actionable. Individual-level matching against a consumer identity graph is the only mechanism that produces a contactable person from B2C traffic. Check which one a vendor does before anything else.
Can agencies run this across multiple clients?
Yes. Subaccounts give each downstream client a scoped child identity under one parent API key, with real data isolation, its own fair-share rate limit and export concurrency, and billing and credit visibility hidden from the client. Site ID's pixel is installed per site, so an agency running it for multiple clients installs a separate pixel for each client's site and generates that pixel under the client's own subaccount. Matched visitors land inside that subaccount instead of mixing with another client's results, the same way subaccount data isolation already works for the API products.
What's the fastest way to tell if it works on my traffic?
Install the pixel and watch a week of real sessions. Match rate varies by traffic mix, so a live read on your own audience beats any vendor benchmark. Because the plan is flat rather than metered, testing at full volume doesn't cost more than testing cautiously. You don't need to sample or ration to keep the trial cheap.
Get Started: Unlimited
One plan, everything included: every product, every feature, and unlimited credits. $999/mo, or $6,999/yr on annual billing.