“We have intent data.” “We have visitor identification.”
These two statements get thrown around in B2B like they mean the same thing. They don’t. And the confusion is costing teams real money - because they buy one tool thinking it does what the other does, then wonder why their pipeline didn’t move.
Intent data tells you who’s researching topics across the web. Visitor identification tells you who’s on YOUR website.
Different data sources. Different signals. Different use cases. And honestly? You probably need both. Here’s why the distinction matters and how to combine them for maximum impact.
Table of Contents
- What Is Intent Data?
- What Is Visitor Identification?
- Key Differences at a Glance
- Company-Level vs Person-Level: The Critical Distinction
- Why You Need Both (Not Either/Or)
- The Combined Signal Architecture
- How Leadpipe Does Both
- Provider Comparison Matrix
- Use Cases for Combined Data
- FAQ
What Is Intent Data?
Intent data is a set of signals indicating that a person or company is actively researching a topic. The research happens across the open web - publisher networks, review sites, content syndication platforms, industry forums - and gets aggregated into something your sales and marketing teams can act on.
Here’s a concrete example of what intent data looks like:
“Acme Corp is showing strong intent for ‘CRM software’ - intent score 82/100 - based on content consumption across 47 publisher sites over the past 14 days.”
The signal is powerful. Acme Corp isn’t just sitting there - someone at the company has been reading articles, downloading whitepapers, and visiting review sites like G2 and TrustRadius, all centered around CRM tools.
How Intent Data Gets Collected
The major intent data providers maintain partnerships with thousands of content publishers. When someone at Acme Corp reads an article about “best CRM for mid-market companies” on a publisher site, that consumption event gets logged, aggregated, and scored.
The typical sources include:
- B2B publisher networks (TechTarget, IDG, etc.)
- Review sites (G2, TrustRadius, Capterra)
- Content syndication platforms
- Bidstream data (ad exchange signals)
- Search behavior patterns
The big names in this space - Bombora, 6sense, G2, Demandbase - all work roughly this way. They aggregate consumption signals, tie them to companies using IP-to-company mapping, and deliver a score that says “this company is in-market.”
The catch? Most of this data is company-level only. You know Acme Corp is researching CRM tools. You don’t know if it’s the VP of Sales or the marketing intern.
What Is Visitor Identification?
Visitor identification is fundamentally different. Instead of tracking research behavior across the web, it identifies the specific people visiting your website.
Here’s what a visitor identification signal looks like:
“Jane Smith, VP of Revenue Operations at Acme Corp, visited your pricing page at 2:14 PM, spent 3 minutes and 22 seconds, and previously visited your integrations page twice last week.”
That’s not aggregated intent from publisher networks. That’s a real person, on your site, right now, looking at your pricing.
How Visitor Identification Works
A small JavaScript pixel sits on your website. When someone visits, the pixel collects browser and device signals and matches them against an identity graph - a database that maps those signals to real people.
The result is person-level data:
- Full name and job title
- Business email and phone number
- Company with firmographic details
- Pages visited, time on site, return visit history
- Real-time delivery via webhooks, CRM sync, or Slack alerts
The key providers in this space include Leadpipe, RB2B, and Warmly. Each has different match rates, data quality, and pricing.
97% of website visitors leave without filling out a form. Visitor identification captures a portion of that invisible traffic - typically 30-40% with Leadpipe - and turns anonymous sessions into named contacts your team can follow up with.
Key Differences at a Glance
Here’s where the confusion clears up:
| Dimension | Intent Data | Visitor Identification |
|---|---|---|
| What it tells you | Who’s researching topics | Who’s on YOUR site |
| Data source | Publisher networks, review sites | Your website pixel |
| Granularity | Usually company-level | Person-level |
| Timing | Aggregated over days/weeks | Real-time |
| Scope | Across the web | Your site only |
| Actionability | ”Someone at Acme is interested" | "Jane from Acme viewed pricing” |
| Best for | Targeting, ABM list building | Sales outreach, lead timing |
| Key providers | Bombora, G2, 6sense | Leadpipe, RB2B, Warmly |
Look at the “Actionability” row. That’s the one that matters most in practice.
Intent data gives you a company name and a topic. Visitor identification gives you a person, a page, and a timestamp. Both are useful. Neither is complete on its own.
Company-Level vs Person-Level: The Critical Distinction
This is the part most people get wrong.
Most intent data is company-level. Bombora tells you “Acme Corp is showing intent for CRM software.” That’s it. Acme has 2,000 employees. Good luck figuring out who to call.
Most visitor identification is person-level. Leadpipe tells you “Jane Smith, VP RevOps at Acme, visited your pricing page.” You know exactly who to reach out to and what they looked at.
But here’s where it gets interesting. The lines are starting to blur.
Leadpipe’s Orbit API delivers person-level intent data across 20,000+ topics. Not “Acme Corp is researching CRM.” Instead: “Jane Smith, VP of RevOps at Acme Corp, has been researching ‘CRM software,’ ‘Salesforce alternatives,’ and ‘revenue operations platforms’ - intent score 85/100.”
That’s the same person-level granularity you’d expect from visitor identification, applied to cross-web intent data. It changes the game because now you’re not choosing between knowing the person (visitor ID) and knowing their research behavior (intent). You get both.
The old trade-off: Pick company-level intent across the web OR person-level identity on your site.
The new reality: Person-level intent across the web AND person-level identity on your site, from a single platform.
Why You Need Both (Not Either/Or)
Let’s walk through what happens when you only have one signal.
Intent Data Without Visitor Identification
You know Acme Corp is researching “marketing automation tools.” Your SDR finds 12 people at Acme on LinkedIn with relevant titles. They pick the CMO, write a cold email, and hope for the best.
Meanwhile, Acme’s Director of Demand Gen - the actual buyer - visited your website yesterday, spent four minutes on your pricing page, and left. Nobody on your team knows.
The result: Your outreach goes to the wrong person while the right person slips away.
Visitor Identification Without Intent Data
Jane Smith from Acme visits your blog post about integrations. Great, you’ve identified her. Your SDR fires off an email about your integration capabilities.
But what they didn’t know is that Jane has been researching “marketing automation alternatives” and “HubSpot competitors” across 30 publisher sites for the past two weeks. She’s deep into an evaluation. The integrations page was just a surface-level check - what she actually cares about is how your platform compares to HubSpot on campaign automation.
The result: Your outreach is relevant but shallow. It doesn’t speak to what’s actually driving her research.
The Combined Signal
Now combine them:
“Jane Smith, Director of Demand Gen at Acme Corp, has been researching ‘HubSpot alternatives’ and ‘marketing automation platforms’ across the web for the past 14 days (intent score: 89/100). She visited your pricing page today for 3 minutes and 22 seconds and previously viewed your comparison page twice.”
Your SDR knows:
- Who to contact (Jane, not 12 guesses)
- What she cares about (HubSpot replacement, not general curiosity)
- When to reach out (right now - she just left your pricing page)
- How to personalize (reference the HubSpot comparison she’s running)
That’s the difference between a cold email and a conversation starter.
The Combined Signal Architecture
Here’s how the two data streams work together:
Intent Data (Leadpipe Orbit) Visitor ID (Leadpipe Pixel)
"Who's researching topics?" "Who's on your site?"
↓ ↓
┌─────────────────────────────────────────┐
│ COMBINED SIGNAL │
│ Person + Topic + Your Site Visit │
│ = Highest-intent lead possible │
└─────────────────────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ ACTION LAYER │
│ • AI SDR triggered with full context │
│ • CRM record enriched automatically │
│ • Slack alert to account owner │
│ • Lead score adjusted in real-time │
└─────────────────────────────────────────┘The architecture is simple. Two data streams converge on a single person record. Intent tells you they’re in-market. Visitor ID tells you they’re on your site. Together, they give you the highest-confidence sales signal available in B2B today.
And because both streams resolve to the person level (not just the company), you can route the lead directly to the right rep with all the context they need.
How Leadpipe Does Both
Most providers pick a lane. Bombora does intent. RB2B does visitor identification. Clearbit does enrichment. You end up stitching together three or four tools to build a complete picture.
Leadpipe is the only platform that combines person-level visitor identification and person-level intent data under one roof.
Visitor Identification (The Pixel)
- Match rate: 30-40%+ of anonymous traffic, depending on traffic quality
- Data returned: Full name, business email, personal email, phone, company, title, LinkedIn, pages visited, time on site
- Matching method: Deterministic (own identity graph - not reselling a third-party graph)
- Delivery: Real-time webhooks, API, native CRM integrations, Slack
- Setup: 2-5 minute JavaScript pixel install
Intent Data (Orbit API)
- Topics: 20,000+ across B2B and B2C categories
- Granularity: Person-level (name, email, title, company) - not just company-level
- Filters: ICP-based filtering by company size, industry, job title, seniority, location
- Freshness: Daily refresh
- Delivery: RESTful API with 18 endpoints
Why One Platform Matters
Having both in a single platform isn’t just convenient. It changes the data quality.
When Leadpipe identifies Jane Smith on your website AND sees her researching relevant topics across the web, those signals reinforce each other. The confidence score goes up. The context gets richer. The lead priority becomes unmistakable.
Compare that to manually cross-referencing a Bombora company-level intent report with an RB2B visitor identification feed, trying to match company names and guess which person the intent signal belongs to. It’s a mess.
One platform. One API. One billing relationship. One identity graph connecting everything.
Provider Comparison Matrix
Here’s how the major players stack up when you need both intent data and visitor identification:
| Provider | Visitor ID | Intent Data | Person-Level Intent | Combined | Pricing |
|---|---|---|---|---|---|
| Leadpipe | Yes | Yes (20K+ topics) | Yes | Yes | $147/mo+ |
| Bombora | No | Yes (12K+ topics) | No (company-level) | No | $25K+/yr |
| 6sense | No | Yes | No (company-level) | No | $25K+/yr |
| G2 | No | Yes (software only) | No (company-level) | No | Custom |
| RB2B | Yes | No | N/A | No | $99/mo |
| Warmly | Yes | Limited | No | Partial | $900/mo |
| Clearbit | No | Limited | No | No | $12K+/yr |
A few things jump out from this table.
Bombora and 6sense are the heavyweights in intent data, but they don’t do visitor identification at all. And their intent is company-level only. You’re paying $25K+ per year to learn that “Acme is interested” - then you still need another tool to figure out who at Acme is interested and whether they’re visiting your site.
RB2B does visitor identification at a low price point, but offers zero intent data. You’ll know who’s on your site but have no idea what they’re researching across the web.
Warmly attempts to combine both but doesn’t offer true person-level intent data, and their pricing starts at $900/month - six times Leadpipe’s entry point.
Leadpipe is the only provider that checks every box: visitor identification, intent data, person-level granularity on both, combined signals, and pricing that starts at $147/month for 500 identified visitors.
Use Cases for Combined Data
When you merge intent signals with visitor identification, entirely new workflows open up. Here are the ones driving the most revenue for teams using the combined stack.
1. AI SDR Targeting with Full Context
This is the big one. AI sales agents are only as good as the data you feed them. When you combine intent + visitor ID, your AI SDR gets the full picture:
- Intent data identifies in-market buyers researching your category
- Visitor ID catches them the moment they land on your site
- AI agent strikes with personalized outreach referencing both their research and their site behavior
The difference between “I noticed your company might be interested in our solution” and “I saw you’ve been evaluating [specific category] - and I noticed you spent time on our pricing page yesterday” is a 3-5x improvement in reply rates.
Read more: How to Choose a Data Provider for AI SDR
2. ABM Account Monitoring
Build your target account list using intent data - find every company researching topics relevant to your solution. Then monitor your website for visits from those accounts.
When someone from a target account shows up on your site, you know two things: the company is in-market (intent) and a specific person is engaged (visitor ID). That’s your trigger for the account owner to step in with a tailored message.
3. Inbound Lead Scoring
Not all form fills are equal. When a lead comes in through your website, enrich them with intent data to see if they’ve been researching your category across the web.
A demo request from someone who’s been researching “marketing automation alternatives” for three weeks is a completely different lead than a demo request from someone who stumbled onto your site from a random Google search. Your enrichment layer should reflect that difference.
4. Content Strategy Informed by Research Behavior
This one is underrated. Look at your identified visitors and check what topics they’re researching across the web. If you notice that 40% of your visitors are researching “AI-powered sales tools,” that’s a strong signal to create content around that topic.
Intent data turns your website analytics from “what pages are popular” into “what problems are our visitors trying to solve.”
5. Competitive Intelligence at the Contact Level
Most intent providers include competitor-related topics. If Jane Smith from Acme is researching “Salesforce alternatives” and also visiting your site, you know she’s in an active evaluation - and your competitor is in the mix.
That context changes how your rep positions the conversation. Instead of a generic pitch, they lead with differentiation.
FAQ
Is intent data the same as visitor identification?
No. Intent data tells you who’s researching topics across the web (publisher sites, review sites, content platforms). Visitor identification tells you who’s visiting your specific website. They’re complementary signals - intent data shows market-level interest, visitor identification shows direct engagement with your brand. Most teams get the best results when they use both together.
Can I get person-level intent data, or is it always company-level?
Most traditional providers (Bombora, 6sense, G2) deliver company-level intent only. You’ll know “Acme Corp is researching CRM tools” but not which person. Leadpipe’s Orbit API is one of the few sources that delivers person-level intent - the actual individual researching the topic, with their name, email, title, and contact info attached.
How accurate is visitor identification? Doesn’t it just guess?
Quality varies dramatically between providers. Leadpipe uses deterministic matching against its own identity graph, which means it’s matching on known data points rather than probabilistic modeling. Independent tests show 30-40%+ match rates, which is 2-3x higher than most competitors. The identified visitors include verified business email, full name, company, and title - not guesses.
Do I need separate tools for intent data and visitor identification?
You can buy them separately - many teams cobble together Bombora for intent and RB2B for visitor ID. But you’ll spend more, deal with two integrations, and lose the ability to correlate signals at the person level. Leadpipe combines both in a single platform starting at $147/month, which is less than what most companies pay for Bombora alone.
The Bottom Line
Intent data and visitor identification are two different signals that answer two different questions:
- Intent data: “Who’s researching topics relevant to my business?”
- Visitor identification: “Who’s on my website right now?”
Neither replaces the other. A team with only intent data knows the market is moving but can’t see their own website traffic. A team with only visitor identification sees who’s on their site but doesn’t know the broader research context.
The winning play is combining both - and the only platform that does it at the person level, under one roof, at a price point that doesn’t require enterprise budget approval, is Leadpipe.
Start with 500 free identified leads. No credit card required. See who’s on your site today and what they’re researching across the web.
Try Leadpipe free — visitor identification + intent data, one platform.
