B2B Website Visitor Identification in

• Choose company-level output when the question is which accounts are researching your site, not which employee visited✓. 1
• Evaluate person-level output separately, with a higher bar for identity accuracy, visitor expectations and permitted outreach✓. 2
• For UK visitors, review tracking tags under the ICO's PECR guidance before enabling non-exempt storage or access✓. 56

1. What is a company-level identification?

Leadfeeder describes its Web Visitors Tracker as JavaScript installed on the website✓. It says the main purpose is to identify visiting companies: technical signals such as IP address are matched against company databases and the visit is enriched with firmographic information such as company name and industry✓. That is a vendor-described method, not proof that every visit will resolve correctly. 1

The output level matters. Leadfeeder says its tracker shows companies, not named individuals, by default✓. An account appearing after a pricing-page visit therefore does not establish which employee viewed the page. Even if a sales rep recognizes a likely buyer at that account, that is an inference, not a visitor identity supplied by the company-level signal. Do not write personalized outreach that falsely implies you know the person's browsing history. 1

A practical company-level workflow starts with account qualification. Match the identified organization to a target-account list, verify whether it is already a customer or active opportunity, and select an account-level next step. This could be research for an account owner rather than an immediate message. Keep the captured page path and timestamp separate from any later contact enrichment so the source of each field remains visible.

2. What is a person-level identification?

RB2B's contact-level guide says it can recognize an individual visitor rather than only a company✓. It describes correlation using first- and third-party cookies, device identifiers and IP analysis, followed by profile enrichment from professional sources✓. This is a different claim from firmographic enrichment. A company match and a named-person match should not be counted as the same event. 2

RB2B also says company-level profiles do not contain employee details for anonymous visitors✓. That makes a useful quality-control rule: if your downstream CRM record suddenly has a name and email after a company-only match, identify the separate data source that supplied them. The visitor signal, the identity match and the professional profile enrichment can have different error modes. Preserve those stages in the audit trail rather than merging them into one opaque 'identified lead' field. 2

Geography changes the product surface. RB2B says its person-level identification applies to visitors located in the United States✓. Do not present a US person-level capability as though it applies worldwide. Its international company-level setting is a different product behavior, and a business operating across regions should test coverage and configure geography rather than extrapolating from a US sample. 3

3. First-party event, identity resolution and enrichment are separate

The first stage is the site event: a script or tag observes a visit. Leadfeeder says its tracker is a JavaScript snippet; RB2B says its cookies are stored under the customer's website domain✓. The second stage is identity resolution, such as Leadfeeder's company database match or RB2B's described correlation across cookies and identifiers✓. The third stage is enrichment, such as adding firmographic or professional profile fields✓. 124

Calling the whole workflow 'first-party data' obscures the difference. The website visit may be observed on a first-party site, but the matched company or professional profile can depend on an external vendor's data. Record what the visitor supplied directly, what the site observed, what the vendor inferred and what the vendor appended. The result will be easier to evaluate, correct and explain to a sales team. 12

4. Privacy review is not optional because the output is B2B

The UK Information Commissioner's Office says PECR regulation 6 can apply when a script or tag accesses or stores information on a user's device✓. It also says UK GDPR applies where the information is personal data✓. Its guidance states that calling a technology first-party rather than third-party is not the central privacy test✓. These are UK-specific regulatory statements; they are not a legal conclusion for every website or jurisdiction. 5

The ICO says non-exempt storage or access technologies should not be used before the subscriber or user has consented✓. Leadfeeder says its tracker can be configured to set cookies only after consent, and RB2B says it does not enforce consent compliance for customers✓. Those vendor statements describe configuration and responsibility, not a ruling that a particular implementation is lawful. Have qualified counsel assess the actual script behavior, purposes, data flows, notices, consent controls, retention and outreach rules for the places where visitors live. 136

Do not assume that company-level output removes every privacy question. The ICO's tag guidance focuses on storage and access behavior on a user's device, and the rules are not decided solely by whether the dashboard shows a person name✓. Conversely, person-level output does not by itself tell you which legal basis or contact rule applies in every US state or country. The specifics depend on jurisdiction and the implementation. 5

5. How to evaluate a vendor without trusting a headline match rate

Define three denominators before a pilot: total eligible visits, visits linked to a company, and visits linked to a named person. RB2B itself distinguishes person-level and company-level identification, while Leadfeeder describes a default company-level output✓. Do not divide named-person matches by only already-identified companies and call the result a sitewide person-resolution rate. 12

Test a controlled sample of accounts and visits. Review whether the company is correct, whether the named visitor can be independently verified, and whether an apparent remote-worker location is being mistaken for a company's headquarters. Include known internal traffic, VPNs, shared networks and anonymous visitors as explicit edge cases. This is an evaluation design, not a claim that a vendor's published average will reproduce on your traffic.

Measure business usefulness separately from technical matching. How many identified accounts fit the ICP? How many were already known in the CRM? How many gave a rep a genuinely useful research prompt? How many downstream conversations were appropriate and welcomed? A larger match list is not automatically better if it adds uncertain identities or creates outreach the recipient would find intrusive.

6. A cautious operating workflow

Start with an account-level use case and a short retention window. Map the tracking script, identity vendor, CRM destination and permissions before launch. Configure consent handling based on a jurisdiction-specific review, then test a few visits in each geography to confirm what fires before and after a user's choice. Leadfeeder documents a consent-aware cookie configuration, while RB2B states customers must handle consent compliance themselves✓. 13

Once data arrives, label each field by origin: site event, company match, person match, enrichment or rep-entered note. Restrict who can see a named-person profile and define a correction route. Route ambiguous company matches for research rather than automatic outreach. Audit the pipeline periodically because a valid installation and a high match count do not prove identity accuracy, privacy compliance or revenue impact.

FAQ

How we researched this

We captured current Leadfeeder and RB2B help pages and UK ICO guidance on October 1, 2026. Vendor statements about matching and enrichment are attributed to those vendors; the ICO is used only for UK regulatory context. The earlier Dealfront Leadfeeder help URL redirected to a Leadfeeder help URL, recorded in the snapshot. We did not independently test match rates, determine any site's legal compliance or infer a universal right to contact identified visitors.

Turn signals into responsible research

Modern Inbound can help structure account research and handoff rules around the signals you can responsibly use. Discuss a research-led outbound workflow, or email [rish@moderninbound.com](mailto:rish@moderninbound.com).