Some visitor identification tools promise the name, email and mobile number of the person who just read your pricing page. For a sales team that has stared at anonymous traffic for years, that pitch is hard to resist.
SiteSonar does not offer it. We identify the company behind a visit, investigate whether that company has a Path to Purchase with you, and name a person only when they tell you who they are. This post explains why we made that choice and what a rep gets in place of a phone number.
What contact-level visitor ID delivers
Person-level tools match a visitor’s network address and other signals against a purchased database of people. When a match comes back, the tool appends a name and contact details to the visit.
The numbers behind those matches deserve a close look:
- Coverage is mostly US-only. Person-level data from these vendors generally covers US residents. A buyer in Ontario, Monterrey or Stuttgart usually returns nothing.
- Real match rates are low. Independent estimates put true person-level matches at roughly 5 to 20 percent of US traffic. Vendors often quote much higher figures, and those usually blend company matches with person matches.
- A match is a guess. The tool reports a person with confidence even when the evidence is thin.
For an industrial seller, the last point causes the most trouble.
Why IP-to-person guesses fail on office networks
Most serious B2B research happens at work. An engineer at a mid-size equipment maker reads your capabilities page from the company network, and so do hundreds of colleagues in accounting, HR and the warehouse. They all share one public network address.
An IP-to-person tool sees that address and picks a name from the people it associates with it. It often gets the company right and the person wrong. The rep then calls a payroll clerk about a coating spec, or emails a plant manager who has never heard of you. The buyer who did the research never hears from you at all.
Each wrong call costs more than a rep’s time. It tells someone at the target account that you are watching them and guessing badly. In a market where a handful of accounts can make your year, that impression sticks.
Company-first, then first-party identity
SiteSonar starts with the company, the part of the signal that holds up. We read the network address, look up the organization behind it, and filter out home internet connections, mobile carriers, bots and your own staff. What remains is a list of companies that actually visited.
People enter the picture only through your own channels:
- Your forms. When a visitor fills in your RFQ, contact or sample form, we connect that person to their visit history.
- Your email links. When someone clicks a link in an email you sent, we know who clicked because you sent it to them.
We never buy, append or infer personal contact data. If nobody at the company has given you their details, the lead shows the company, what they did and why it matters.
What a rep gets in place of a phone number
A name with no context leads to a cold call. A company with a clear reason to talk leads to a useful conversation. Every SiteSonar lead carries a Sonar Reading and the evidence behind it:
- The verdict. Initiate, Investigate or Ignore, based on whether a specific part they make matches something you do.
- The signal. Echo, Contact or Lock, based on what the visitor actually did on your site.
- The part and the process. For example, a test instrument maker whose plastic housings need EMI shielding.
- The question to ask. One specific opening, drawn from the pages they read.
A rep who knows the part can find the right person in one call.
With that, the rep can call the main line, ask for the engineer responsible for that product, and open with something relevant. On Initiate · Lock, such as a quote page visit from a company with a clear path, the reading says call today. On Initiate · Echo, it says send the matching application page and wait.
Privacy is a sales point
Industrial buyers tend to be private people. Engineers and purchasing managers get plenty of spam already, and many work under supplier agreements or customer NDAs. A supplier who calls out of the blue, knowing exactly which page they read, can feel invasive.
A company-first approach lets you be open about how you work:
- You know which companies visited, which is how most B2B analytics has worked for years.
- You know people only when they reached out to you or clicked your email.
- You do not sell, share or buy anyone’s personal data.
That is easy to explain to a prospect and to your own legal team. It also keeps things simpler if you sell into Canada, Mexico or Europe, where rules on personal data are stricter.
What to do this week
- Audit any visitor ID tool you use now. Ask the vendor for its person-level match rate on its own, separate from company matches.
- Check the last ten “identified people” from that tool against your CRM. Count how many were the actual buyer.
- Make sure your RFQ and contact forms are short and easy to find. Those forms are where real names come from.
- Train reps to open with the part and the process, then ask who owns it.