Close CRM has no native website visitor identification feature at all, not even the weak, company-only version that Pipedrive or HubSpot ship out of the box. If a visitor doesn't fill out a form or reply to a cold email, Close has zero record that they ever existed. For a CRM built specifically for high-velocity outbound teams, that's a real gap: reps running hundreds of manual touches a week get no signal on which of those prospects are actually reading the site back.

That's the short version. The longer version is that Close was built to be the fastest CRM for people making calls, sending emails, and texting leads at volume, not for capturing inbound signal. It has no visitor-tracking add-on to switch on and no company-watchlist sidebar to check. If you want to know who's reading your pricing page before you dial them, you have to build that layer yourself. Here's what Close does and doesn't do out of the box, why the gap hurts more for Close's typical user than it does for a slower-motion CRM, and how to close it without replacing your CRM.

Does Close CRM Track Website Visitors at All?

No. Close's product surface is Leads, Contacts, and Opportunities, worked through Smart Views, the Power Dialer and Predictive Dialer, and built-in calling, email, and SMS sequences. Every one of those is oriented around outreach a rep already knows to make. There's no module anywhere in Close that watches your website and tells you who showed up.

Compare that to what other CRMs offer natively:

• Pipedrive ships a Leadfeeder-powered Web Visitors add-on that resolves visiting IPs to company names (no person, no email).
• HubSpot has Breeze Intelligence, built on the former Clearbit, doing similar company-level resolution tied to contact records.
• Close has neither. It has a full REST API and a native Zapier integration, so it's built to receive data from other tools, but nothing generates that visitor data on its own.

That's not a knock on Close. It's a genuinely fast CRM for the job it was designed to do. It just means the "who's on our site right now" problem is entirely yours to solve, from a blank slate, if you want it solved at all.

Why the Gap Hurts Close's Users More Than It Hurts Everyone Else

We see this pattern constantly with early-stage and lean-team customers evaluating Knock2: the sales motion is close to 100% outbound, there's no separate marketing function generating inbound leads, and Close is the system of record for every call, email, and text a rep sends. In that setup, a prospect who's visited the pricing page five times in two weeks looks identical in Close to someone who's never heard of the company, because nothing in the stack is watching the website at all. The rep dials both leads cold, in the same order, with the same script, at the same priority.

That's a worse version of the problem Pipedrive or HubSpot users have. Their native features at least surface a company name to look at, even if it's not a person. Close users start from nothing. Every prospect reading your docs, checking pricing, or coming back a third time is invisible unless they raise their hand, which most buyers doing real evaluation work simply won't do before they're ready to talk.

How to Add Person-Level Identification on Top of Close

The fix isn't replacing Close. Close is good at what it does, running fast, high-volume outbound. The fix is putting a person-level identification layer in front of it, then routing only the matches worth a rep's time in as real Close records. Knock2 does this by matching visitors against an identity graph built from a consent-based publisher network, resolving a visit to a named contact (name, email, title) rather than a company name with no one to call.

Two identification rates matter here, both measured against engaged sessions (a visit lasting 10+ seconds or with 2+ pageviews, the standard Google Analytics definition):

• 93%* of engaged sessions resolve to an account or company
• 62%* of engaged US sessions resolve to a named person (name, email, title)

*Identification rates measured against engaged sessions. Results may vary by traffic profile, geography, and industry.

For a Close user specifically, the person-level number is the one that matters. A company name with no contact record isn't a workable lead in a CRM built around dialing and texting named people. Company-level data has nowhere to go in Close's workflow. A named contact with a title does.

How Match Quality Actually Ranks, Tier by Tier

Not every identified visitor is worth a rep's dial. Here's how the tiers break down before anything gets routed into Close:

• 🔴 Named person, verified title, engaged on a high-intent page - create the Lead and drop it straight into the assigned rep's dialer queue, no review needed
• 🟠 Named person, verified title, low-intent page - create the Lead, route to a nurture sequence instead of a live call task
• 🟡 Company matched, no person, high engagement - log as account intelligence, worth a manual look, not an automatic Lead
• 🟢 Company matched, no person, low engagement - log for reporting only, don't create a record
• ⚪ No confident match either level - discard, don't force a low-confidence entry into a CRM built for high-trust, high-volume dialing

Because Close has no native tracking at all, it can't even produce the 🟡 and 🟢 tiers on its own the way Pipedrive can. Every tier here has to come from the identification layer sitting in front of it.

Routing Identified Contacts Into Close: The Actual Workflow

Close doesn't have a one-click visitor-tracking app to install, so this runs through the API or Zapier rather than a native toggle. In practice:

1. Identify and score the visit first. Person-level match, page-intent weighting, and an ICP fit check all happen before anything touches Close.
2. Filter before you create a Lead. Only 🔴 and 🟠 tier matches should generate a new Close record. Pushing every company-level hit into Close just recreates a noisy list nobody works, the exact problem Close's speed-first design is meant to avoid.
3. Push via the Close API or Zapier. A matched, scored contact creates or updates a Lead, attaches a Contact with the right name, email, and title, and can log the triggering page visit as an Activity, using Close's standard objects rather than a bolt-on integration.
4. Drop it into an existing Smart View or dialer queue. Close's whole design center is speed, so a routed match is most useful the moment it lands in the same Power Dialer queue a rep already works, not in a separate visitor list they have to remember to check.
5. Attach a Task with a response-time SLA. A routed Lead with no follow-up commitment just becomes a new, quieter version of the ignored list Close was supposed to prevent.
6. Score Opportunities against real people, not page views. A deal tied to a named contact and their engagement history is something you can report on later. A deal loosely tied to "a company that visited the site" isn't.

Frequently Asked Questions

Does Close CRM have a website visitor tracking feature?

No. Unlike Pipedrive (Leadfeeder-powered Web Visitors) or HubSpot (Breeze Intelligence), Close has no native website visitor identification or tracking feature of any kind, at the company level or the person level.

How do I get website visitor data into Close CRM?

Through Close's REST API or its native Zapier integration. A person-level identification tool resolves anonymous traffic to named contacts, scores the match, and pushes qualified matches into Close as Leads and Contacts, since Close has no way to generate that data itself.

Is Close's Zapier integration enough to route identified visitors automatically?

It's the delivery mechanism, not the identification layer. Zapier can move a matched, scored contact into Close reliably, but something upstream still has to do the actual person-level resolution and filtering first. Without that filter, Zapier will just as happily flood Close with low-confidence, company-only matches.

Should every identified company go into Close as a Lead?

No. Unfiltered company-level matches create the exact low-signal list Close's speed-first workflow can't absorb. Filter to person-level matches with real intent (the 🔴 and 🟠 tiers above) before a record hits a rep's queue.

Does this replace any part of Close, or run alongside it?

Alongside it. The identification layer sits in front of Close and only creates or updates records for matches worth a rep's time. Close stays exactly what it is, the fastest way to call, email, and text the leads worth reaching.

Close was built to make reps fast, not to tell them who's already reading the site. If your team is running outbound blind because Close has nothing watching your traffic, the fix is a person-level identification layer in front of it, not a new CRM. See how Knock2's identification layer works, or check the routing automation that gets matched contacts into a CRM on an SLA. Related builds: the HubSpot version, the Pipedrive version, and the Salesforce version of this build. If Close is your CRM but pipeline still isn't showing up, see why website visitor identification isn't converting to pipeline.

See Knock2 identify your Close-bound traffic and route real, named contacts, not blind cold calls, into your pipeline.