Identify more person-level traffic than any other tool.

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 specific individual with contact details) takes a bit longer — usually minutes to a couple of hours — because person-level identification runs through additional identity graph matching.

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

Yes. Knock2 uses the same underlying technology as ad retargeting pixels from Meta, Google, and LinkedIn. Our data comes from consented publisher login co-ops, tying identity to an anonymous device fingerprint.

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