# RB2B: visitor identity and plan limits

Assess RB2B visitor identification, US coverage and plan limits before buying.

Canonical page: https://quillwell.com/guides/software/rb2b/
Updated 2026-10-31
Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/

## The short answer

- Consider RB2B when your team needs person-level signals from eligible US visitors and can verify the results.
- [RB2B’s pricing table](https://www.rb2b.com/pricing) identifies companies globally; its Free plan includes 150 monthly resolutions.
- RB2B Starter includes LinkedIn URLs; Pro adds email and integrations.
- Consider Snitcher when company-based pricing and account prioritization fit your workflow.

## Choose the identity before the plan

Start with the action a sales team will take. A matched company can guide account research; a person-level result needs evidence that the person actually visited.

[RB2B’s pricing table](https://www.rb2b.com/pricing) describes global company-level identification and US-only contact-level identification. Free identifies companies, Starter adds LinkedIn URLs, and Pro adds email addresses and integrations.

For example, a known US test visitor may produce a person-level record while another visit produces only a company. Record each outcome separately and compare it with the independently known visit.

A sales team should preserve the identity type with the record. A company match can support account prioritization without proving which employee visited.

## Read coverage against its population

Coverage depends on who is counted and what qualifies as a match. Use the published figures to frame a trial rather than forecast all your site traffic.

RB2B’s [how-it-works article](https://support.rb2b.com/en/articles/8891294-what-is-rb2b-and-how-does-it-work) claims 40–45% person-level and 30–35% company-level coverage for qualified US traffic. Its [visitor profile FAQ](https://support.rb2b.com/en/articles/11662812-visitor-profile-faqs) separately claims 70–80% US contact-level identification.

The sources use different denominator wording and do not reconcile the figures. Ask RB2B to define qualification and the FAQ population before using either claim in a forecast.

In your own trial, count correct matches and incorrect identifications; include no matches against the same eligible known-visit cohort. Report company and person outcomes separately.

## Price the required fields

Choose a plan for the fields and handoff your team will use. A starting price cannot tell you how much of your traffic will resolve.

[RB2B pricing](https://www.rb2b.com/pricing) lists Starter at $79/month and Pro starting at $149. The Free plan includes 150 monthly resolutions, while Pro volumes are controlled dynamically.

Starter includes LinkedIn URLs but no email addresses; Pro adds email and integrations. Obtain capacity and terms for your expected workload before comparing a quote with a company-based subscription.

A resolution and a unique company identified in a month are different units. Use the same expected audience and required fields when requesting prices.

## Set up consent and preserve context

Agree on the consent configuration before collecting the test cohort. Include the consent outcome in the record used to interpret each result.

[RB2B’s setup guidance](https://support.rb2b.com/en/articles/8891294-what-is-rb2b-and-how-does-it-work) describes automatic consent gating with CookieYes and manual script gating for other consent managers. RB2B limits person identification to eligible US visitors.

Have the team responsible for your consent setup decide how to configure the trial. Test both consent outcomes under the settings your site will use.

[RB2B’s visitor profile FAQ](https://support.rb2b.com/en/articles/11662812-visitor-profile-faqs) places page-view history in the Activity panel. Obtain the export schema and retention terms before relying on that history for a handoff or migration.

## Test a usable result

A returned record is useful only if it is correct and supports an action your team intends to take. Run the same controlled visits through the intended handoff.