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 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, which is most B2B traffic. Device-level matching is why Knock2 can reach 93%* account-level and 62%* person-level identification on US traffic.

From consented publisher login data. Major publisher websites (news outlets, commerce sites, content platforms) let users log in with email or a federated identity. Those authenticated identities are tied to the user's device fingerprint and shared with the ecosystem through identity graph partnerships — the same networks that power ad retargeting.

Knock2 sits on top of multiple graphs (rather than one single provider) and stitches them together, which is why our match rates are higher than tools built on a single data source.

IP lookup tells you what network a visitor is on, not who they are. If someone's working from home on their ISP's shared IP, from a coffee shop, on mobile data, or behind a corporate VPN, IP lookup can't reliably map to a person or company. That's why older visitor ID tools top out around 30 to 40% match rates.

Device fingerprinting identifies the specific laptop or phone that loaded your page. Combined with an identity graph that links devices to people, it works regardless of what network the device is on, which is how match rates climb into the 60s and 90s.

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.