RB2B identifies site visitors using an identity data layer built and maintained by Retention.com, RB2B's parent company. It's the same underlying data that powers RB2B's Slack alerts and CRM pushes.
That data layer covers more than what shows up inside the RB2B app. If you want it directly — via API, warehouse delivery, or flat file — it's available outside the RB2B app itself.
Three paths, depending on how you want to consume it.
Self-serve access to the identity data RB2B runs on, across a broad set of endpoints covering identity resolution, enrichment, and more. Built for teams that want to call the data directly from their own product or workflow.
Talk to us about API access →For teams that want the data delivered on a recurring basis directly into your data warehouse, rather than called record-by-record. This is the right fit if you're enriching at scale, building suppression lists, or feeding the data into your own models.
Talk to us about direct integration →For teams that want identity, enrichment, and intent data delivered as a recurring file or data feed, rather than through an API or live warehouse connection — a fit for large-scale, enterprise use cases as well as lighter-weight, one-off needs.
Talk to us about direct integration →For teams vetting this before turning it on.
SOC 2 Type II certified
Data Services Agreement, Data Usage Terms, DPA, and InfoSec Addendum available on request
CCPA/CPRA and GDPR posture documented, consistent with RB2B's compliance scope
Database and CCPA opt-outs published and honored