The cheapest path to "who is on my site right now". For Yalc workflows, RB2B feeds the warmest possible source into the qualification pipeline, alongside LinkedIn Visitor Qualification.
RB2B identifies anonymous US website visitors by person and by company. Drop a script on the site, RB2B matches the visitor against its Person-Level ID database, and surfaces the named individual plus their LinkedIn profile and validated business email. Coverage claim is 70 to 80 percent of US web traffic.
For Yalc operators, this is the warmest top of funnel source available. Where LinkedIn Visitor Qualification scores people who already engaged with you (profile visits), RB2B scores people who hit your website. Both are intent signals; together they triangulate buying interest before a single outbound message goes out.
RB2B sits at the **listen** node of every Yalc workflow that treats site visits as a buying signal. Output flows into the same qualification pipeline that handles LinkedIn visitors and engagement scrapes. Triage, score, route. The MCP equivalent or webhook integration depends on the team's volume.
The tight scope (US only person-level) is the constraint to plan around. For European audiences, the company level fallback is useful but requires a different outbound approach (account based outreach to inferred decision makers, not direct person outreach).
The website visitor identification node. Yalc reads daily resolutions, scores each visitor against ICP, surfaces the hottest into a daily review queue.
Copy paste prompts for Claude Code that invoke RB2B.
No first party Yalc skill ships for RB2B yet. The workflow is straightforward enough to drive from Claude's HTTP tool calling RB2B's API directly, then routing the output through the existing leads qualification skill. A dedicated RB2B skill would consolidate the daily pull plus competitor exclusion plus ICP scoring into one verb.
→ Request a Yalc skill for this toolRB2B sits at the unusual intersection of "free is generous enough to actually be useful" and "paid is cheap enough that you'll just upgrade". Free tier gives you 150 company-level identifications per month plus a 7 day full-featured trial of person-level ID. Starter at $79 a month unlocks 300 monthly person-level resolutions for US visitors, with LinkedIn profiles, validated emails, and full integrations.
The cost reality is that RB2B's value depends entirely on whether your site gets US traffic worth identifying. If 70 percent of your traffic is European or APAC, only the company-level ID applies (still useful, but a different ROI calculation). For US heavy B2B sites, $79 a month for 300 named visitors a month is a strong unit economic.
150 company-level resolutions monthly. 7 day full Starter trial. Right for piloting.
300 person-level resolutions, US only, with LinkedIn profiles plus validated emails. Right for solo operators and small teams.
More resolutions, advanced integrations, team seats. Talk to sales for volume pricing.
RB2B uses Person-Level Identity matching against its US database, fed by partnerships and signals. The technology is proprietary; the user-visible result is a named individual with LinkedIn profile and validated email after a visitor lands on your site.
GDPR and similar regulations make person-level identification of EU visitors meaningfully harder. RB2B's database is built on US data; expanding to EU would require a different legal and technical foundation. Company level ID via Demandbase partnership is global.
150 company-level resolutions per month is genuinely useful for low traffic B2B sites. Pair with the 7 day Starter trial to see what person-level adds. Most operators upgrade to Starter within the trial.
ZoomInfo's visitor reveal is bundled into the broader ZoomInfo platform and costs significantly more. RB2B is standalone and focused. For a team that doesn't need the full ZoomInfo suite, RB2B is dramatically cheaper at the visitor ID layer.
Real time on the visitor's session typically. The script captures the visit, RB2B matches against the database, results appear in the dashboard within minutes. For Yalc workflows, daily pulls cover most use cases.
Compliance is on the website operator. RB2B provides the technical capability; you implement disclosures and consent per your jurisdiction's rules. Most US privacy frameworks treat this as legitimate interest with appropriate notice.
Or fork the repo and contribute one.