Lead Forensics shows the company. Knock2 reveals the buyer.

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 device fingerprinting combined with an identity graph built from consented publisher login data. When someone logs into a major publisher site, their identity is tied to their device. When that same device later visits your site, our pixel matches it back to the person. It's the same underlying technology that powers retargeting pixels from Meta, Google, and LinkedIn.

Traditional visitor ID tools rely on IP address lookup, which fails for anyone on home WiFi, mobile, or a VPN. Device-level matching is why Knock2 can reach 93%* account-level and 62%* person-level identification on US traffic.

Three main differences. First, transparency: Lead Forensics claims an "industry-leading" match rate but doesn't publish a number. Knock2 publishes both 93%* account-level and 62%* person-level coverage on US traffic, measured against Google Analytics engaged sessions.

Second, data depth: Lead Forensics is account-only — you see the company, not the specific person — while Knock2 returns both the account and the individual, with name, title, email, phone, and LinkedIn.

Third, commercial model: Lead Forensics typically runs annual contracts with per-seat pricing in the tens of thousands of dollars. Knock2 starts at $199/month with no per-seat fees, and you can start month-to-month.

Both. Knock2 returns account-level data (the company) and person-level data (the specific individual, with name, title, work email, phone, and LinkedIn profile). Person-level identification is US traffic only due to privacy regulations in other regions. Most teams use both: account-level coverage for breadth, person-level for direct outreach.

Yes. Native integrations are built for HubSpot, Salesforce, Slack, Apollo, Outreach, Lemlist, Instantly, and Clay. For anything not on that list, webhooks cover Zapier, Make, n8n, and any other tool that accepts them. Identified visitors can be routed in real time based on lead score, pages visited, firmographics, persona match, UTMs, or any combination.

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: major publisher sites that users have signed into, tying their identity to an anonymous device fingerprint. When that same device later visits your site, we match it back to the identity that was originally consented to share.

Account-level identification works globally. Person-level identification (with names, emails, and contact details) is limited to US traffic by design. This is how Knock2 stays compliant with GDPR, CCPA, and the ePrivacy Directive in Europe. You won't see individual European or Asian visitors' personal details, but you will see which companies are visiting.

Plans start at $199/month (Startup) and scale with included credits. Identifying an account costs 1 credit, identifying a person costs 6 credits, and prospecting additional contacts at an account costs 3 credits. Most teams land on Growth ($499) or Scale ($999) once they see their actual traffic volume. Every plan includes a 7-day free trial.