RB2B uses cookies to identify website visitors and deliver its core functionality. This article covers what cookies RB2B sets, what data they contain, how long they last, and what you need to know for compliance purposes.
What RB2B cookies are used for
When the RB2B tracking script is installed on your website, it sets first-party cookies in the visitor's browser. These cookies are used to:
Recognise returning visitors across sessions
Maintain session continuity during a single visit
Store attribution data (referring URLs)
Support RB2B's person-level identity resolution process
RB2B cookies are not used for advertising, behavioural profiling, or any purpose outside the RB2B identification platform.
Cookie reference
Cookie name | Expiration | Purpose | Data stored |
| 20 days | Location-based identification and matching | Visitor geolocation |
| 1 second | Prevents duplicate script executions | Script load status flag |
| 15 days | Visit attribution | Referring URL |
| 30 minutes | Active session management | Temporary session identifier |
| 360 days | Persistent visitor identification | Unique visitor ID |
| 1 month | Internal identification framework | Internal tracking data |
| 1 month | Identity resolution | Visitor resolution data |
| 1 month | Session-to-identity linking | Internal record linkage data |
| 2 days | Temporary identity resolution buffer | Visitor data pending resolution |
| 1 year | Long-term cross-session identification | Persistent unique token |
Data and privacy
Do these cookies contain PII?
No. None of the cookies above store personally identifiable information such as names, email addresses, or phone numbers.
Are these first-party or third-party cookies?
All RB2B cookies are first-party cookies, set under your website's own domain, not a third-party domain.
Is data shared with third parties?
RB2B cookies do not transmit data to advertising networks or third-party data brokers. Data collected is used solely within the RB2B platform for visitor identification.
Where is cookie data stored?
Cookies are stored in the visitor's browser under your website's domain.
Are these cookies required for RB2B to function?
Yes. These cookies are required for company- and person-level visitor identification. Blocking or delaying them will degrade or prevent identification accuracy.
Cookie consent and classification
If your website uses a consent management platform (such as CookieYes, OneTrust, or similar), classify RB2B cookies as functional or essential cookies. This ensures they can be set prior to user consent where your policy permits, and that they are included in your cookie disclosure.
Cookies to declare in your consent configuration: _reb2bgeo, _reb2bloaded, _reb2bref, _reb2sessionID, _reb2buid, _reb2bfxf, _reb2btd, _reb2bli, _reb2bresolve, _reb2butk
Compliance
Website owners are responsible for ensuring their use of RB2B complies with applicable privacy and data protection law, including GDPR, CCPA, and any other regional regulations that apply to their user base. If your jurisdiction requires cookie disclosure or user consent, include the cookies listed above in your privacy policy and cookie notice.
Quick reference for security reviews
Question | Answer |
Cookie type | First-party only |
PII in cookies | None |
Advertising use | None |
Third-party data sharing | None |
Cookies required for core function | Yes |
Longest-lived cookie |
|
Total cookies set | 10 |