Detecting Deanonymized Website Visitors with RB2B

RB2B’s core promise is straightforward: the pixel identifies which LinkedIn profiles are browsing your website, in real time, and sends those identities to Slack. No form fill required. No enrichment waterfall needed. Just a person’s name, LinkedIn URL, and the pages they visited, delivered within minutes of their session.

This is a genuinely different data type from everything else in the outbound stack. Instead of targeting a list of people who might be interested, you are targeting people who have already demonstrated interest by visiting your site. The conversion rate from identified visitor to booked meeting is materially higher than cold outbound — but only if you are fast, relevant, and selective.

This playbook walks through the full implementation: pixel install, Slack alert configuration, ICP filtering, enrichment, HubSpot routing, and measurement. It also covers the privacy and legal constraints you need to understand before going live, particularly for any visitors from EU IP addresses.

Setup: Prerequisites

• RB2B account: Pro plan ($149/month). The free plan limits you to 10 identifications per month and does not include the Slack or CRM integrations. The Pro plan allows unlimited identifications (subject to their data availability, not a hard cap you set).
• Website access: You need to be able to add a JavaScript snippet to the of your website. If you are on a CMS like WordPress, HubSpot CMS, or Webflow, this is a 5-minute GTM tag or direct theme edit. If your engineering team controls the site, file a ticket with the snippet and they can add it in one deploy.
• Slack workspace: RB2B’s Slack integration is pre-built. You authorize it via OAuth and select the destination channel.
• HubSpot or Salesforce: For routing identified visitors to your outbound team’s CRM view. RB2B has a native HubSpot integration; Salesforce requires a Zapier or Make middleware step.

Step 1: Install the RB2B Pixel

Log into RB2B. Navigate to Settings → Pixel. Copy the JavaScript snippet. It looks like this:

Add this snippet to the section of every page you want to track. If you are using Google Tag Manager, create a new Custom HTML tag with the snippet, set trigger to "All Pages," and publish. Verification: after install, visit your own website from a LinkedIn-authenticated browser session. Within 5–10 minutes, your own profile should appear in the RB2B dashboard under "Recent Visitors." If it does not appear within 15 minutes, check that the script is loading (browser console should show a successful load of the RB2B script) and that your LinkedIn session cookie is active in the same browser.

What the pixel actually does: RB2B's pixel makes a reverse identity match between your site visitor's browser fingerprint and LinkedIn profile data. It does not access your visitors' LinkedIn cookies directly — it cross-references anonymized browser signals against RB2B's proprietary identity graph, which is built from users who have voluntarily connected their LinkedIn profile to RB2B's network (often via other RB2B customer sites they have visited). This is a probabilistic match, not a deterministic one. RB2B reports an identification rate of 20–35% of US business traffic — meaning roughly 1 in 4 visitors gets identified. The other 3 remain anonymous.

Step 2: Configure Slack Alerts

In RB2B, go to Integrations → Slack. Click "Connect to Slack" and authorize via OAuth. Select the destination channel. Recommendation: create a dedicated channel called #visitor-signals or #rb2b-alerts rather than routing into #general or an existing sales channel. Volume will be significant — a site getting 500 business visitors per week will generate 100–75 Slack messages per week (at 20–35% identification rate). A dedicated channel keeps the signal visible without polluting other channels.

RB2B's default Slack message format includes: visitor name, LinkedIn URL, company, job title, pages visited, time on site, and session timestamp. This is enough context for a trained SDR to make a send/no-send decision in under 10 seconds.

Step 3: Filter to ICP-Fit Visitors

Raw RB2B output is noisy. Not every identified visitor is a prospect: competitors research your site, job seekers visit your careers page, journalists check your pricing. Without filtering, your SDRs will waste time evaluating non-prospects and miss the signal in the noise.

RB2B's Pro plan includes basic filters inside the dashboard: industry, company headcount, job title keywords, and page visited. Configure these first:

• Job title filter: Include only seniority levels relevant to your ICP. If you sell to VP+ buyers, filter for "VP," "Director," "Head of," "Chief." Exclude "intern," "student," "recruiter."
• Company headcount filter: Set your target range. If you sell to 50–500 person companies, filter the headcount field accordingly.
• Page filter: Prioritize visitors who hit high-intent pages: /pricing, /product, /demo, /compare. A visitor who only hit your blog once is lower priority than one who visited /pricing twice in the same session.

For more sophisticated filtering, pipe RB2B's Slack webhook payload into a Make or n8n workflow that applies additional logic before forwarding to your SDR channel. The webhook payload is JSON and includes all visitor fields:

