website-visitor-identification

name	website-visitor-identification
description	Design website visitor identification and deanonymization programs — company vs person-level ID, vendor selection (Clearbit/Breeze, RB2B, 6sense, etc.), privacy guardrails (GDPR/CCPA operational), Slack alert triage, and ICP routing to MQL or outbound triggers. Use when implementing visitor ID, reverse-IP reveal, intent data, or person-level LinkedIn visitor tracking. Triggers on: "visitor identification", "deanonymization", "website intent", "Clearbit Reveal", "RB2B", "who visited our website", "reverse IP", "WebSights", "Leadfeeder", "visitor ID privacy".
license	MIT
compatibility	Claude Code, Jesse, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose
metadata	{"version":"1.0.0","author":"LeadMagic","category":"inbound","tags":["inbound","visitor-id","intent","deanonymization","privacy","abm","clearbit","rb2b"],"related_skills":["inbound-triage","icp-scoring","1p-tagging-pixels","revops-tech-stack","gtm-spend-management","cold-email-strategy","lead-enrichment","campaign-governance","attribution"],"frameworks":["HubSpot Breeze Intelligence (Clearbit heritage) — Reveal & enrichment","Dharmesh Shah (HubSpot) — Inbound Attract + measurable intent","Chris Walker (Refine Labs) — Measurable demand vs dark social","Scott Brinker — MarTech consolidation before new intent vendors","Winning by Design — Bowtie acquisition stage instrumentation","SiriusDecisions Demand Waterfall — MQL definitions from intent"]}

Website Visitor Identification

Overview

Most B2B sites convert 2–3% of traffic to forms — the rest looks like dark traffic. Visitor identification (deanonymization) recovers company or person signals from anonymous sessions. The mistake: buying RB2B or 6sense before deciding identification level, running person-level ID on EU traffic without privacy review, or routing every alert to SDRs without an ICP filter.

This skill is the canonical home for visitor ID strategy: person vs business decision tree, vendor comparison (Clearbit/Breeze, RB2B, 6sense, Demandbase, ZoomInfo WebSights, Leadfeeder/Dealfront, Warmly, Koala, Factors.ai, Albacross), privacy operational checklist (not legal advice), and GTM workflows from website visit → MQL or guardrailed outbound trigger.

Frameworks Referenced

• HubSpot Breeze Intelligence (Clearbit heritage). Company Reveal on visit; form enrichment for person + firmographics in HubSpot-native stacks.
• Dharmesh Shah (HubSpot). Visitor ID instruments the Attract stage of the inbound flywheel — permission-based follow-up after self-directed research. references/dharmesh-shah-hubspot-inbound.md · Pattern 20 + 27.
• Chris Walker (Refine Labs). Visitor ID is the measurable counterpart to dark social — pair with content-marketing and attribution, not replace them. Pattern 26 + 20.
• Scott Brinker — MarTech consolidation. One company-ID owner + at most one person-ID vendor until utilization proves ROI (revops-tech-stack).
• Winning by Design Bowtie. Visitor ID instruments the acquisition stage.
• SiriusDecisions Demand Waterfall. Intent signals feed MQL definitions — coordinate with inbound-triage.

When to Use

• "Identify companies visiting our website"
• "Set up Clearbit Reveal / Breeze Intelligence"
• "RB2B vs Warmly vs Koala"
• "Person-level vs company-level visitor ID"
• "Website intent data program"
• "GDPR / CCPA for visitor deanonymization" (operational — not legal counsel)
• "Slack alerts for website visitors"
• "Route visitor intent to sales"

Prerequisites

• ICP defined (icp-scoring)
• CRM with account + contact model
• Consent management for EU traffic ()