HubSpot Breeze Intelligence identifies companies visiting your site, not the people on them. It runs on the same reverse-IP-to-company matching that powered Clearbit before HubSpot acquired it in December 2023, so it can tell you "Acme Corp visited your pricing page" but it cannot reliably tell you which named person at Acme did. Reported match rates against real B2B traffic land in the 15-30% range, well short of what a dedicated identification tool can do, and that gap gets wider the more remote, mobile, or VPN-heavy your visitor mix is.

If you're a HubSpot customer wondering whether Breeze Intelligence makes a separate website visitor identification tool redundant, the honest answer is: it depends on what you're trying to do with the data, and for most outbound-driven teams, no.

What Breeze Intelligence Actually Is

Breeze Intelligence is HubSpot's bundled enrichment and identification layer, built on the Clearbit acquisition. When HubSpot folded Clearbit's dataset into its own product line, the underlying identification mechanism didn't change, only the packaging did. That matters because Clearbit's reverse-IP approach was never built to identify individuals; it was built to identify the company behind a business IP address, then enrich records you already had in your CRM.

Inside HubSpot, Breeze Intelligence shows up in two places: form enrichment (auto-filling company fields when a known lead submits a form) and visitor identification (surfacing which companies hit your site, even anonymously). The form enrichment side works well because it's enriching a record you already captured. The anonymous visitor side is where the gap between marketing copy and reality opens up.

How Breeze Intelligence Identifies Visitors

The mechanism is reverse-IP lookup: Breeze checks the IP address behind a page view against a database of known business IP ranges and returns the company that owns that range, if it's in the database. That's a company-level match, not a person-level one. There is no name, no email, no title attached to that visitor unless they've already filled out a form on your site.

This is a fundamentally different approach from an identity graph built on a consent-based publisher network, which is how Knock2 and other dedicated identification tools resolve person-level matches (name, email, title) alongside company-level ones. Reverse-IP matching can only ever answer "what company is this," never "who specifically." We wrote up the mechanics of that identity-graph approach in more depth in Build vs. Buy: Should Your GTM Team Build Its Own Website Visitor Identification Tool? if you want the fuller technical picture.

Why the Match Rate Is Lower Than You'd Think

Reverse-IP matching has three structural weaknesses that a pure company-database lookup can't get around:

• Remote and hybrid work. A visitor on home broadband or a coffee shop's WiFi doesn't resolve to their employer's IP range at all. Breeze simply won't see a company match for that session.
• Mobile carrier IPs. Cellular traffic routes through carrier IP blocks, not corporate ones, so mobile visits are close to unmatchable with this method.
• VPNs and cloud egress. Corporate VPNs increasingly exit through cloud providers (AWS, Azure) rather than a company's own registered IP block, which breaks the reverse-IP lookup entirely.

None of this is a Breeze-specific flaw. It's the ceiling of reverse-IP matching as a category, which is why community-reported match rates for Breeze and its Clearbit predecessor have consistently landed lower than the headline numbers in HubSpot's own marketing. A tool that layers in an identity graph and multiple enrichment passes can clear that ceiling; a single reverse-IP lookup structurally cannot.

What Breeze Intelligence Can't Do

To be specific about the gap rather than just gesture at it, Breeze Intelligence cannot:

• Identify the individual person behind an anonymous visit, only the company (when the IP resolves at all).
• Reliably match remote workers, mobile visitors, or VPN traffic to a company.
• Surface a buying committee, that is, the specific title-matched people at a visiting company worth reaching out to.
• Route a "hot" anonymous visit to a rep in real time based on person-level intent, since there's no person to route.

If your motion depends on any of those, form-fill enrichment alone won't get you there.

When Breeze Alone Is Actually Enough

This isn't a universal "upgrade now" pitch. Whether Breeze's company-level signal is sufficient depends heavily on your motion, deal size, and how much of your pipeline starts from cold anonymous traffic versus known accounts:

• 🔴 High-volume PLG or self-serve motion - low ACV, high anonymous traffic volume, SDR team needs named leads to work, not just company logos. Breeze alone leaves most of the pipeline invisible.
• 🟠 Mixed inbound/outbound mid-market - reps need to know who specifically to call, not just which accounts are browsing. Company-level alone creates guesswork on top of every alert.
• 🟡 Smaller team, longer sales cycle - reps can afford to manually research the 1-2 named people at a flagged account each week. Breeze's account-level signal plus manual lookup can bridge the gap for a while.
• 🟢 Small daily visitor volume, mostly known accounts - if most visits are already-open deals or existing customers, company-level confirmation is often all you need.
• ⚪ Pure enterprise ABM with a fixed named-account list - reps already know the individuals they're targeting; visitor ID is a confirmation signal, not a discovery tool. Breeze's coverage gaps matter less here.