// RB2B webhook payload shape (simplified)
{
  "event": "visitor_identified",
  "visitor": {
    "name": "Jane Smith",
    "linkedin_url": "https://linkedin.com/in/janesmith",
    "title": "VP of Revenue Operations",
    "company": {
      "name": "Acme Corp",
      "industry": "B2B SaaS",
      "headcount": 210,
      "domain": "acmecorp.com"
    }
  },
  "session": {
    "pages_visited": ["/pricing", "/product/features", "/compare"],
    "session_duration_seconds": 187,
    "timestamp": "2026-04-30T14:22:11Z",
    "ip_country": "US"
  }
}

// n8n filter node: only forward if:
// - visitor.company.headcount between 50 and 2000
// - session.pages_visited contains "/pricing" OR "/demo"
// - visitor.title matches /VP|Director|Head of|Chief/i
// - session.ip_country == "US"  // (see GDPR section below)

Step 4: Enrich and Route to HubSpot

After ICP filtering, enrich the identified visitor before routing. RB2B gives you a LinkedIn URL and basic firmographic data, but you need a work email to reach out. Pipe the visitor's LinkedIn URL into an enrichment step via Apollo (match by LinkedIn URL, 1 credit per lookup) or Clay (if you have a Clay workspace with LinkedIn URL enrichment configured).

In n8n or Make, the enrichment step fires after the ICP filter passes, before the HubSpot routing step:

// n8n HTTP Request node: Apollo person match by LinkedIn URL
// Method: GET
// URL: https://api.apollo.io/v1/people/match
// Body:
{
  "api_key": "{{env.APOLLO_API_KEY}}",
  "linkedin_url": "{{$json.visitor.linkedin_url}}",
  "reveal_personal_emails": false,
  "reveal_phone_number": false
}

// On success: extract email, verified_email boolean, phone
// On failure or null email: log to #visitor-signals as "identified but no email found"
//   -- do NOT skip; SDR can still reach out via LinkedIn

After enrichment, create or update the HubSpot contact record and set a custom property rb2b_identified_visitor: true and rb2b_last_seen: [timestamp] and rb2b_pages_visited: [comma-separated list]. Create a HubSpot list filtered on rb2b_identified_visitor = true AND create_date = today. Assign this list to your outbound SDR team as a daily priority queue.

Send a final Slack notification to the assigned SDR with the enriched context, the HubSpot contact link, and a suggested LinkedIn message opening line (generated via a Claude API call if you want to automate this — optional). The SDR should reach out within 2 hours of identification for maximum conversion.

Conversion Rate: Real Numbers

Public benchmarks from RB2B customers (sourced from their case studies, G2 reviews, and community discussions through Q1 2026):

• Identification rate: 20–35% of US business traffic identified by LinkedIn profile.
• ICP-fit rate of identified visitors: 15–25% of identified visitors pass ICP filters (company size, title, industry). This is the population your SDRs actually work.
• Outreach response rate: 8–18% of contacted visitors respond to a LinkedIn message or email. Higher end requires a well-personalized message referencing their site visit (done tactfully, not creepily).
• Response-to-meeting conversion: 25–40% of responses convert to a booked meeting.
• Net: visitor-to-meeting rate: Multiply through: 27% identification x 20% ICP fit x 13% response x 32% meeting = approximately 0.2–2.5% of total website visitors convert to a meeting.

For context: a typical inbound form conversion rate is 1–3% of site visitors. RB2B can get you to a similar conversion rate on visitors who never filled a form — but only if your SDRs are fast and the outreach is relevant. Slow or generic outreach drops the response rate to 3–5%, which makes the math much less compelling.

GDPR and Privacy: What's Allowed Where

This is the section most vendor-written RB2B content skips. You need to understand it before going live.

United States: B2B website visitor identification is generally permissible under US law. There is no federal equivalent of GDPR. CAN-SPAM and CCPA apply to subsequent communications, not to the identification itself. CCPA requires that California residents have the right to opt out of "sale" of their personal information — whether RB2B's identity matching constitutes a "sale" under CCPA is a legal question your counsel should evaluate, but RB2B's current terms of service are structured to argue it does not. US-based operations can run RB2B with standard privacy policy disclosure ("we use third-party tools to identify business visitors") without additional consent mechanisms in most interpretations. Consult your legal counsel for your specific situation.

