Overview
Your website is your most active sales channel — and also your most wasteful. Industry data consistently shows that 97% of B2B website visitors leave without identifying themselves. No form fill, no chat conversation, no trial sign-up. They visited your pricing page, read your integration docs, compared your plans — and vanished.
The technology to de-anonymise these visitors has matured significantly. Reverse IP lookup, device fingerprinting, and first-party cookie matching can now identify the company (and increasingly the individual) behind an anonymous visit. When combined with page-level intent scoring, this data becomes a powerful prospecting signal.
This playbook covers five website visitor signals — pricing page activity, security/terms page visits, integration page activity, documentation page visits, and repeat anonymous visits — and shows you how to turn them into qualified pipeline. For the complete signal taxonomy, see our signal-based prospecting guide.
The Signals This Playbook Uses
| Signal | Propensity | Volume | Strength |
|---|---|---|---|
| Pricing page activity | 9/10 | 5/10 | High |
| Security/terms page activity | 8/10 | 3/10 | High |
| Integration page activity | 7/10 | 5/10 | Medium |
| Documentation page visits | 5/10 | 7/10 | Medium |
| Repeat anonymous visits (3+ sessions) | 7/10 | 4/10 | High |
Pricing page activity is the single strongest website intent signal. A visitor on your pricing page is evaluating cost — they have already decided your product might solve their problem and are now checking whether it fits their budget.
Security and terms page visits are late-stage buying signals that most teams ignore. When someone reads your SOC 2 documentation or terms of service, they are conducting due diligence. This is procurement-level activity.
Integration page activity signals technical evaluation. The visitor is checking whether your product fits their existing stack — a practical, implementation-focused question that indicates serious consideration.
Repeat visits from the same company compound intent. A single visit could be casual research. Three visits from the same IP over two weeks is a buying committee doing their homework.
Step 1: Detection Setup
Required tools:
Alert configuration:
Page-level intent scoring:
| Page Type | Intent Score | Rationale |
|---|---|---|
| Pricing | 10 | Active budget evaluation |
| Security/Terms | 9 | Procurement due diligence |
| Integration/API docs | 7 | Technical evaluation |
| Case studies | 6 | Social proof gathering |
| Product features | 5 | Solution exploration |
| Blog/resources | 2 | Early research |
| Homepage only | 1 | Brand awareness |
Step 2: Signal Qualification
Not all website visitors are created equal. Layer company identification with firmographic and behavioural filters.
Firmographic filters:
Behavioural filters (apply in order):
Enrichment steps:
After identifying the company, enrich with contact data. Use Clearbit, ZoomInfo, or Apollo to find the likely buyer: the person whose title matches your buyer persona at that company. If the identified company has 500+ employees, look for department-level signals to narrow the contact.
Step 3: Outreach Execution
Timing: Same-day or next-day for Tier 1 signals. Within the week for Tier 2.
Channel priority:
Critical rule: Never reference that you know they visited your website. This feels invasive and damages trust. Instead, use the intent signals to inform your message — lead with relevance, not surveillance.
Template 1: Pricing Page Visitor (Company Identified)
Hi [Name], we have been working with several [industry] companies at [their stage] on [problem your product solves]. Teams like [Customer A] and [Customer B] have seen [specific outcome].
>
I noticed [Company] is in a growth phase right now — [reference a public signal: recent hire, funding, product launch]. Would it make sense to explore whether [your product] could support that?
>
Happy to share a quick comparison of how companies your size typically structure their [relevant function].
Template 2: Integration Page Visitor
Hi [Name], quick question — is your team at [Company] currently evaluating [product category] tools that integrate with [tech they likely use — e.g., Salesforce, Slack, etc.]?
>
We built native integrations with [relevant tools] specifically for [their use case]. [Customer] went live in under a week and saw [outcome].
>
Worth a short conversation, or would a technical overview be more useful?
Step 4: Signal Stacking for Maximum Impact
The power combinations:
Measuring Success
| Metric | Target | Benchmark |
|---|---|---|
| Company identification rate | 20-30% of total traffic | varies by tool |
| ICP match rate among identified | 15-25% | depends on traffic quality |
| Reply rate (Tier 1 signals) | 12-18% | vs 3-5% cold |
| Meeting conversion from identified visitors | 3-5% of identified ICP companies | vs <1% untracked |
| Pipeline from website signals | 15-25% of total pipeline | for signal-mature teams |
Frequently Asked Questions
Related Signal Playbooks
This playbook is part of the Signal-Based Prospecting series. Related playbooks: