Key capabilities
Visitor Identification
Resolve anonymous IP traffic to named companies and individual contacts using Knock2’s global identity graph. No form fills required.
Lead Scoring
Every identified visitor is automatically scored against your ICP criteria — firmographic fit, page intent, and visit frequency — so your team always knows who to call first.
Contact Enrichment
Go beyond company-level identification. Knock2 enriches visitor records with job title, LinkedIn profile, email, and phone data so you can reach the right person directly.
Webhooks
Receive instant HTTP push notifications whenever a high-scoring visitor lands on your site. Pipe alerts straight into Slack, your CRM, or any downstream system.
Filter Sets
Define reusable filter rules — by industry, employee count, intent page, ICP score, and more — to segment your visitor stream and focus on the accounts that matter most.
Multi-Tenant
If you’re building on top of Knock2 as a platform, the multi-tenant API lets you provision and manage isolated sub-tenants, each with their own tracking, data, and API keys.
How it works
Knock2 operates as a four-stage pipeline that runs automatically once you embed the tracking script on your site.- Tracking script fires — A single
<script>tag on your site sends an anonymous session event to Knock2 every time a visitor loads a page. - Visitor is identified — Knock2 resolves the visitor’s IP and session signals against its enrichment database, linking the session to a known company and, where possible, a named contact.
- Data is available via API — The identified account and contact records appear immediately in the REST API under
/v1/accountsand/v1/contacts, enriched with firmographics, ICP score, and visit history. - Webhook alerts fire — If the visitor matches a configured filter set, Knock2 fires a webhook to your endpoint in real time, carrying the full account and contact payload.
Identification accuracy improves over time as Knock2 correlates repeat visit patterns. Most customers see meaningful identification rates within the first 24–48 hours of going live.
What’s next
Quickstart
Install the tracking script and make your first API call in under five minutes.
Authentication
Learn how to get your API key, pass it in requests, and handle authentication errors.