European Union: RB2B's approach has significant GDPR exposure in the EU. GDPR requires a lawful basis for processing personal data. RB2B's identity matching processes personal data (LinkedIn profile linked to browsing behavior) without explicit consent from the data subject. The "legitimate interest" basis could theoretically apply for B2B marketing, but it requires a documented Legitimate Interest Assessment (LIA) and a genuine balancing test — not a rubber stamp.

More practically: RB2B's identity graph is built primarily from US LinkedIn data. Their EU identification rates are materially lower (estimated 5–12% versus 20–35% for US traffic), making the product significantly less useful for EU-heavy sites regardless of legal considerations. The pragmatic recommendation: use the ip_country filter in your n8n/Make workflow to exclude EU visitors from RB2B processing entirely (filter out IP countries in the EU member state list). This eliminates your GDPR exposure and does not meaningfully reduce your addressable market if you are US-focused. For EU-targeted identification, evaluate Warmly or Leadfeeder, which have explicit EU data processing agreements and GDPR-compliant product architectures.

Disclosure in outreach: When an SDR reaches out to an identified visitor, they should not open with "I saw you visited our pricing page" in a way that feels surveillance-like. The correct framing is to reference the topic area without revealing the tracking mechanism: "I noticed you may be evaluating [problem area] solutions" or lead with a relevant insight. This is not just ethical guidance — outreach that feels like surveillance generates immediate negative responses and brand damage that offsets any conversion lift.

Troubleshooting

• Identification rate below 10%: Check that the pixel is loading on all pages (not just the homepage). Verify via browser DevTools → Network tab that the RB2B script is returning a 200 response. Also check: if most of your traffic is mobile, identification rates are lower (LinkedIn cookies are less consistently active on mobile browsers).
• High noise-to-signal ratio in Slack: You have not configured ICP filters. Start with the job title and headcount filters inside RB2B's dashboard before building the n8n layer. Dashboard filters are faster to iterate on than workflow logic.
• Apollo enrichment returning null emails on RB2B-identified visitors: RB2B's LinkedIn URL format may not match Apollo's expected format. Normalize the LinkedIn URL before passing to Apollo: strip trailing slashes, ensure the URL starts with https://www.linkedin.com/in/ (not https://linkedin.com/in/). Apollo's match is sensitive to URL format.
• SDRs not acting on visitor alerts within the 2-hour window: The notification format is too complex or the channel is too noisy. Reduce the Slack message to: Name, Title, Company, Pages Visited, and one action button. Remove all other fields. Cognitive load is the enemy of fast response.

What This Doesn't Solve

Anonymous traffic. The 65–80% of visitors RB2B cannot identify remain anonymous. For this population, you need a different strategy: better CRO to increase form conversion, retargeting ads, or an IP-based company identification tool (Clearbit Reveal, Warmly's company-level identification) that tells you which company is visiting even when individual identity is unknown. RB2B and company-level identification are complementary, not substitutes.

Account-level coordination. RB2B identifies individual visitors. It does not tell you that three people from the same company visited in the same week — a much stronger buying signal than one person visiting once. Build an account aggregation layer in HubSpot: a workflow that checks the HubSpot company record for multiple rb2b_identified_visitor contacts created in a 7-day window and flags the company for account-based outreach.

Should You Actually Buy RB2B?

Buy RB2B if: you have more than 2,000 monthly US business visitors, your SDR team has capacity to respond to inbound signals within 2 hours, and your average deal size justifies spending time on visitors who have not yet raised their hand. At $149/month, the break-even is roughly 1–2 additional meetings per month depending on your ACV. Most teams with decent traffic and a responsive SDR motion hit break-even in the first 30 days.

Do not buy RB2B if: your traffic is primarily EU-based, your site gets fewer than 500 business visitors per month (the identification volume will not justify the workflow overhead), your SDR team cannot realistically respond within 2–4 hours, or you are in a highly regulated industry where the privacy implications require significant legal review before deployment.

The honest ceiling: RB2B is a top-of-funnel signal amplifier, not a demand generation engine. It makes your existing traffic more actionable. It does not create new demand. Teams that treat it as a replacement for outbound prospecting or content strategy will be disappointed. Teams that treat it as a conversion layer on top of existing traffic will find it one of the highest-ROI tools in the GTM stack at this price point.

Related reading: See the full RB2B vendor profile for pricing details, data methodology, integration depth, and analyst assessment. For a direct comparison against Warmly's deanonymization and account intelligence approach, see RB2B vs. Warmly. For enriching identified visitors before routing, see the Clay waterfall enrichment playbook.