Website visitor identification
Website visitor identification (or visitor resolution) matches anonymous website traffic to a company, and sometimes a named person, using IP and other signals, so a team can see which accounts are looking at its site before anyone fills out a form.
Website visitor identification, also called visitor resolution or de-anonymization, matches otherwise-anonymous traffic on a site to a company, and in some tools a named person, using IP data and other matching signals. Tools like RB2B resolve anonymous visits to a company; engagement-focused layers like Warmly go further and try to surface which visitor is worth a look. Either way, the output is a company, or person, a team didn't have to wait for a form-fill to learn about.
A resolved visit still isn't intent
The same caution that applies to any intent signal applies here specifically. A resolved visit tells a team a company looked at its site. It doesn't say who within that company looked, why, or whether they're anywhere near a buying decision. Treating a resolved visit as a qualified lead skips the exact verification step that turns a hypothesis into something worth a send: what page, how many times, and over how many days.
Page-level weighting matters more than the fact of the visit. A pricing page revisit means someone's doing math. A single blog read costs a visitor nothing and can come from a paid social click they don't remember clicking. A visitor-identification tool hands a team the company. It still needs a scoring layer on top that weighs what that company actually did on the site, or a resolved visit just becomes an expensive, better-labeled version of the same noise a page-view counter always produced.
In practice
Pair visitor identification with page-level weighting, pricing and demo pages scored well above a single blog read, rather than routing every resolved company straight to a rep. Combine it with other account-level signals (funding, hiring, job change) before treating a resolved visit as the reason for a send.
What people get wrong
A resolved company visit gets treated as a lead in itself, when it's a company-level hint that still needs a real named contact, a reason, and a scoring pass before it's worth an outreach send. The tool solves who looked. It doesn't solve who to email or why now, and skipping that gap is how a resolved-visitor list turns into outreach that reads like a data feed with no judgment behind it.
