Walkthrough

How to Set Up RB2B: A Visitor Identification Walkthrough

Tom Regan·Founder & GTM Strategist, Artemis GTM·8 min read·Updated Nov 12, 2026

Quick Answer

Set RB2B up in a fixed order: install its script in your site header, define your ICP as Hot Leads and require every criterion to match, mark your high-intent URLs as Hot Pages, suppress customers and competitors, then connect Slack and your CRM filtered to those tags. Compare the best visitor identification tools before you commit.

What does setting up RB2B involve?

Five stages, in order: install the script, define Hot Leads, mark Hot Pages, suppress the visitors you never want to see, then connect Slack and your CRM. Each stage filters the one after it. An RB2B alert stream is only as useful as the tags behind it, and none of it exists until the script is loading on your pages.

RB2B is a person-first website visitor identification tool: it matches individual US visitors to professional profiles and pushes the named person, their title, company and LinkedIn URL into Slack or your CRM. Affiliate link. This page is the install walkthrough. For how the matching works, read how website visitor identification works; if you are weighing it against a full platform, see the Warmly setup walkthrough for the same steps in Warmly.

Cite This

RB2B's person-level identification is US-only by design: it will not identify individuals located outside the US. Company-level identification is global, and RB2B says a consent collection tool is required to deploy it globally. Region is therefore a setup decision, not an afterthought.

RB2B FAQ: Pricing, Coverage, Compliance & Integrations

How do you install the RB2B script?

Copy the script from your RB2B account and add it to the header of every page you want tracked. RB2B's own instruction is a single line: install one script in your site header, per its FAQ. A site-wide header slot (or a tag manager tag set to fire on all pages) is the right place, because a script scoped to a landing page can only ever identify visitors on that landing page.

If you want to collect on a subset of pages on purpose, do it with RB2B's URL restriction rules rather than by scoping the script. RB2B notes that URL rules restrict only data collection, and the script's other functions stay active, per its filtering guide.

How do you define Hot Leads so the stream stays in-ICP?

Hot Leads is RB2B's name for ICP filtering: visitors who match your profile are tagged automatically, and the criteria cover company revenue, company size, seniority, department, category and geography, per the RB2B FAQ. The setting that matters most is the match threshold.

Define the ICP from wins, not guesses. Use the size bands, departments and seniority levels that show up in your closed-won deals. The method is in validating your ICP with closed-won data.
Require every criterion. RB2B's guide warns that if you define five ICP fields but require only one to match, many visitors will qualify. Set the tag to require all conditions.
Re-check it on a schedule. RB2B recommends validating the tagging periodically; a quarterly look at what the tag let through is enough for most teams.

Which pages should be Hot Pages?

Hot Pages are the high-intent URLs you mark so RB2B tags every visitor who views them, per the RB2B FAQ. Mark pricing, demo or contact, integrations and head-to-head comparison pages. Leave the blog off. A person who reads a guide is researching; a person on your pricing page is shopping, and that is the visit a rep should see first. The tiering logic is the same one used in deanonymized visitor outreach automation.

What should you exclude before any alert goes live?

RB2B gives you three suppression controls, and all three belong in place before Slack is connected:

Domain exclusion list. A visitor identified with an email from an excluded domain is skipped entirely and will not appear in your dashboard, reports or integrations, per RB2B's filtering guide. Add your own domain, your competitors and your current customers.
Page suppression. Exclude by domain, URL or list, so careers pages, the customer login and support docs never generate an alert.
URL restrictions. Collect only on the paths that matter if your site carries a lot of low-intent traffic.

The same exclusion logic, applied to scoring rather than alerts, sits in the fit layer of pain-first ICP scoring.

How do you connect RB2B to Slack?

Create the Slack channel first, then open Integrations in RB2B, select Slack, click Connect to Slack and authorize the workspace, and pick the channel when prompted, per RB2B's Slack setup guide. Be signed into only one Slack workspace while you do it. The integration posts to one connected channel, has a status toggle to pause it, a daily recap option, and a setting that alerts when a previously identified visitor returns.

Filter the Slack integration to your Hot Leads tag so the channel carries only in-ICP visits, then leave repeat-visitor alerts off until the first-visit stream is clean. Speed is the reason the channel exists: Harvard Business Review (Oldroyd, McElheran and Elkington, March 2011) reported an average first response to a web lead of around 42 hours, and a named US visitor on your pricing page is worth far more in the first few minutes than the next day. The routing SLA behind that is in speed-to-lead.

Should you sync RB2B into your CRM?

Yes, once the tags are trusted. On paid plans RB2B connects to HubSpot natively: from the Integrations tab you connect and authorize, and RB2B creates contacts with RB2B-specific properties such as last seen, referring URL and LinkedIn URL, and logs pageviews on the contact timeline, per its HubSpot integration playbook. Apply the same Hot Leads filter to the CRM integration as to Slack, so the CRM is not filled with records no rep will ever work. A customer or an open opportunity revisiting your site should be suppressed, not alerted as net-new.

