RB2B Review 2026: Free Website Visitor Identification Tested

You finally know who visited your website. Great. Now what?

That is the question visitor identification tools eventually have to answer. A name or company in Slack is useful, but you still need to decide whether that visitor fits your ICP, understand what they were interested in, get the right data into your CRM, and decide who should follow up.

RB2B handles more of that workflow than its simple “identify anonymous visitors” pitch suggests. This review looks at where it works well, what you get for free, and where your growth stack may still need to pick up the work.

Key takeaways

• RB2B reports approximately 40–45% contact-level identification for US traffic, with another 30–35% identified at the company level. Your actual match rate will depend on your traffic mix, visitor behavior, devices, consent status, and available identity signals.
• If you want person-level identification, your traffic needs to come from the US. International visitors can still be identified at the company level, subject to the appropriate consent and compliance setup.
• The free tier gives you 150 company-level credits per month. You’ll need a paid plan for person-level identification.
• On higher tiers, you get more than Slack alerts. RB2B adds business emails, HubSpot and Salesforce integrations, Hot Leads filtering, and connections to outbound tools, so you can route identified visitors into your existing sales workflows.
• If you serve global markets, your person-level coverage will depend heavily on how much of your audience is US-based.
• You can handle filtering, CRM routing, and some workflow automation inside RB2B, but you may still need additional tools if you want deeper enrichment, broader intent data, or more of your growth workflow managed in one place.

Understanding why B2B teams need visitor identification

80-95% of your traffic remains completely anonymous. That statistic defines the problem. Your website generates traffic from companies researching solutions, evaluating competitors, and reading your content. Without visitor identification, you have no idea who they are until they decide to reach out, if they ever do.

The shift from company-level to person-level identification changed what teams expect from these tools. Company-level identification tells you that someone from Acme Corp visited your pricing page. Person-level identification tells you that Sarah Chen, VP of Marketing at Acme Corp, visited your pricing page three times this week and spent four minutes on your case studies. The difference matters for outbound prospecting.

The real cost of anonymous traffic

Anonymous traffic isn’t a vanity metric problem. It’s a revenue problem. Every company visiting your site represents potential revenue you cannot capture because you don’t know they exist. Your SDRs cannot reach out to companies they cannot see. Your marketing team cannot retarget visitors they cannot identify. Your sales team cannot prioritize accounts already showing buying intent.

Visitor identification tools emerged to close this gap. The question is whether identification alone creates enough value or whether you need the full workflow from identified visitor to qualified opportunity.

What free website visitor ID actually delivers

RB2B works by matching website visitors against an identity graph of opted-in US consumers. When someone visits your site, the pixel fires and attempts to resolve their identity using cookie matching. If successful, RB2B delivers a Slack notification with the visitor’s name, company, job title, and LinkedIn profile URL.

The setup is simple: install a JavaScript pixel, connect Slack, and notifications start arriving. The free tier provides 150 credits per month for company-level identification only. Person-level identification requires a paid plan.

The match rate reality check

RB2B reports a combined identification rate of approximately 70–80% for US traffic. That breaks down to roughly 40–45% contact-level identification and another 30–35% at the company level.

Those numbers are useful as a benchmark, but you shouldn’t treat them as a guarantee. Your results will depend on your traffic mix, visitor behavior, devices, consent status, and the identity signals RB2B can resolve.

The difference between the two match types matters in practice. Contact-level identification can give you a name, professional email, LinkedIn profile, job title, and company affiliation when available. Company-level identification tells you which organization visited without necessarily telling you who the individual visitor was.

If you get 10,000 monthly visitors and 60% are US-based, applying RB2B’s reported 40–45% contact-level range to those 6,000 US visitors gives you roughly 2,400–2,700 identified individuals. Use that as an illustrative range, not an expected outcome for every site.

What the free tier actually provides

The free plan includes:

• 150 monthly resolutions
• Company-level identification
• No access to person-level contact details such as names, emails, or LinkedIn profiles after the trial
• No CRM or outbound integrations
• Upgrade required to unlock full contact profiles and advanced integrations

The free tier validates whether your traffic includes ICP-fit companies. It doesn’t provide enough data or volume for operational outbound at scale.

Testing RB2B’s identification capabilities

Person-level identification is US-only

If you want person-level identification from RB2B, your visitor needs to be in the United States. RB2B checks visitor location before attempting contact-level resolution and restricts this part of the product to US traffic.

