Factors’ RB2B integration deanonymizes website visitors at the person level. Once enabled, every identified visitor flows into Factors as a user, and their RB2B-enriched attributes (name, title, company, LinkedIn URL, work email, location, and more) become available as user properties across reports, segments, timelines, alerts, and workflows.

This article covers how to turn on the feature and how to use the enriched properties across the Factors platform.

RB2B enrichment is configured from the Integrations section under Settings.

Go to Settings → Integrations and locate Factors Visitor Identity Enrichment under the Factors Data section.
​

Click into the integration. Toggle Visitor Identity Enrichment to ON and confirm that RB2B is selected as the identification source.

Your monthly quota and usage are displayed at the bottom of the page.

Once enabled, RB2B will begin identifying eligible website visitors. Identified users and their enriched properties typically appear in Factors within a few minutes of the visit.

The following properties are ingested as user properties on identified visitors. Required fields will always have a value; optional fields may be null when RB2B does not have a match.

In Factors, these surface with an RB2B prefix (for example, RB2B First Name, RB2B Company LinkedIn URL, RB2B Title).

Once a visitor is identified, all enriched fields are available with the RB2B prefix under the Other category for event-based filters and are available across the following surfaces.
​

On any account, open the Timeline view and click into a anonymous user to open the More Details panel. RB2B properties appear under User Properties for anonymous and identified users alike, giving you person-level context on otherwise unknown traffic.

You can see who visited (name, title, company), how to reach them (work email, LinkedIn URL), and firmographics (revenue range, employee count, country) directly alongside their activity.
​

In the segment builder, RB2B properties are available inside event-based filters. While adding a filter under an event, click Select Property and search for RB2B to see the full list.
​

Typical uses include building segments of accounts that have had identified visitors with specific titles, segmenting by RB2B Company Country, or isolating users from companies above a revenue threshold.
​

RB2B properties are accessible inside Reports as event filter properties. While configuring an event in any analysis, click Select Property under the event’s where clause and search for RB2B.

You can filter event analyses (such as Website Sessions or Page Views) by RB2B Title, RB2B Company Name, RB2B Company LinkedIn URL, and other enriched attributes.

RB2B properties are also accessible to Factors Agents. When an agent uses the Account Journey tool to pull a user’s activity, the enriched RB2B fields (name, title, company, work email, LinkedIn URL, location) are included in the agent’s context — so the agent can summarise identified visitors with person-level detail rather than just an anonymous user record.
​

​

RB2B properties can be used in real-time alerts in two ways:

RB2B properties are available inside Workflows as filter properties — you can scope a workflow to fire only when certain RB2B attributes match.

Note: RB2B properties cannot be sent as part of a workflow payload to downstream destinations. If you need to push RB2B details into a CRM or other system, use Real-time Alerts (which support payload inclusion) instead.
​

No. RB2B identifies a subset of US-based B2B visitors whose digital identity can be resolved. International coverage is limited.

RB2B identification applies from the moment the integration is enabled. Visits before activation are not enriched retroactively.
​

Yes — RB2B properties are user properties and can be used as filters in any event-based report, including attribution analyses.
​