RB2B handles the hardest part by design: person-level identification is US-only. Company-level identification is global, and RB2B says a consent collection tool is required if you deploy it globally. Artemis GTM's recommended default for any visitor identification stack is the same split: US traffic can run opt-out outreach with a working unsubscribe, rest-of-world traffic runs opt-in, and EEA, UK and Swiss traffic stays company-level only, so there is no person to enroll. Nothing here is legal advice; confirm the posture with counsel.

What are the most common RB2B setup mistakes?

Mistake	What it costs you	The fix
Script on one page only	RB2B can only identify visitors on pages that load it	Install it in the site-wide header
Hot Leads requires one criterion of five	Most visitors qualify and the channel floods	Require all conditions
No exclusion list	Customers, competitors and your own team ping reps	Exclude those domains before connecting Slack
Slack and CRM unfiltered	Every identified visitor becomes an alert and a record	Filter both integrations to the Hot Leads tag
Global company-level ID with no consent tool	A compliance gap RB2B itself flags	Add a consent collection tool or keep company-level ID US-only

Where Artemis GTM fits

Artemis GTM is an AI GTM engineering firm that builds GTM systems; it is not a data vendor. In an engagement it installs the RB2B script, writes the Hot Leads criteria from your closed-won data, marks the Hot Pages, builds the exclusion lists, wires Slack and the CRM sync filtered to those tags, and sets the region rules. Every record the setup touches stays in your own RB2B account, CRM and Slack; Artemis GTM holds no visitor data and resells none.

Frequently asked questions

What is the right order to set up RB2B?

Install the script in your site header first, because RB2B can only identify visitors on pages that load it. Then define your ICP as a Hot Leads tag and require all of its criteria to match, mark your pricing, demo and comparison URLs as Hot Pages, and add your customers, competitors and your own domain to the exclusion list. Connect Slack and your CRM last, filtered to those tags, so the first alert a rep sees is already an in-ICP, high-intent visit.

Does RB2B identify people outside the US?

No. RB2B states that its person-level identification is US-only and will not identify individuals located outside the US, for GDPR and CCPA compliance. Company-level identification is global through its Demandbase partnership, and RB2B says a consent collection tool is required if you deploy global company-level identification. Artemis GTM's recommended default matches that split: US traffic can run opt-out outreach, rest-of-world traffic runs opt-in, and EEA, UK and Swiss traffic stays company-level only. This is not legal advice; confirm the posture with counsel.

How do you stop RB2B Slack alerts from becoming noise?

Filter the integration to your Hot Leads tag instead of sending every identified visitor. RB2B's own guidance is that if you define five ICP fields but require only one to match, many visitors will qualify, so set the tag to require all conditions. Restrict collection to the URLs that matter, exclude domains you never want to see, and leave repeat-visitor alerts off until the first-visit stream is clean.

Can RB2B push identified visitors into HubSpot?

Yes, on its paid plans. RB2B connects to HubSpot natively from its Integrations tab, writes identified visitors as contacts with RB2B-specific properties such as last seen and LinkedIn URL, and logs their pageviews on the contact timeline. Filter that sync to your Hot Leads tag the same way you filter Slack, so only in-ICP records land in the CRM your reps work from.

What does Artemis GTM set up for an RB2B implementation?

It installs the script, writes the Hot Leads criteria from your closed-won data, marks the Hot Pages, builds the exclusion and suppression lists, wires Slack and the CRM sync filtered to those tags, and sets the region rules so non-US traffic stays company-level. All of it is built inside your own RB2B account, CRM and Slack during an engagement; Artemis GTM holds no visitor data and resells none. The scope and quote come from an evaluation call.

Sources & References

RB2B, "RB2B FAQ: Pricing, Coverage, Compliance & Integrations": US-only person-level coverage, global company-level coverage and its consent requirement, the header install, Hot Leads, Hot Pages and page suppression.
RB2B Help Center, "Quieting the Noise: How to Filter for Relevant Leads in RB2B" (May 2026): the Hot Leads match threshold, URL restrictions, the domain exclusion list and tag-filtered integrations.
RB2B Help Center, "Setup Guide: Slack" (March 2025): the connection steps, connected channel, daily recap and repeat-visitor settings.
RB2B Academy, "HubSpot x RB2B: Integration Playbook" (May 2025): the native HubSpot connection, contact properties and timeline events.
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads," Harvard Business Review (March 2011): the roughly 42-hour average first response to a web lead.

Not ready for an engagement?

If identified visitors who never reach a rep in time is the gap, the free guides let you price it in your own numbers before anyone builds anything. Start with the seven revenue leaks, then read The Engine Room to watch the systems getting built.

Done for you

Want this built inside your stack?

Artemis GTM is an AI GTM engineering firm that builds and runs outbound and inbound GTM systems for seed to Series C B2B startups, hands-on, in three to six months, with its own agent architecture, then hands the systems over. One evaluation call, a written scoping note, a custom quote.

Book an evaluation

Not ready for an engagement? Read The Engine Room, the build notes from inside the firm.