Does Warmly Identify Website Visitors? The Real Scope

Warmly identifies website visitors at two separate levels: company-level (which account is on your site) and person-level (which named individual, with contact details, is on your site), and the two levels come with very different reliability. Company-level identification is the mature layer most waterfall-based tools get right. Person-level identification, the layer sales teams actually want for one-to-one outbound, is where match rates swing hardest and where buyers get burned by a headline number their own traffic never reproduces.

If you're evaluating Warmly, or any identification tool built on stacked third-party data, the real question isn't "does it identify visitors." It's "at what level, how consistently, and what does my specific traffic actually convert to."

Company-Level vs. Person-Level: What Warmly Actually Delivers

Warmly, like most tools built on a data waterfall, runs visitor traffic through a stack of third-party providers and reconciles the results rather than relying on a single proprietary dataset. Publicly, the company describes routing traffic through 20-plus data providers and only surfacing a person-level match when multiple providers agree, a consensus model rather than a single-source lookup. That's a reasonable design choice, and it should cut down on false positives compared to trusting one provider's guess. It also means the two levels of identification behave very differently in practice.

• 🔴 Company-level identification - highest confidence, works on the large majority of qualifying business traffic. This is the layer most vendors, Warmly included, get right most of the time.
• 🟠 Person-level identification, US business traffic - meaningfully lower confidence than company-level. Publicly reported ranges for waterfall-stacked tools commonly land in the teens to low twenties as a percentage of engaged sessions, and vary a lot by industry and traffic source.
• 🟡 Person-level identification, mixed or international traffic - drops further. Waterfall data providers are built primarily on US B2B data, so traffic from outside the US, or a mix of B2B and B2C visitors, degrades the person-level number fastest.
• ⚪ Anonymous, unmatched traffic - the rest. Every identification vendor, Warmly and Knock2 included, has a real unmatched tail. Anyone claiming they identify 100% of visitors isn't describing a real product.

The honest takeaway: don't shop on a single "match rate" headline. Ask which level, company or person, the number describes, and ask for it against a traffic profile that looks like yours, not a best-case account. We broke down the fuller framework in why company-level and person-level identification aren't the same product decision.

How the Waterfall Model Compares to an Identity Graph

Structurally, there are two dominant approaches to visitor identification on the market today. A waterfall model, which Warmly and several other tools use, runs a visitor's available signals through multiple third-party data providers in sequence or parallel, then picks the best or most-agreed-upon answer. It's a reasonable way to increase coverage without owning a single proprietary dataset, but match quality is capped by whatever the underlying providers actually know, and it can shift week to week as those providers' own data changes.

Knock2 takes a different approach: we match visitors against an identity graph built from a consent-based publisher network, rather than stacking third-party providers after the fact. That's a structural difference, not just a marketing distinction, and it's part of why our published benchmarks hold up consistently across traffic profiles rather than swinging with whichever providers a waterfall happens to hit that week: 93%* account-level identification and 62%* person-level identification (name, email, title) for US traffic, both measured against engaged sessions.

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

Why No Two Warmly Match-Rate Numbers Ever Agree

If you've talked to more than one vendor rep, or run more than one pilot, you've probably noticed: nobody's match-rate number matches anybody else's, sometimes not even two reps at the same company. That's usually not dishonesty, it's a measurement problem. "Match rate" can mean matched-against-all-traffic, matched-against-engaged-sessions, matched-against-US-only-traffic, or matched-against-a-cherry-picked-week, and each denominator produces a wildly different headline number. We published a full methodology for pressure-testing any vendor's stated number, including our own, in how to verify a vendor's match rate claim on your own traffic. The short version, adapted for Warmly specifically, is below.

A 20-Minute Self-Test to Verify Warmly's Match Rate on Your Own Traffic

1. Pull last week's engaged sessions from Google Analytics (10+ seconds or 2+ pageviews, the standard "real visit" definition most vendors use as their own denominator).
2. Export Warmly's identified-visitor log for the same window.
3. Split the export into company-level-only matches and person-level (named contact) matches. Most dashboards don't do this split for you by default, so do it manually or ask your rep to pull it broken out.
4. Divide each count by your engaged-session total, not by total pageviews or total traffic. That's the number a vendor should be quoting, and it's usually meaningfully lower than the number in the deck.
5. Spot-check 15 to 20 of the person-level matches by hand. Are these real named individuals with a title and a business email, or thin records with a name and nothing else your reps could actually act on?

Run the same test against any tool you're evaluating, ours included. A vendor that won't help you build this export, or that gets cagey about denominators, is telling you something.

What Each Pricing Tier Actually Unlocks

Waterfall-based tools frequently gate identification depth behind plan tier, and Warmly is no exception. Before you commit to a plan based on a sales demo, confirm in writing which of the following your specific tier includes:

• 🔴 Company-level identification and basic account alerts - typically included at entry tiers across most vendors in this category.
• 🟠 Person-level (named contact) identification - frequently a mid-tier or add-on capability, not entry-level, across waterfall tools generally.
• 🟡 Workflow automation (routing, sequencing, CRM sync) - usually gated separately from identification depth itself, and worth pricing out independently since it can double the effective cost.
• 🟢 Seat and contact-volume caps - ask what happens to pricing once your matched-contact volume grows past the tier's included cap. This is where "identification" tools tend to get expensive fast.

Where This Leaves You

Warmly does identify website visitors at both the company and person level, and its consensus-based waterfall approach is a defensible design choice. What it can't do, and what no waterfall tool can do, is guarantee a specific match rate on your specific traffic before you test it. This post joins our existing lineup of vendor-specific breakdowns, including whether Apollo identifies website visitors and whether HubSpot's Breeze Intelligence does. The teams that get the most value out of any identification tool, Warmly or otherwise, are the ones that run the 20-minute self-test above before they buy, not after.

If you want to see what an identity-graph approach looks like against your own traffic, with company-level and person-level numbers broken out against the same engaged-session denominator used above, you can see how Knock2's identification works or check current pricing.

FAQ

Does Warmly identify anonymous website visitors?

Yes, at the company level for most qualifying business traffic, and at the person level for a smaller subset, using a multi-provider waterfall model with consensus matching. Actual match rates depend heavily on your traffic's geography and industry mix.

What's the difference between Warmly's company-level and person-level identification?

Company-level identification tells you which account is on your site. Person-level identification tells you which named individual, with a title and contact details, is on your site. Company-level match rates are consistently higher across the industry; person-level rates are lower and more variable.

How accurate is Warmly's match rate?

Match-rate accuracy depends entirely on the denominator used (all traffic vs. engaged sessions vs. US-only traffic) and on your specific traffic profile. Rather than trust any vendor's stated number, including ours, run the self-test in this post against your own last week of traffic.

Is Warmly a good alternative to a dedicated identity-graph tool like Knock2?

It depends on what you need. If company-level account alerts are enough, most waterfall tools, Warmly included, will get you there. If you need consistent, high-confidence person-level identification for one-to-one outbound, compare Warmly's person-level match rate against an identity-graph approach on your own traffic before deciding.

Does Warmly work for international or non-US traffic?

Company-level identification generally holds up better internationally than person-level identification, since most waterfall data providers are built primarily on US business data. If a meaningful share of your traffic is outside the US, test that segment specifically rather than relying on a blended average.