The Stack
RB2B
It only pays for itself above a certain amount of traffic and intent. Below that the economics do not work, however good the matching is.
- Category
- Website visitor identification
- Where the data sits
- In the United States
What you learn in the first month
An identification on its own is rarely the point. It is one input to a workflow: an ICP account returning to the pricing page after a proposal is a behaviour we can score and enrich further. On European traffic the person-level match is not there, so we work from company-level signals and enrich from the pages visited and the company size toward the roles most likely to matter. That is also the honest answer on geography. For a Europe-heavy campaign we would not pick this as the identification layer in the first place. And no identification tool catches every visitor, so if site traffic is thin the maths simply does not work.
We earn a commission if you sign up through some of the links on this page. What each tool teaches you is written from running it, and the hosting answer is the same whether we earn on it or not. Where there is no link, there is no programme we are part of.
Where the data sits
The United States. RB2B states that the service and website are hosted in the United States and that users outside the US consent to their personal information being transferred there. Its own documentation states that person-level identification activates only for visitors it can confirm are in the United States, with company-level identification for everyone else. No transfer mechanism is named.
Worth saying plainly: hosting outside the EU can still be GDPR compliant. It is not the same thing as EU data residency, and which one you need depends on who you sell to. What the law actually asks of you is a separate question with a separate answer.