RB2B Integration: Person-level Website Visitors

What you get

1,000 identified people per month included for Pocus customers
Ability to purchase additional identification credits as needed
Simple enablement: ask your Customer Success team to toggle RB2B on for your workspace

Installation

Add the standard Pocus snippet from your Integrations page in the Pocus platform. When your CS team enables RB2B for your workspace, a second script for RB2B will be included automatically. If you manage scripts manually, you'll need to include both scripts as shown in the example structure below.

&lt;!-- Pocus base snippet - Use exact code from your Pocus Integrations page --&gt;
&lt;script
  src="&lt;your-pocus-script-url&gt;"
  data-pocus-project-id="your-unique-project-id"
  async
  defer
&gt;&lt;/script&gt;

&lt;!-- RB2B person-level add-on (appears when RB2B is enabled) --&gt;
&lt;script
  src="&lt;!-- RB2B script URL provided by Pocus/RB2B on enablement --&gt;"
  data-rb2b-key="your-rb2b-key"
  async
  defer
&gt;&lt;/script&gt;

If you deploy via Google Tag Manager, mirror the above by appending the RB2B script creation after the Pocus script in your tag. Always use the exact snippet from your Pocus Integrations page, not this example.

🇺🇸
RB2B person-level identification is limited to visits originating from US IP addresses.

🔒
In addition to restricting where the scripts run, you can limit person-level visit identification to specific URLs and wildcards (for example, /pricing/, /blog/). Provide the exact allowlist patterns to your Pocus CS team and we’ll configure the RB2B identification scope accordingly.

How it works

RB2B resolves eligible visitor events to known people using their identification graph and consent-aware matching. For the detailed flow, thresholds, and matching logic, refer to RB2B’s documentation:

Getting started[1]
Web SDK / implementation details[2]
Identification and matching FAQs[3]

Pocus ingests the RB2B-resolved identities alongside your company-level visit data, unlocking person-level insights and downstream routing in Pocus.

Privacy, consent, and policy updates

🚧
When enabling person-level resolution, review and update your public-facing privacy policy and consent flows as required by your legal team. RB2B provides guidance on GDPR and CCPA implications and recommended disclosures.[4]

Key points to align with your counsel:

Default without RB2B remains company-level insights only
With RB2B enabled, person-level processing should reflect your stated purposes and lawful bases
Honor regional consent requirements and opt-outs

Troubleshooting

Not seeing person-level identities after enablement? Confirm RB2B is toggled on by your CS team, that your domain is in-scope per RB2B docs, and that ad-blockers are not suppressing the RB2B script
Identification counts lower than expected? Review RB2B’s match prerequisites and consent requirements in their docs[6][7]