Yes, partially. Instantly shipped a native Website Visitors module in 2026: a pixel you install on your site that tries to resolve anonymous traffic into a company, and for a share of sessions, a named contact. It's US-traffic only, sold as a paid add-on, and genuinely useful as a top-up signal inside Instantly itself. What it is not is a replacement for a dedicated identification layer. An independent 14-day test found it resolving 22% to 35% of visitors to a real contact, a wide range that lands well short of what purpose-built identity-graph platforms publish. Here's what the module actually does, what the data says, and how to decide whether it's enough on its own.

What Instantly's Website Visitors Module Actually Does

The mechanism is a JavaScript pixel, the same category of tool as RB2B, installed on your site to catch anonymous sessions as they happen. Instantly pairs the pixel with a feature it calls SuperSearch, which layers on identity and intent enrichment once a session is flagged. The pricing model is credit-based: you're charged only when a session resolves to a business email or LinkedIn profile, while unmatched sessions still surface a company-only resolution at no extra cost. Reported pricing puts the entry tier at roughly $75 to $80 a month on an annual plan, on top of whatever you're already paying for sending.

That's a meaningfully different product than what Smartlead, Lemlist, Apollo, and most other sequencers offer today, which is nothing native at all. Credit where it's due: Instantly built something real, and for a team that lives inside Instantly all day, a same-platform signal that needs no extra integration is a legitimate convenience.

What the Match Rate Data Actually Shows

The number that matters is the one from an independent 14-day test, not a vendor's own marketing page: a 22% to 35% visitor-to-contact match rate. That's a real range, but it's also a wide one, and the width is the tell. We've written before about how to vet a website visitor ID vendor's accuracy claims, and the same discipline applies here: a match rate is not a fixed property of a tool, it's a property of the tool applied to a specific slice of traffic, measured against a specific denominator. The same logic played out almost identically when we tested why RB2B's published match rates never agree. Neither vendor is being dishonest. Both numbers move with whose traffic you're measuring.

For context, Knock2 matches visitors against an identity graph built from a consent-based publisher network, rather than a single platform's pixel and login state. Measured the same way, person-level identified visitors divided by engaged sessions, Knock2 publishes 93%* company-level and 62%* person-level identification for US traffic. *Identification rates measured against engaged sessions. Results may vary by traffic profile, geography, and industry. That gap between a 22-35% range and a 62% published number is exactly why "does Instantly identify website visitors" and "should Instantly's module be your only identification layer" are two different questions with two different answers.

Where the Gap Shows Up: A Module Scoped to One Channel

Instantly's Website Visitors module was built by a sequencer company to fill its own campaigns, and it behaves that way. It resolves a visitor, then hands you a name to add to an Instantly sequence. What it doesn't do: route a contact to Salesforce or HubSpot automatically, check whether that person is already mid-sequence somewhere else in your stack, map the rest of the buying committee at that account, or fire a Slack alert the moment a target account lands on your pricing page. It's a lead source for one tool, not a signal layer for your GTM stack.

That scoping bites hardest for teams running outbound at real volume, particularly marketing and lead-gen agencies managing multiple client accounts through the same sequencer. An agency juggling five client campaigns in Instantly doesn't just need to know a visitor showed up. It needs that visitor attributed to the right client, deduplicated against whatever else is already running, and routed without a human re-keying it between tools. A module that only feeds one campaign inside one platform can't do that on its own, no matter how good its match rate gets.

Instantly's Module vs. a Dedicated Identification Layer

Once you know your real match rate, here's what should carry the most weight in deciding whether the native module is enough or whether you need identification sitting upstream of every tool, not just one:

• 🔴 Very High - Cross-channel routing: does identification feed every destination in your stack (CRM, Slack, multiple sequencers), or only the one platform it's bundled with.
• 🔴 Very High - Denominator transparency: is the published match rate measured against the same engaged-session definition you'd use to check it yourself.
• 🟠 High - Person vs. company resolution: does a "match" mean a verified name and email, or just a company name with no individual to contact.
• 🟡 Medium - Geographic coverage: US-only resolution versus broader coverage, if any share of your buyers sit outside the US.
• 🟢 Low-Medium - Workflow depth: does a match trigger enrichment and buying-committee mapping, or stop at a single contact record.
• ⚪ Low - Credit pricing: matters far less once you know your real match rate and what it feeds.

How to Test Instantly's Match Rate on Your Own Traffic This Week

Don't take the 22-35% range, or Knock2's 62%*, as your number. Run this instead:

• Install the pixel and let it run for 14 days without wiring it into any downstream automation yet.
• Pull your engaged-session count for that same window from Google Analytics (any visit of 10 seconds or more, or 2+ pageviews) and use it as the denominator, not raw pageviews.
• Divide resolved contacts by engaged sessions. That's your real match rate, not a published one.
• Segment the matches by traffic source. A pixel-based module typically performs unevenly across organic, paid, and direct traffic, and the aggregate number can hide a channel where it barely works at all.
• Decide from there: keep the module as a same-platform top-up, or put a dedicated identification layer upstream that feeds Instantly along with everything else instead of feeding only Instantly.

Where Knock2 Fits

The fix isn't necessarily replacing Instantly. Its sending infrastructure and the Website Visitors module both do a real job. The fix is deciding whether that job should be the only source of identified contacts reaching your team, or one input into a layer that sits above every channel you run.

Knock2's identification runs upstream of any sequencer, Instantly included, through Plays: standing automations that trigger the moment a person or account is identified, optionally enrich the contact and map the rest of the buying committee, then hand off to a destination. The Instantly output step takes two inputs, a contact ID and an Instantly campaign ID, the same contact-first pattern used across every native sequencer integration Knock2 supports. That means a visitor identified anywhere on your site, not just the pages where Instantly's pixel happens to fire, can land in the right Instantly campaign automatically, alongside Salesforce, HubSpot, or a Slack alert for the same event.

FAQ

Does Instantly identify website visitors?

Partially. Its Website Visitors module resolves some anonymous US traffic to a company, and a share of that to a named contact. It's scoped to feed Instantly's own campaigns, not to act as a company-wide identification layer.

What is Instantly's match rate for website visitor identification?

An independent 14-day test found a 22% to 35% visitor-to-contact match rate. Treat that as a starting range and test it on your own traffic before relying on it.

Is Instantly's Website Visitors module available outside the US?

Person-level resolution is US-traffic only. International sessions aren't covered at the same depth.

Can I use Instantly's Website Visitors module alongside Knock2?

Yes. Knock2 identifies and qualifies visitors across your full GTM stack, then can route qualified contacts straight into an Instantly campaign through a Play, so both the module and Instantly's sending infrastructure stay in use.

How does Knock2 measure its own match rate?

Knock2 publishes 93%* company-level and 62%* person-level identification for US traffic, both measured against engaged sessions. *Results may vary by traffic profile, geography, and industry.

A match rate is a property of a tool applied to your traffic, not a fixed spec you can copy off a pricing page. Instantly's Website Visitors module is a real feature with a real, if wide, published range behind it. Whether that range is enough depends entirely on how much of your pipeline you're willing to route through one channel's resolution. If your test shows you're leaving contacts unresolved outside Instantly, especially on channels the pixel doesn't reach, it's worth seeing how an identity-graph layer compares on your own traffic. Start a free trial and run the numbers yourself.