Website visitor identification that names the person, not just the company.

The 93% figure refers to account-level identification, meaning Knock2 can tell you which company a visitor is from 93% of the time. It's measured against "engaged sessions," which Google Analytics defines as any visit that lasts 10 seconds or longer, or includes 2 or more pageviews.

The 62% figure is for person-level identification (name, email, title) on US traffic, measured the same way. We publish both numbers because they answer different questions: which companies are on my site, and which individuals can I reach out to.

Knock2 uses a lightweight website pixel and a proprietary waterfall identification process to match site activity with relevant contact and company data.

The specific identification methods used may vary based on factors such as the visitor's location, available signals, data coverage, and applicable privacy requirements. Knock2 can identify companies globally, while contact-level identification is currently focused on eligible visitors in the United States.

When a match is available, Knock2 combines the identification result with business data and on-site behavior to help your team understand who is visiting, what they are interested in, and which visitors may be most relevant.

IP-level identification uses a visitor's network information to associate website activity with a company or organization. This is generally used for account-level identification and may represent multiple people visiting from the same business. Device-level identification uses signals associated with a specific browser or device to support more precise visitor matching.

Account-level identification tells you which company a visitor is from. Person-level identification tells you exactly who the individual is: name, title, work email, phone, and LinkedIn profile. Person-level data is only available for US traffic due to privacy regulations in other regions. Most teams use both: account-level coverage for breadth, person-level for direct outreach.

Account-level data (the company behind a visitor) typically appears in the dashboard within seconds of the visit. Person-level data (the individual, with contact details) takes a bit longer, usually minutes to a couple of hours, because resolving an individual runs through additional matching steps.

For most use cases (Slack alerts, outbound sequences, CRM enrichment), that latency is well within the window where the recency still matters.

Yes. Knock2 is built on the same class of identity and analytics technology already running on most B2B websites.

Person-level identification runs on US traffic only, by design. Everywhere else, Knock2 returns company-level information only. That is how it stays within GDPR, CCPA and ePrivacy expectations. The identity data itself is licensed from established data providers.

Person-level identification is limited to US traffic by design, to stay compliant with GDPR, CCPA, and the ePrivacy Directive in Europe. Account-level identification works globally.

Website visitor identification matches an anonymous session to a company, and on US traffic to a person. Knock2 identifies 93% of engaged sessions at the account level and 62% of US engaged sessions at the person level. An engaged session is 10 seconds or longer, or 2 or more pageviews. Google Analytics still measures the visit. Identification names who it was.

No. Knock2 is knock2.ai, website visitor identification for B2B teams. Knock AI at knock-ai.com is a different company. Check the domain before comparing match rates or pricing.

The 2026 comparison of Knock2, RB2B, Warmly, Leadfeeder, Snitcher, Vector, and Lead Forensics is best website visitor identification software. It separates person-level identification from company-level identification, and it leaves a cell blank when Knock2 has not published that vendor's number.