HeyReach doesn't identify a single website visitor. It has no reverse-IP lookup, no identity graph, no fingerprinting of its own. Every "buying intent" event that fires a HeyReach LinkedIn campaign is actually coming from a bolted-on third party, almost always RB2B, sometimes Trigify, and HeyReach is purely the execution layer that sends the connection request after that other tool decides who counts. That distinction matters more than it looks, because your LinkedIn outbound ends up only as complete as whichever single identification vendor you plugged in upstream.

What HeyReach actually does (and doesn't do)

HeyReach is a LinkedIn automation platform: it manages multiple LinkedIn seats, rotates senders to stay under detection thresholds, and runs connection-request and messaging sequences at a scale a single rep's account can't sustain safely. That's a real, useful job. It is not website visitor identification. HeyReach's own integration documentation for RB2B spells out the division of labor plainly: RB2B watches your site, flags a "real buying intent" event, and HeyReach receives that flag and fires a campaign. Trigify plays the same upstream role for teams routing signals through it instead. Either way, HeyReach never resolves a session to a person, the same structural gap we found when we looked at how Outreach.io's own visit signals depend entirely on ZoomInfo. It waits for someone else to hand it a name, then does what it's genuinely good at: scaling the outreach safely.

Why one upstream source becomes your whole coverage ceiling

If a HeyReach campaign only fires because RB2B or Trigify told it to, your entire LinkedIn outbound motion inherits that one vendor's coverage, geography, and blind spots wholesale. RB2B's own knowledge base states a person-level identification rate of roughly 40 to 45% of qualified US traffic, with another 30 to 35% resolving to company-level only, for a combined 70 to 80% of US-based traffic identified at some level. Two things fall out of that. First, person-level, the only kind that can trigger a LinkedIn connection request in the first place, covers well under half of even the traffic RB2B calls qualified. Second, RB2B's own documentation scopes person-level matching to US visitors, so if your ICP includes UK, EU, ANZ, or APAC accounts, that traffic can't reach a HeyReach campaign through this path, no matter how hot the account looks in your analytics dashboard.

None of that is a knock on RB2B specifically (see our full breakdown of how identification approaches compare if you're evaluating one against the other). Every identification vendor has a ceiling and a geography, including us: person-level identification typically resolves 62%* of engaged US sessions to a name, verified work email, and title, working from an identity graph built off a consent-based publisher network, and account-level identification resolves 93%* of engaged sessions to a company. For more on when each match type is actually useful, see our breakdown of person-level versus company-level identification. The problem with the HeyReach setup isn't any single vendor's number. It's architectural. HeyReach has exactly one identification input wired to it, so whatever that input misses simply never happens. There's no second source to catch the visitor the first tool didn't resolve, no waterfall, no fallback path. A visitor either clears one vendor's bar or your LinkedIn sequence never fires for them, and because nothing else in your stack is watching, you have no way of knowing what you lost.

The gap is worse than "some visitors get missed"

There's a structural detail that makes this tighter than it first appears. HeyReach's own campaign API only accepts a contact record, never a company or account record, because you can't send a LinkedIn connection request to a company. That means a HeyReach campaign can only ever be fed by a person-level match. It's the same constraint we build against on our own integration: pushing a contact into a HeyReach campaign requires an actual contact ID, full stop, there's no company-level path into that output. So even generously assuming a single-source setup nails its stated person-level rate, everything that resolves at company-level only, which is usually the larger bucket, evaporates before it ever reaches your LinkedIn queue. You paid for the traffic. You know a real account was there. It just never became a touch.

What feeding HeyReach should look like instead

The fix isn't dropping HeyReach, it's still the right tool for scaled, compliant LinkedIn sending. The fix is not trusting one vendor to be your only eyes on the site. Rank your current setup honestly:

🔴 Single vendor, no waterfall, US-only coverage - you're capped near 40 to 45% person-level of US traffic and blind everywhere else. Assume most international ICP visits and most non-pricing-page intent never reach a rep.
🟠 Single vendor plus manual company-level follow-up - better, but someone has to notice the company-level match, go find the right person on LinkedIn by hand, and start the sequence manually. It works until volume goes up and it quietly stops happening.
🟡 Waterfall identification feeding HeyReach directly - a person-level match from any qualifying source pushes straight into a HeyReach campaign through the native integration, no manual step, no vendor-specific geography cap.
🟢 Waterfall identification with a Plays layer routing by signal strength - pricing or demo-page visits from a named account trigger an immediate one-off LinkedIn connection request outside the campaign queue, while broader engaged traffic still flows into the standard HeyReach sequence. Speed matches signal strength instead of every visitor waiting in the same line. This is the same tiered-response logic we laid out in the LinkedIn play, applied specifically to a HeyReach queue.

A play you can build this week

You don't need to rip out your current stack to close this gap. Three moves, in order:

1. Pull your last 30 days of engaged sessions and check what share resolved to a company only versus an actual person. If company-level dwarfs person-level, and for most single-source setups it does, that's your leak, not your LinkedIn copy or your connection-note personalization.
2. Route validated, person-level matches into your HeyReach campaign through the native integration so every qualifying contact enters the queue automatically instead of depending on someone noticing a company-level alert.
3. For your highest-intent pages, pricing, demo request, comparison pages, set a same-day LinkedIn connection request outside the standard campaign cadence. A visitor who hit your pricing page an hour ago and gets a request tomorrow in the regular queue has already cooled off.

Do this and HeyReach keeps doing what it's actually built for, safe, scaled LinkedIn sending, while the identification layer feeding it stops being the single point of failure for your entire LinkedIn motion. If LinkedIn is one piece of a broader multi-channel push, our warm outbound playbook covers how to sequence it alongside email and Slack alerts without duplicating touches.

FAQ

Does HeyReach have its own website visitor identification?

No. HeyReach is a LinkedIn outreach and automation platform. It relies on third-party tools, most commonly RB2B or Trigify, to detect and identify website visitors, then triggers campaigns based on the signal those tools send it.

What's the difference between RB2B and a waterfall identification approach?

RB2B is a single identification vendor with a published match rate and US-only person-level coverage. A waterfall approach checks multiple identity sources for each session, which typically raises both person-level and geographic coverage instead of capping every visitor at one vendor's ceiling.

Can company-level identified visitors still be reached through HeyReach?

Not automatically. HeyReach's campaign API requires a contact record to send a connection request, so a company-level-only match can't enter a HeyReach campaign on its own. It needs either a person-level match from your identification source or a manual step to find the right individual first.

Is it worth replacing HeyReach with a different LinkedIn tool?

Usually not. The gap here isn't HeyReach's sending capability, it's what's feeding it. Most teams get more value from strengthening the identification layer upstream than from switching LinkedIn automation platforms.

How fast should a LinkedIn touch follow a high-intent page visit?

Same day, ideally within a few hours for pricing or demo-request pages. Acceptance and response rates drop the longer a request sits between the visit and the send.

Ready to see it running on your own traffic? Book a Knock2 demo and we'll show you what your site's engaged sessions actually resolve to, person-level and company-level, before you decide what feeds your LinkedIn queue.

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