One pattern we hear consistently from teams evaluating identification tools: even a bare company-level hit is worth acting on when the account fits your ICP. If someone from a target account is on your site, that's a real signal even without a named contact, and it's worth a note to two or three people at that company rather than waiting for a perfect person-level match. The gap is that Breeze can only ever give you that first half of the picture.

How to Test Your Real Match Rate

Don't take any vendor's headline match-rate number, including HubSpot's, at face value. The methodology for verifying it yourself is the same one we laid out for RB2B in Why No Two "RB2B Match Rate" Numbers Ever Agree (And How to Test Yours): pull a week of raw session volume from your analytics tool, then compare it against how many of those sessions Breeze actually returned a company for. Segment by traffic source and device type before you draw conclusions. Paid social and mobile-heavy traffic will show a materially worse match rate than direct traffic from desktop users on corporate networks, and averaging across all of it will hide that gap.

Running Breeze and a Dedicated Tool Together

The two aren't mutually exclusive, and ripping out Breeze to replace it isn't usually the right call since it's already enriching your form-fills and native to your CRM. The more common pattern among HubSpot customers we work with is running both: Breeze continues to enrich known contacts and forms, while a dedicated identification tool with an identity-graph approach covers the anonymous, remote, and mobile traffic Breeze structurally can't see, then pushes the person-level matches straight into HubSpot as contacts and companies. That's the same native-integration pattern we cover for building outbound workflows once you have those contacts in hand, in Turn Anonymous Website Traffic Into HubSpot Pipeline.

Knock2 is built around this stacking model rather than a rip-and-replace pitch: person-level identification (name, email, title) for US traffic runs at roughly 62%* against engaged sessions, and account/company-level identification runs at roughly 93%*, both well above what reverse-IP matching alone can reach, and both sync natively into HubSpot alongside whatever Breeze is already doing.

*Identification rates measured against engaged sessions (any visit lasting 10 seconds or longer, or including 2 or more pageviews). Results may vary by traffic profile, geography, and industry.

For the broader question of what a dedicated tool replaces in your stack versus what it doesn't, see The GTM Stack Cut List: What Website Visitor ID Actually Replaces (and What It Can't), and for a full buy-vs-build framework specific to visitor identification, see The GTM Stack for Website Visitor Identification: What to Buy, Build, and Skip in 2026.

If you want to see what person-level identification looks like layered on top of what you're already getting from HubSpot, explore how Knock2's workflows connect directly into HubSpot.

FAQ

Does HubSpot Breeze Intelligence identify individual website visitors?

No. Breeze Intelligence matches anonymous visitors to a company via reverse-IP lookup. It does not identify the specific person browsing unless that person has already submitted a form on your site.

What is HubSpot Breeze Intelligence's match rate?

Community-reported match rates for Breeze Intelligence and its Clearbit-derived matching typically fall in the 15-30% range of B2B site traffic, lower for traffic that's heavy on mobile, remote, or VPN sessions. Test your own rate rather than relying on a marketing figure, since it varies significantly by traffic mix.

Is Breeze Intelligence the same as Clearbit?

Breeze Intelligence is built on the technology HubSpot acquired when it purchased Clearbit in December 2023. The underlying reverse-IP matching mechanism is the same; HubSpot rebranded and bundled it into its own product line.

Can I use Breeze Intelligence and a dedicated visitor identification tool together?

Yes, and for most outbound-driven teams this is the more practical setup than replacing Breeze outright. Breeze continues enriching known contacts and forms while a dedicated tool covers the anonymous, remote, and mobile traffic reverse-IP matching structurally misses, then syncs person-level matches into HubSpot.

How do I check my own Breeze Intelligence match rate instead of trusting the marketing number?

Pull a week of session volume from your analytics tool, compare it to how many sessions Breeze returned a company match for, and segment by traffic source and device type before drawing conclusions, since paid social and mobile traffic will show materially worse match rates than direct desktop traffic.