Skip to main content

RB2B

Purpose: Person-level website visitor identification. Identifies individual visitors by name, job title, email (where available), LinkedIn profile, and company — not just the company like most intent tools. Used to build outbound lead lists from inbound traffic.

Last verified: May 2026


Quick Reference​

FeatureDetail
IdentificationPerson-level (name, email, LinkedIn, title)
Company dataCompany name, industry, size, revenue estimate
Engagement dataPages visited, visit timestamps, referrer, all-time views
ExportCSV export (custom report)
CRM integrationVia CSV → Python import pipeline into TwentyCRM
CostFree tier available; paid plans for higher volume
AccessClient-specific accounts — no central Pacing login

Overview​

RB2B tracks website visitors and de-anonymises them at person level using LinkedIn and partner identity graphs. Unlike company-level tools (Clearbit, Leadfeeder), it returns individual people — useful for direct outreach without needing a separate prospecting step.

The export contains two profile types in a single CSV:

  • Person rows — individual visitor with name, job title, email, LinkedIn URL, and the company they work at
  • Company rows — identified company with LinkedIn company URL, industry, size, revenue estimate, but no individual contact

Both types include engagement data: pages visited, view counts, first/last seen timestamps, referrer, and RB2B tags (e.g. "Hot page").


Data Fields​

CSV ColumnTypeDescription
LinkedInUrlURLPerson's LinkedIn profile or company LinkedIn page
FirstName / LastNameTextPerson name (Person rows only)
TitleTextJob title (Person rows only)
CompanyNameTextEmployer / company visited from
WorkEmailEmailWork email (Person rows only, where available)
WebsiteURLCompany website
IndustryTextIndustry category
EstimatedEmployeeCountRangeHeadcount bucket (e.g. 51-200, 5001+)
EstimateRevenueRangeRevenue estimate (e.g. $1M - $5M)
City / State / ZipcodeTextLocation
AllTimePageViewsNumberTotal page views across all time
RecentPageCountNumberPage views in recent window
RecentPageUrlsJSON arrayList of visited URLs (recent)
LastSeenAt / FirstSeenAtDatetimeVisit timestamps
MostRecentReferrerURLWhere they came from (e.g. Google, LinkedIn)
TagsJSON arrayRB2B-assigned tags (e.g. ["Hot page"])
FilterMatchesJSON arrayFilter rules this lead matched
ProfileTypePerson / CompanyRow type

TwentyCRM Integration​

RB2B exports are imported into TwentyCRM via a Python pipeline. The pipeline:

  1. Reads the CSV and splits rows by ProfileType
  2. Creates custom fields on person and company objects (one-time setup)
  3. Imports all companies first (creates stubs for companies referenced by persons but not in company rows)
  4. Imports all persons, linked to their company
  5. Scores and stages a shortlist of top opportunities
  6. Attaches a "Next Steps" checklist note to each opportunity

Custom fields created in TwentyCRM​

These fields are added to both person and company objects, and to opportunity:

Field nameTypeSource
industryTextIndustry
estimatedRevenueTextEstimateRevenue
allTimeViewsNumberAllTimePageViews
recentPageViewsNumberRecentPageCount
lastSeenAtDateTimeLastSeenAt
firstSeenAtDateTimeFirstSeenAt
leadTagsTextTags
leadReferrerTextMostRecentReferrer
visitedPagesTextRecentPageUrls (deduplicated)
score (opportunity only)NumberCalculated (1-10)

Lead scoring (1-10)​

SignalPoints
Base2
All-time views â‰Ĩ 5+1
All-time views â‰Ĩ 15+2
All-time views â‰Ĩ 30+3
All-time views â‰Ĩ 50+4
Recent views â‰Ĩ 3+1
Recent views â‰Ĩ 10+2
"Hot page" tag+2
Has work email+1
Max10

Pipeline stages assigned on import​

StageCondition
MEETING"Hot page" tag AND (has email OR views â‰Ĩ 20)
SCREENINGHas email OR all-time views â‰Ĩ 10
NEWEverything else

Import Scripts​

Scripts live in scripts/resources/rb2b/. Run from workspace root.

Prerequisites​

# API key for the target TwentyCRM workspace (not the Pacing agency workspace)
# Add to root .env:
RB2B_TWENTYCRM_API_KEY=your-client-workspace-token
RB2B_TWENTYCRM_API_BASE=https://pacingagency.com/rest

1. Import companies and people​

python3 scripts/resources/rb2b/rb2b-import.py \
--csv ~/Downloads/filtered_custom_report_XXXXXXXXX.csv

Creates all companies and people from the CSV. Custom fields are created automatically on first run if they don't exist.

2. Create top-N opportunities​

python3 scripts/resources/rb2b/rb2b-opportunities.py \
--csv ~/Downloads/filtered_custom_report_XXXXXXXXX.csv \
--top 10

Scores all leads, selects the top N, creates opportunities with stage and score, and adds a "Next Steps" checklist note to each.

3. Add notes to existing opportunities (if needed)​

python3 scripts/resources/rb2b/rb2b-notes.py

Idempotent — skips opps that already have a note.

See scripts/resources/rb2b/README.md for full documentation.


Automation Opportunities​

The current pipeline is manual (export CSV → run scripts). Potential next steps:

Near-term (low effort)​

  • Zapier / n8n webhook: RB2B supports webhook output — route directly to TwentyCRM REST API without a CSV step
  • Scheduled import: Trigger n8n on a schedule to pull RB2B webhook data and upsert into TwentyCRM

Medium-term​

  • Lead enrichment: After import, enrich company records with Apollo.io or Clay before scoring
  • Automated email sequences: High-scoring leads (â‰Ĩ7) trigger an n8n workflow that sends a personalised cold email via Resend or Notifuse
  • LinkedIn audience sync: Export scored leads to a CSV matched against LinkedIn Matched Audiences for retargeting
  • Slack alert: n8n notifies a Slack channel when a score-10 lead appears

Architecture sketch (fully automated)​

RB2B webhook → n8n workflow
├── Upsert person + company in TwentyCRM
├── Score lead (views + tags + email)
├── If score â‰Ĩ 7 → create opportunity + note
├── If score â‰Ĩ 8 → send cold email via Resend
└── If score â‰Ĩ 9 → Slack alert to sales channel

Account Access​

  • Access: Client-specific — each client has their own RB2B account at app.rb2b.com
  • Script pixel: Embedded on client website via GTM or direct
  • Exports: Settings → Reports → Custom Report → Export CSV

  • tools/twentycrm.md — target CRM for imports
  • tools/n8n.md — automation platform for future webhook pipeline
  • tools/notifuse.md — email delivery for automated outreach sequences
Note Context

Importance Rating: Medium — useful for client outbound lead pipelines, not mission-critical infrastructure.

Focus Areas for Note:

  • Person-level identification is the key differentiator vs company-level tools
  • The import pipeline (CSV → TwentyCRM) is the current workflow; full automation via n8n webhook is the target state
  • Scripts are reusable across client workspaces — the token and CSV path are the only things that change

Additional Context:

  • No central Pacing account — each client has their own RB2B pixel and account
  • The working/ folder in the workspace root contains run-specific logs (gitignored)

Last Updated: May 2026 Owner: Ben Power Status: Active (manual pipeline) — automation in planning