RB2B: Person-level website visitor identification for US traffic.
RB2B identifies the individual visiting your site (LinkedIn profile, work email) for US-based traffic. Our pod wires those anonymous visits into scored, routed plays so an SDR calls the right person the same day they hit pricing.
What is RB2B and how do you use it in outbound?
RB2B identifies individual US visitors on your website and pushes them to Slack or your CRM in near real time. In outbound it is a timing signal, not a list source: a named person from a target account reading your pricing page this morning is the highest-intent trigger most B2B teams can access, and it works best when routed into a same-day call and a short, specific email.
- Person-level, US-only. Treat non-US traffic with company-level tools instead.
- Speed is the whole value. Route to a same-day touch or the signal is worthless.
- Reference the intent category, never the specific page view.
- Suppress open opportunities and existing customers before routing.
How our pod runs RB2B.
- Install RB2B and configure ICP filters so only relevant visitors surface
- Enrich identified visitors via Clay and route to the CRM with source tags
- Trigger same-day call queues and email touches on pricing / demo visits
- Suppress current customers, open opps, and closed-lost from alerts
Where RB2B earns its place in the stack.
Pricing-page intent
An ICP contact visits pricing twice in 48 hours. RB2B identifies them, we enrich, score, and route a same-day call queue and personalized email.
Anonymous demo-page revival
A prospect from a target account visits the demo page but never fills the form. We surface the contact and route a warm follow-up before the intent decays.
Real RB2B plays we ship.
Pricing visit to same-day call
- 01RB2B fires a visitor identification event
- 02Clay checks ICP fit and current CRM status
- 03New, in-ICP contacts sync to HubSpot / Salesforce with source = RB2B
- 04SDR gets a Slack alert with brief, then dials + emails same day
US-focused B2B SaaS with steady site traffic and an ICP that visits pricing before booking.
How we configure RB2B in week 1.
The Foundation build installs RB2B in your own account in this order. Each step is documented in the operating playbook we hand over.
- 01
Install and verify
Add the script sitewide, confirm identification fires on pricing, product, and comparison pages, and check volume for a full week before building plays.
- 02
Tier the pages
Pricing, comparison, and demo pages are tier 1. Blog and careers traffic are noise. Only tier 1 should page a human.
- 03
Filter to ICP
Match the identified person against your ICP definition and target account list. Drop everything else so the Slack channel stays credible.
- 04
Route to a play
Tier 1 ICP match creates a task for a same-day call plus a two-line email. Everything else drops into a low-volume nurture sequence.
- 05
Write it back
Log the visit as a CRM activity with page tier and timestamp so meetings can be attributed to website intent later.
What good looks like with RB2B.
| Metric | Benchmark | Context |
|---|---|---|
| US identification rate | 20-35% | Of US B2B visitors, varying with traffic mix. |
| Tier 1 ICP matches | 5-15% | Of identified visitors, on a focused ICP. |
| Same-day touch target | Under 4 hours | Reply rates fall off sharply after the same business day. |
Ranges reflect what we observe running B2B SaaS mid-market motions. Treat them as starting targets, not guarantees.
How RB2B builds go wrong.
- Saying 'I saw you visiting our pricing page.' It reads as surveillance and kills replies.
- Routing every identified visitor, which trains the team to ignore the channel.
- No suppression, so AEs get paged about their own open opportunities.
- Relying on it outside the US, where person-level coverage drops sharply.
Frequently asked questions
Explore the rest of the stack.
How we run RB2B by segment.
Every ICP and industry page shows the target list logic, triggers, and sequence structure we run with this stack.
Narrow TAM, association and event driven outbound.
Read the playbookBottom-up adoption with technical buyers who hate pitches.
Read the playbookIncident and compliance triggers into CISO organizations.
Read the playbookFast-moving category with budget owners still forming.
Read the playbookRegulatory triggers and compliance-aware sequences.
Read the playbookHeadcount and benefits-cycle timing into People leaders.
Read the playbookHIPAA-aware outbound into clinical and revenue-cycle buyers.
Read the playbookCrowded category, so displacement and stack-signal plays win.
Read the playbookRequest an integration.
Tell us which tool you need connected and we will reply with a timeline, scope, and whether it fits your pod.
Want to see RB2B run inside your stack?
See your reachable market, realistic meeting range, expected cost per meeting, and recommended outbound motion.