That doesn’t mean your international traffic disappears entirely. RB2B can still attempt company-level identification outside the US, subject to the appropriate consent and compliance setup.

So if you sell globally, look closely at where your traffic actually comes from. A US-heavy audience gives you more opportunities for contact-level identification. A more international audience means you’ll rely much more heavily on company-level data.

Match rates vary by traffic

RB2B’s published averages give you a starting point, but your own traffic determines what you actually see:

• US traffic: You may see around 40–45% contact-level identification, with another 30–35% identified at the company level based on RB2B’s reported averages
• International traffic: You won’t get person-level identification, but company-level identification can still apply
• VPN and proxy traffic: You may see lower identification when location or identity signals are obscured
• Traffic quality and behavior: Your results can shift depending on visitor quality, behavior, consent status, and the signals available for matching

The number that matters most isn’t RB2B’s headline average. It’s the match rate you see across your own audience after the pixel has been running long enough to give you a representative sample.

From identification to activation

Knowing who visited is useful. The bigger question is what you can do with that information once it reaches your team.

RB2B now gives you more ways to prioritize and route visitors than a basic Slack-only setup. Hot Leads lets you narrow the list using factors such as ICP fit, industry, company size, decision-making role, geography, and behavioral signals. You can then push qualifying visitors into connected CRMs, messaging tools, and outbound platforms.

What RB2B gives you vs. what you may still need

So the question isn’t whether RB2B can move identified visitors into a workflow. It can. The real decision is how much of the workflow you want to configure across connected tools versus manage inside one platform.

Integrating visitor identification with your growth stack

Standalone visitor identification creates workflow debt. Most teams using RB2B add layers:

• Enrichment tools (Apollo, ZoomInfo, Clay) to get verified emails and firmographics
• CRM workflows: Pro and Pro+ can connect directly with platforms such as HubSpot and Salesforce to create or update records and attach website activity
• Outbound workflows: RB2B connects with outbound platforms directly and through webhooks, Zapier, and Make for automated follow-up
• Lead prioritization: Website activity and visitor data can feed CRM scoring, segmentation, routing, and outreach workflows

This stack solves the workflow problem but creates a new problem: you now manage four or more tools, each with its own subscription, data model, and failure modes.

The platform alternative

Instead of stitching together point solutions, platforms that combine identification with enrichment, scoring, and CRM sync eliminate the integration burden. Ploy Grow identifies companies visiting your site, enriches them with firmographic data, scores buying intent, and syncs qualified accounts directly to HubSpot or Attio.

The difference matters for your daily work. With RB2B plus enrichment tools, your team processes notifications. With an integrated platform, you review qualified opportunities that are already in your CRM with context attached.

Ploybooks take this further by automating entire workflows. Instead of building sequences manually, pre-built Ploybooks handle tasks like emailing ICP website visitors or running Company Swarm outreach for high-intent accounts.

Privacy and compliance considerations

Why person-level identification is US-only

If you want to use RB2B for person-level identification, you’re working with US traffic only. RB2B checks visitor location before attempting contact-level resolution and does not extend that part of the product internationally.

Company-level identification is broader. If you have international traffic, RB2B can still identify organizations, although you’ll need to make sure your consent and compliance setup matches the markets you operate in.

For your team, the distinction is straightforward: you can use person-level identification for US visitors and company-level identification more broadly. Your own privacy and consent obligations will still depend on where you operate and who you target.

What you must set up

Visitor identification tools require customer-side compliance work:

• Privacy policy disclosure about third-party identity graph usage
• Cookie banner setup to exclude declined visitors from identification
• Opt-out link in marketing emails (CAN-SPAM requirement)
• Do Not Track and Global Privacy Control signal honoring

RB2B operates under CAN-SPAM with opted-in data and verifiable consent records. CCPA compliance includes a public opt-out form maintained by the provider with automatic request passthrough. But the responsibility for proper disclosure and consent management falls on you.

Regional coverage reality

If you serve a global audience, your geographic traffic mix will have a direct impact on what you get from RB2B. The more US traffic you have, the more opportunities you’ll have for person-level matches. Outside the US, you’ll be working primarily with company-level identification.

When free visitor ID makes sense

The free tier works for one purpose: proving that ICP-fit companies visit your website. At 150 company-level credits per month, you can validate traffic quality before committing budget.

