Help the user with RB2B platform questions — Person-Level Website Visitor ID, Company-Level ID, Hot Pages, Hot Leads, Traffic Insights, Identity Resolution API, and integrations.

Important context: RB2B offers person-level visitor identification (US traffic only) — it identifies the individual visiting your site, not just the company. This is the key differentiator vs Clearbit Reveal, Leadfeeder, and other company-level-only tools. Company-level ID is powered by Demandbase and works globally.

If exists, read it first for accumulated knowledge.

If the question is about visitor identification strategy across tools (not RB2B-specific) — hand off: "This is an intent signal strategy question — run: " If the question is about enrichment strategy across tools — hand off: "This is an enrichment strategy question — run: " If the question is about building prospect lists across tools — hand off: "This is a prospect list building question — run: " If the question is about lead scoring model design — hand off: "This is a lead scoring strategy question — run: " If the question is about connecting RB2B to other tools — hand off: "This is a tool integration question — run: "

Otherwise, answer directly using the reference below.

Read

references/platform-guide.md

for detailed module documentation, pricing, integrations, and data model.

User says: "I want to know exactly who is visiting our pricing page so my SDRs can follow up — how do I set up RB2B?" Skill does: Walks through pixel installation, Hot Pages configuration for the pricing page, Slack alert setup, explains person-level ID is US-only with 35-45% match rate on Pro+, recommends connecting to CRM for automatic lead creation, and suggests a follow-up workflow where SDRs reach out within 24 hours referencing the specific page visited Result: Sales team gets real-time Slack alerts with visitor name, email, LinkedIn, and company when someone hits the pricing page

User says: "We're currently using Clearbit Reveal for website visitor identification — should we switch to RB2B?" Skill does: Compares person-level (RB2B) vs company-level only (Clearbit Reveal), explains RB2B's US-only limitation vs Reveal's global coverage, discusses pricing differences (RB2B $79-199/mo vs Clearbit credit-based), notes that Clearbit is now Breeze Intelligence (HubSpot lock-in), and recommends RB2B if US traffic is primary and person-level ID is the goal Result: Clear comparison helping the user decide based on their traffic geography and identification depth needs

User says: "How do I automatically add RB2B-identified visitors to my Apollo sequences?" Skill does: Explains the native Apollo integration, walks through connecting RB2B to Apollo, recommends filtering with Hot Leads (ICP criteria) before pushing to sequences to avoid spamming non-ICP visitors, suggests using Hot Pages to only sequence visitors from high-intent pages, and shows how to personalize the sequence with visit context Result: Automated pipeline from website visit → ICP filter → personalized outbound sequence

Symptom: RB2B dashboard shows zero visitors after installing the pixel Cause: Pixel snippet not loading correctly, blocked by ad blockers, or installed on wrong pages Solution: Verify the pixel is in the tag using browser dev tools (Network tab → search for "rb2b"). Check that it's not blocked by your Content Security Policy. Test with ad blockers disabled. If using Google Tag Manager, ensure the tag fires on "All Pages" and the trigger is set to "Page View".

Symptom: Getting mostly company-level identifications, very few person-level matches Cause: Traffic is primarily non-US, mobile, or VPN — person-level ID only works for US-based desktop/business IP visitors Solution: Check your traffic geography in Google Analytics. If most traffic is international, person-level ID won't work for those visitors. Consider upgrading to Pro+ for higher US match rates (35-45%). If using ads, ensure US targeting. Note that mobile carrier IPs and VPN users can't be identified at person level.

Symptom: Same visitors appearing as new leads in CRM repeatedly, or outdated visitor data Cause: CRM integration not deduplicating on email, or webhook pushing every page view as a new record Solution: Configure your CRM integration to match on email address and update existing records rather than creating duplicates. In HubSpot/Salesforce, set the integration to "update if exists, create if new." If using webhooks with a custom integration, implement dedup logic on your end using the visitor's email as the unique key.