Account-based marketing has a data problem.
You built your target account list. You defined your ICPs. You are running ads, sending sequences, and publishing content aimed at the 500 accounts most likely to buy. But you have no idea when someone from one of those accounts actually shows up on your website.
Your analytics shows company-level visits from “Acme Corp” - maybe. If their IP happens to resolve to a corporate network. But you do not know which person at Acme Corp visited, what pages they viewed, or whether they are a decision-maker or an intern doing research.
Traditional ABM relies on spray-and-pray outreach to your target list, hoping the timing is right. With visitor identification, you stop guessing. You know exactly when a specific person from a target account hits your website, what content they consumed, and how long they spent evaluating your product. That is the difference between “we think Acme Corp might be interested” and “Sarah Chen, VP of Marketing at Acme Corp, just spent 3 minutes on our pricing page.”
This post is the complete ABM + visitor identification playbook. From defining your target list to closing deals, step by step.
Table of Contents
- Why Traditional ABM Falls Short
- The ABM + Visitor ID Framework
- Step 1: Define Your Target Account List
- Step 2: Set Up Person-Level Identification
- Step 3: Configure Real-Time Alerts
- Step 4: Enrich with Intent Data
- Step 5: Build Your Engagement Playbook
- Step 6: Measure What Matters
- Advanced: Pre-Visit Intent with Orbit
- The Combined Workflow
- FAQ
Why Traditional ABM Falls Short
ABM is the right strategy. Focusing your sales and marketing resources on high-value target accounts instead of casting a wide net makes sense. The economics are clear: a $100K deal from a target account is worth more than ten $5K deals from random inbound.
But the execution has a gap.
Most ABM programs work like this:
- Build a list of 200-1,000 target accounts
- Run LinkedIn ads and content campaigns at those accounts
- Send personalized email sequences to contacts at those accounts
- Wait for someone to respond, attend a webinar, or fill out a form
- When someone engages, notify the assigned AE
The problem is step 4. You are waiting for the prospect to raise their hand. And modern B2B buyers do not raise their hand until they have already completed most of their research. They visit your website, read your content, check your pricing, compare you against competitors - all anonymously.
By the time someone from a target account fills out your form, they are already deep into vendor selection. You have missed weeks of research activity that could have informed your outreach.
Company-level identification tools partially solve this. They tell you “someone from Acme Corp visited your blog.” But knowing a company visited is not actionable. You need to know the person. You need their name, title, email, and LinkedIn. You need to know if the visitor is the VP of Marketing evaluating solutions or a junior analyst doing a competitive sweep.
Person-level identification changes the ABM game entirely. Instead of waiting for engagement, you detect it the moment it happens - at the individual level - and respond with precision.
The ABM + Visitor ID Framework
Here is the framework in one view before we dig into each step:
Target Account List
↓
Visitor Identification (Leadpipe)
↓
"Person from target account detected"
↓
Real-time Slack alert to assigned AE
↓
CRM activity logged automatically
↓
AE engages with full context
↓
Orbit Intent Data (optional layer)
↓
"In-market decision-makers at target accounts
identified BEFORE they visit your site"
The first layer (Leadpipe) catches people from target accounts when they visit your website. The second layer (Orbit) identifies people at target accounts who are researching your category across the web, even before they visit you. Together, they give your ABM program both reactive and proactive intelligence.
Step 1: Define Your Target Account List
If you already have a target account list, skip this section. If you do not, here is a quick framework.
Your target account list should be tight enough to be actionable and broad enough to generate pipeline. For most B2B companies, 200-500 accounts is the sweet spot.
Selection criteria:
- Industry fit: Which verticals have the highest close rates in your CRM?
- Company size: What employee count and revenue range is your sweet spot?
- Technology fit: Do they use tools your product integrates with?
- Geography: Where can your sales team effectively sell and support?
- Budget signals: Have they raised funding, expanded teams, or posted relevant job openings?
Export your list with company names and domains. You will use the domain list to match identified visitors against target accounts.
Pro tip: Also define your “ideal buyer” within each account. For most B2B SaaS, this is 2-3 personas (e.g., VP of Marketing, Director of Sales, RevOps lead). When a visitor from a target account is identified, you will want to quickly assess whether they match one of these buyer personas.
Step 2: Set Up Person-Level Identification
Install Leadpipe’s JavaScript pixel on your website. It takes 2-5 minutes. Once active, every visitor who can be resolved through Leadpipe’s identity graph will generate a webhook with structured contact data.
The webhook payload includes everything you need for ABM:
- email - for direct outreach
- first_name, last_name - for personalization
- company_name - to match against your target account list
- job_title - to identify decision-makers vs. researchers
- linkedin_url - for LinkedIn engagement
- page_url - to understand what they were researching
- visit_duration - to gauge engagement depth
The critical step for ABM: build a matching layer that compares the company_name (or email domain) from each identified visitor against your target account list. When there is a match, trigger a different workflow than your standard visitor identification flow. For a step-by-step walkthrough of this exact setup, see how to track when target accounts visit your site.
A non-target account visitor might go into a general nurture sequence. A target account visitor should trigger an instant alert to the assigned AE with full context.
You can implement this matching logic in a few ways:
- CRM workflow: If your target accounts are tagged in HubSpot or Salesforce, set up a workflow that checks incoming Leadpipe contacts against account ownership and routes accordingly.
- Custom webhook processing: Add target account matching to your webhook handler before routing the data.
- Zapier/Make: Use a lookup step to check the company domain against a Google Sheet of target accounts.
Step 3: Configure Real-Time Alerts
When a target account visitor is identified, speed matters. The assigned AE needs to know immediately.
Slack alerts
The most effective setup is a dedicated Slack channel for target account activity. When Leadpipe identifies a visitor from your target list, fire a Slack notification to the channel (and optionally DM the assigned AE directly):
TARGET ACCOUNT ALERT
Company: Acme Corp (Target Account - Tier 1)
Visitor: Sarah Chen, VP of Marketing
Email: sarah.chen@acmecorp.com
LinkedIn: linkedin.com/in/sarahchen
Pages Viewed:
/pricing (2 min 34 sec)
/case-studies/saas (1 min 12 sec)
/integrations/hubspot (45 sec)
Assigned AE: @mike.thompson
Action: Engage within 1 hour
That Slack message contains everything the AE needs to start a relevant conversation. No research required. No “let me look them up on LinkedIn first.” All the context is right there.
CRM activity logging
Simultaneously, log the visit as an activity on the account record in your CRM. This creates a timeline of target account engagement that the entire revenue team can see:
- March 15: Sarah Chen visited pricing page (2 min)
- March 12: James Park (Director of Ops) visited integrations page
- March 8: Sarah Chen read blog post on visitor identification
Now the AE sees a pattern. Multiple people from Acme Corp are researching your product. A buying committee is forming. That context changes the entire approach - this is not a single curious browser, it is an active evaluation.
Step 4: Enrich with Intent Data
Visitor identification tells you when someone from a target account visits your website. But what about the 80% of the buying journey that happens before they get to your site?
This is where intent data adds a powerful layer to your ABM program.
Before a prospect visits your website, they are:
- Reading industry blogs and analyst reports
- Searching for solutions on Google
- Consuming competitor content
- Asking peers for recommendations on LinkedIn and Slack communities
Traditional intent data providers give you company-level signals: “Acme Corp is researching CRM software.” That is useful but imprecise. You do not know who at Acme Corp is researching, or whether the research is happening in your target persona.
Person-level intent data from Orbit changes this. Orbit monitors online activity across 20,735 topics and identifies specific individuals - by name, email, and title - who are actively researching topics relevant to your product. With ICP filters for company size, industry, and job title, you can narrow this to exactly the personas you care about at your target accounts.
For ABM, this means you can identify in-market decision-makers at target accounts before they ever visit your website.
Try Leadpipe free with 500 leads ->
Step 5: Build Your Engagement Playbook
Different signals call for different responses. Here is a playbook organized by trigger event:
Trigger: First visit from a target account
Signal strength: Medium Action: Log the visit. Send a soft awareness email from the assigned AE introducing themselves. Do not reference the website visit directly. Something like: “I work with companies similar to [company] on [problem space] - would it be helpful to share how [similar customer] approached this?”
Trigger: Target account visitor on pricing page
Signal strength: Very high Action: Instant Slack alert. AE reaches out within 1 hour with a pricing-specific message. Reference the plan tier that matches their company size. Offer a walkthrough.
Trigger: Multiple people from the same target account
Signal strength: Very high (buying committee forming) Action: This is your green light for a full ABM push. The AE should multi-thread - reach out to each identified contact with a message relevant to their role. Marketing should increase ad spend on this account. Consider sending a personalized asset (ROI analysis, industry-specific case study).
Trigger: Return visit from a previously identified contact
Signal strength: High Action: The prospect came back. Whatever you sent or showed them was interesting enough to warrant another look. Follow up on your previous outreach. If they have not responded yet, try a different channel (LinkedIn if you emailed, email if you messaged on LinkedIn).
Trigger: Orbit detects intent before website visit
Signal strength: Medium-high Action: Start the ABM sequence proactively. The AE sends a relevant piece of content related to the topic the prospect is researching. You are engaging them before they even reach your website, positioning yourself ahead of competitors they have not visited yet.
Trigger: Target account visits competitor comparison page
Signal strength: Very high Action: They are actively comparing vendors. This is the most time-sensitive trigger. The AE should reach out with a competitive positioning asset and offer to walk through a side-by-side comparison. Speed wins here.
Step 6: Measure What Matters
ABM metrics should focus on account progression, not vanity numbers. Here is what to track:
Activity metrics
- Target accounts identified on site (monthly): How many of your target accounts had at least one identified visitor this month?
- Unique contacts identified per account: Are you seeing multiple personas, suggesting a buying committee?
- Pages per target account session: How deeply are they researching?
- Return visit rate for target accounts: Are they coming back?
Engagement metrics
- AE response time after alert: How quickly does your team act on target account signals?
- Outreach response rate from identified visitors: Are the personalized messages landing?
- Meeting book rate from target account visitors: How many identified target account visitors convert to meetings?
Pipeline metrics
- Pipeline generated from visitor-identified target accounts: Dollar value attributed to deals where visitor identification was the first touch
- Deal velocity for identified vs. unidentified accounts: Do deals close faster when you engaged early through visitor ID?
- Win rate for identified vs. unidentified target accounts: Does early engagement improve your close rate?
The data should show a clear pattern: target accounts where you engaged based on visitor identification data close faster and at higher rates than accounts where you relied on traditional outreach timing.
Advanced: Pre-Visit Intent with Orbit
The most sophisticated ABM programs combine reactive identification (catching target account visitors on your site) with proactive intent detection (finding target account prospects before they visit).
Here is how Orbit’s person-level intent data adds a pre-visit layer to your ABM program:
How it works
Orbit monitors digital activity across 20,735 topics using a cross-site pixel network. When someone at one of your target accounts starts researching a topic relevant to your product, Orbit flags them - by name, email, job title, and company.
Unlike company-level intent from providers like Bombora or 6sense, Orbit delivers person-level data. You do not just know that “Acme Corp is researching visitor identification.” You know that “Sarah Chen, VP of Marketing at Acme Corp, has been researching visitor identification tools for the past 5 days.”
The combined ABM workflow
- Week 1: Orbit detects Sarah Chen researching “website visitor identification” - she is consuming content across multiple sites
- Week 1: AE sends a relevant guide to Sarah’s email, positioning your solution as a helpful resource (not a pitch)
- Week 2: Sarah visits your website. Leadpipe identifies her on your pricing page
- Week 2: AE gets instant alert: “Sarah Chen (target account) is on your pricing page - she has been researching this topic for 2 weeks”
- Week 2: AE follows up with a specific message referencing the plan that fits Acme’s size and use case
- Week 3: Sarah’s colleague James Park (Director of Ops at Acme) visits your integrations page. Leadpipe identifies him
- Week 3: AE multi-threads - reaches out to James with integration-specific content while continuing the conversation with Sarah
At every stage, your team has context that competitors do not. You know who is researching, what they care about, and when they are actively evaluating. That is the ABM advantage that visitor identification + intent data creates.
The Combined Workflow
Here is the full ABM workflow with both Leadpipe and Orbit:
| Stage | Signal Source | What You Know | Action |
|---|---|---|---|
| Pre-visit intent | Orbit | Person is researching your category online | AE sends relevant content proactively |
| First site visit | Leadpipe | Person identified on your website | Log activity, send awareness email |
| High-intent visit | Leadpipe | Person visited pricing/demo pages | Instant alert, AE engages within 1 hour |
| Multi-person visit | Leadpipe | Multiple people from same account visiting | Full ABM push, multi-thread outreach |
| Return visit | Leadpipe | Known contact came back | Follow up on previous outreach |
Each layer adds signal. Each signal adds context. The more context your AE has, the more relevant their outreach, and the higher the response rate.
Most ABM programs operate with one or zero of these signal layers. Adding both - pre-visit intent detection and on-site person-level identification - puts your team weeks ahead of competitors in every target account conversation.
Implementation Checklist
Here is a quick checklist to implement this playbook:
- Target account list finalized (200-500 accounts with domains)
- Leadpipe pixel installed on your website
- Webhook configured with target account matching logic
- Dedicated Slack channel for target account alerts
- CRM integration logging visitor activity on account records
- Engagement playbook documented (response templates per trigger)
- AE assignment mapping (which rep owns which accounts)
- Orbit configured with ICP filters matching target account personas
- Measurement framework set up (activity, engagement, pipeline metrics)
- Weekly review cadence to analyze target account activity trends
The technical setup takes a day. The playbook refinement takes a few weeks of iteration. The pipeline impact shows within the first month.
Start your free trial - 500 identified leads, no credit card required ->
FAQ
How many target accounts should I start with?
Start with your top 50 accounts - the ones your sales team is most actively pursuing. This keeps the alert volume manageable while you refine your engagement playbook. Expand to 200-500 once the workflow is dialed in.
What if nobody from my target accounts visits my website?
That is where Orbit’s intent data becomes essential. If target accounts are not visiting your site yet, Orbit can identify decision-makers at those accounts who are researching your category elsewhere. Use that signal to drive them to your site through targeted ads and outreach.
Does this work with company-level identification tools?
Partially. Company-level tools can tell you a target account visited, but you still do not know which person or how to reach them. Person-level identification makes the entire playbook actionable because you have an email address and context to work with.
How do I avoid looking creepy when reaching out?
Never say “I saw you on our website.” Instead, lead with value: share a relevant resource, reference a common challenge in their industry, or mention a mutual connection. The visitor data informs your approach, but it should not be the opening line. Review the outreach templates in our pricing page playbook.
Can I use this playbook with an AI SDR?
Absolutely. The target account matching and engagement logic can feed into an AI outreach agent that drafts personalized messages for each trigger event. The AI uses the Leadpipe webhook data plus account context from your CRM to generate relevant, timely outreach at scale.
Related Articles
- Person-Level Intent Data: How It Works
- Orbit: Person-Level Intent Audiences
- What Are the Alternatives to 6sense?
- Intent Data vs. Visitor Identification
- What to Do When Someone Visits Your Pricing Page
- Leadpipe Salesforce Integration
- Visitor Identification Slack Alerts
- Track When Target Accounts Visit Your Site