RB2B relies on cookies to function correctly and identify website visitors accurately. These cookies enable features such as session tracking, visitor identification, and attribution, which are essential for delivering core RB2B functionality.
Depending on your website’s cookie consent policy, you may be required to disclose information about RB2B cookies within your own cookie banner or policy documentation. This article lists the cookies RB2B sets, their purposes, and their expiration periods.
Overview
When the RB2B tracking script is installed on your website, it sets a number of first-party cookies in the visitor’s browser. These cookies store information used to recognize returning visitors, record attribution data, and maintain session integrity.
RB2B does not use cookies for advertising or behavioral tracking — they are used solely for identification and session processing within the RB2B platform.
RB2B Cookies and Their Purpose
Cookie Name | Expiration | Purpose |
| 20 days | Stores the visitor’s geolocation, used for location-based identification and matching. |
| 1 second | Tracks whether the RB2B script has successfully loaded to prevent duplicate executions. |
| 15 days | Stores the visitor’s referring URL to attribute visits correctly. |
| 30 minutes | Holds a temporary session identifier unique to the visitor for use during the active session. |
| 360 days | Stores a persistent, unique identifier used in RB2B’s person-level identification process. |
| 1 month | Used for internal tracking within RB2B’s identification framework. |
| 1 month | Stores data related to RB2B’s identity resolution process for the visitor. |
| 1 month | Used to link the visitor’s browser session to RB2B’s internal identification records. |
| 2 days | Temporarily stores visitor information while RB2B’s identity resolution process completes. |
| 1 year | Stores a long-term unique token for persistent visitor identification across sessions. |
Implementation Notes
All RB2B cookies are first-party cookies, meaning they are stored under your website’s domain rather than a third-party domain.
None of these cookies contain personally identifiable information (PII).
These cookies are required for RB2B to perform company- and person-level visitor identification.
If your site uses a cookie consent manager (e.g., CookieYes, OneTrust, or similar), ensure that RB2B cookies are classified as “essential” or “functional” cookies so that they can be set before consent is granted when necessary.
Blocking or delaying these cookies may prevent RB2B from accurately identifying visitors.
Compliance Reminder
Website owners are responsible for ensuring that their use of RB2B cookies complies with applicable privacy and data protection laws (such as GDPR, CCPA, or similar regional regulations).
If your organization operates in a jurisdiction that requires cookie disclosures or user consent, include RB2B cookies in your policy documentation accordingly.
Summary
RB2B cookies are a vital component of the visitor identification process. They help maintain session continuity, track referrals, and enable accurate company- and person-level recognition without collecting personal data.
By ensuring these cookies are permitted and disclosed properly, you can maintain compliance while enabling RB2B to deliver accurate visitor insights.