If your site generates 2,000 monthly visitors with 80% US traffic and you discover 40 ICP-fit companies visiting per month, you have proof that visitor identification creates value. That validation justifies upgrading to paid plans or investing in a full platform.

Where RB2B breaks down

RB2B hits limits when:

• Volume exceeds manual capacity: 50+ identified visitors per week overwhelms SDR workflows
• International traffic matters: 40-60% of visitors generate no person-level data
• Speed matters: Manual enrichment and outreach delays response by hours or days
• Attribution matters: No connection between visitor, campaign, and closed revenue

When you experience these limits, you have two paths: add enrichment and automation tools on top of RB2B, or replace it with a platform that connects identification to revenue.

The platform path

Ploy’s method eliminates the work of stitching tools together. Ploy Grow handles visitor de-anonymization, firmographic enrichment, intent scoring, and CRM synchronization in one platform. Because Ploy Web, Ploy Grow, and Ploy Ads share context, insights from visitor identification inform website optimization and ad targeting automatically.

The free tier includes visitor de-anonymization, custom domains, integrations, and Git sync with no credit card required. If your goal is turning anonymous traffic into revenue rather than Slack notifications, testing a platform method against point solutions reveals the workflow difference quickly.

Where you may need more than RB2B

You may start looking beyond RB2B when:

• International person-level identification matters: You’ll only get contact-level identification for US traffic
• You need deeper enrichment: You may want additional providers for more specialized firmographic, technographic, or contact data
• You want cross-channel intent: RB2B can prioritize visitors using ICP and behavioral signals, but you may need other systems if you want intent data across a wider set of touchpoints
• Full-funnel attribution matters: You can track visitor activity and UTM campaign data and pass that information into connected systems, but tying website identification all the way through to closed revenue may still depend on your CRM or attribution stack

At that point, you have two options. You can keep RB2B at the center and add integrations around it, or you can move toward a platform that brings more of those functions into one system.

What makes Ploy different

Ploy doesn’t stop at identification. You get:

• Automatic enrichment: Company firmographics, tech stack, funding, and hiring signals attached to every identified visitor
• Intent scoring: Built-in models that prioritize accounts showing buying signals across multiple touchpoints
• Native CRM sync: Qualified accounts flow directly into HubSpot or Attio with full context, no manual data entry
• Workflow automation: Ploybooks handle email sequences, lead routing, and outreach at scale
• Cross-platform intelligence: Insights from website visitors inform your paid ads and on-site personalization automatically

The difference shows up in your daily work. With RB2B, you triage Slack notifications and manually build records. With Ploy, you review qualified opportunities that are already scored, enriched, and ready for outreach.

Ploy’s free tier lets you see how integrated identification, enrichment, and automation change what’s possible when anonymous visitors land on your site. No credit card required, and you’ll have qualified accounts in your CRM within minutes of setup.

Frequently asked questions

How long does RB2B take to show results after installation?

The pixel fires immediately after installation, and Slack notifications begin arriving within minutes of your first matched visitor. Setup takes approximately five minutes for pixel installation and Slack connection. However, you’ll need additional time to build workflows for enrichment, lead scoring, and CRM entry before you can act on notifications at scale.

Does RB2B work with traffic from paid advertising campaigns?

Yes, RB2B identifies visitors regardless of traffic source. However, paid traffic often has different match rate characteristics than organic traffic. Visitors from LinkedIn ads may match at higher rates due to professional context, while visitors from display advertising match at lower rates due to broader audience targeting.

What happens to identified visitor data if you cancel your RB2B subscription?

Historical data access depends on your plan and timing. The platform does not provide bulk export functionality for identified visitors. If you need long-term records, export data to your CRM or enrichment tools before cancellation.

Can RB2B identify visitors using VPNs or privacy browsers?

VPN traffic typically does not match at the person level because the IP address resolves to the VPN provider rather than the visitor’s location. Privacy browsers that block third-party cookies prevent the identity graph matching that powers person-level identification. Company-level identification via IP lookup also fails for VPN users. The growing adoption of privacy tools contributes to the gap between marketed match rates and real-world results.

How does RB2B handle repeat visitors to the same website?

RB2B charges one credit per unique identified person, not per visit. If the same person visits multiple times within a billing period, you’re charged once. However, the Slack notification fires on each visit, which can create noise if high-intent prospects return frequently. There is no native suppression for repeat visitor notifications, so teams often build custom filters in Slack or downstream tools.