1. Visitor Identity & Professional Profile
These details are derived from RB2B’s matching and enrichment process, using professional data sources such as LinkedIn and verified databases.
Full Name (First and Last)
Job Title – Current role or professional designation
LinkedIn Profile URL – Direct link to the visitor's public LinkedIn page
Business Email Address – A verified, professional email (when available)
RB2B prioritizes business email addresses whenever available. However, if the business email does not pass our internal validation tests—such as deliverability, formatting, or domain legitimacy—we may instead return a verified personal email as a fallback to ensure a usable point of contact.
Location Information:
City
State
ZIP Code
2. Company Affiliation
Provides insight into the visitor's employer or associated business.
Company Name – The name of the organization the visitor works for
Company Website – Direct URL to the company's official site
Industry Category – General sector or business classification (e.g., Software, Manufacturing, Healthcare)
Employee Count – Estimated size of the workforce
Estimated Annual Revenue – Based on public and proprietary data sources
3. On-Site Behavior & Visit Context
RB2B provides behavioral data tied to each qualified visitor session, offering insights into user intent and engagement.
Timestamp of Visit – Exact date and time when the visitor accessed your site
Referring URL – The webpage or source that directed the visitor to your site (e.g., search engine, LinkedIn, partner site)
Pages Visited / Page View History – A log of the specific pages the visitor viewed during their session, including the order and duration of each view.
This allows you to understand what content or offerings the visitor engaged with, helping to assess their level of interest and potential buying intent.
Note: All data is provided only after the visitor has passed RB2B’s initial qualification checks (such as U.S. geolocation and consent) and when a meaningful match has been achieved. Not every field may be populated in every case, depending on available signals and consent conditions.