The GTM stack you've been duct-taping together, in one system.
Knock2 identifies every site visitor, scores them against your ICP, enriches the committee, validates every email, and routes them into your CRM, Slack, and sequencer automatically.
%20(1).png)
.png){kind=logo}
Frequently asked questions
The 93%* figure refers to account-level identification on engaged sessions (Google Analytics defines an engaged session as 10 seconds or more, or 2+ pageviews). The 62%* figure is for person-level identification on US traffic. For RevOps, this means a consistent signal layer feeding your CRM, routing rules, and attribution — not a best-effort data source that varies wildly by account size or traffic pattern.
Most teams land on RevOps as the owner because Knock2 sits at the intersection of identification (data), scoring (rules), routing (workflows), and CRM integration — all RevOps territory. Marketing and sales are the consumers; RevOps configures and maintains.
Practically, RevOps owns the ICP definition, lead scoring prompts, routing rules, and CRM field mapping. Marketing surfaces ABM lists and nurture sequences. Sales works the identified list.
Initial setup is typically an hour or two: install the pixel, write a natural-language ICP description, configure one or two routing rules (a Slack alert, a CRM push), connect HubSpot or Salesforce. The ICP and scoring logic live in Knock2, not your CRM, so you're not building new workflows inside HubSpot or Salesforce.
Ongoing tuning is low — mostly thumbs up / thumbs down on scored visitors to refine the model, plus occasional ICP updates when targeting shifts.
Yes. Identified visitors can be routed to specific reps, Slack channels, or CRM queues based on firmographics (company size, revenue, industry), location (country, state, region), or account ownership in your CRM. Round-robin and rule-based assignment both work.
You can run separate scoring models per segment — for example, one for enterprise SaaS and another for mid-market services — each with its own ICP description, threshold, and routing rules. The same identified visitor can hit multiple models independently and route to different reps or workflows based on which model matched.
Plans start at $199/month (Startup) with no per-seat fees, so your whole revenue team can use Knock2 without per-user cost scaling. Most teams land on Growth ($499) or Scale ($999).
Hear it from
Watch real teams share how Knock2 transformed their pipeline
Ready to be the next
Join 1,000+ GTM leaders turning website traffic into qualified pipeline