Skip to main content

RB2B Visitor Identification

Syft's RB2B integration increases contact-level identification rates by up to 40% by adding RB2B as another data provider in Syft's visitor ID waterfall. When enabled, the Syft website tag can use RB2B as an additional contact identification source for US-based business visitors, then attach that identity to the visitor's website activity in Syft.

What it does​

RB2B helps Syft turn more anonymous website activity into person-level contacts your team can act on by adding another contact ID source to Syft's existing identification waterfall.

When Syft identifies a visitor through RB2B, Syft can:

  • Create or update the visitor's contact profile with RB2B identity data.
  • Connect the identified person to their browsing sessions and intent signals.
  • Show the contact as first identified by RB2B.
  • Let you use Syft AI and filters to find RB2B-identified visitors.
  • Trigger motions such as Slack alerts, CRM creation, enrichment, and LinkedIn connection requests when the visitor matches your criteria.

RB2B is another contact identification source inside Syft's visitor ID waterfall. You still use Syft for visitor timelines, account context, ICP and persona matching, intent analysis, motions, CRM sync, and usage reporting.

Turn it on​

  1. Go to Data Collection under Settings.
  2. Find Include RB2B Visitor ID.
  3. Turn the toggle on.
  4. Review and accept the RB2B add-on terms if prompted.
  5. Copy the updated Syft tag. The new tag uses the RB2B-enabled Syft bundle.
  6. Replace the existing Syft tag on your website with the updated tag.
  7. Remove any standalone RB2B script from your website or tag manager.
  8. If your site uses a Content Security Policy, update it to allow the Syft and RB2B-enabled tag resources. See Content Security Policy support.

Running the standalone RB2B script and the RB2B-enabled Syft tag at the same time can cause data loss or inconsistent visitor identification. Use the Syft tag as the single installation path.

Verify the installation​

After updating the tag, test the installation from Settings > Data Collection > Allowed Domains.

If the test says Syft is active but RB2B could not load, check the following:

  • The website is using the updated RB2B-enabled Syft tag.
  • Any old standalone RB2B script has been removed.
  • Your Content Security Policy allows the required Syft domains.
  • The tag is installed on the same domain that is listed in Allowed Domains.

New RB2B-sourced identifications appear as Syft's visitor ID waterfall matches eligible visitors. It is normal not to see contacts immediately if no eligible visitor has been identified yet.

Find RB2B-identified visitors​

You can find visitors first identified through the RB2B source in a few ways:

  • Open a contact or visitor profile and look for the RB2B identity source label.
  • Ask Syft AI for visitors identified through RB2B, de-anonymized visitors, or website visitors.
  • Filter contacts by First identified by and select RB2B.
  • Build a motion that targets visitors identified through the RB2B source together with ICP, persona, intent, page-view, or company filters.

For example, you can ask Syft AI:

Show me visitors identified through RB2B from the last 30 days with high intent.

Or:

Create a motion for visitors identified through RB2B who viewed pricing and match our buyer persona.

Billing​

RB2B uses your Syft credits. You do not need to buy or manage a separate RB2B subscription through Syft.

RB2B-sourced identification is billed as a Signal Credit:

  • RB2B Contact Identification: 2 credits per unique RB2B-identified contact per month.
  • If you later activate that contact with a motion, the normal contact activation charge applies separately.
  • RB2B-sourced identification credits and activation credits are independent.

You can monitor usage in Plan & Billing. If RB2B is paused because your account has reached its credit limit, the Data Collection page will show a paused message.

See Credits & Usage for the full billing model.

FAQ​

How is this different from running RB2B directly?​

With the Syft integration, RB2B acts as another data provider in Syft's visitor ID waterfall. That means RB2B-sourced identity data is combined automatically with Syft's session timelines, account records, ICP and persona logic, AI search, motions, CRM sync, and billing dashboard.

You should not run RB2B directly alongside the RB2B-enabled Syft tag. Use the Syft tag so tracking and identity stitching stay consistent.

Does RB2B replace Syft identification?​

No. RB2B adds another person-level identification source to Syft's visitor ID waterfall. Syft can still identify visitors through first-party tracking, form capture, signups and logins, personalized links, CRM data, and Syft's other de-anonymization sources.

Which visitors can RB2B identify?​

RB2B is intended for US-based business visitors. Identification rates depend on visitor eligibility, available data, consent and privacy controls, and the visitor's browser or network environment.

Do I need to install a separate RB2B script?​

No. After enabling the integration, install the RB2B-enabled Syft tag from Data Collection. Remove any standalone RB2B script from your site or tag manager.

Can I run the RB2B script in parallel with the Syft tag?​

No. Running the standalone RB2B script alongside the RB2B-enabled Syft tag can cause the two tags to interfere with each other's data collection. This can lead to incomplete tracking, data loss, or inconsistent visitor identification in Syft.

Do I need to update my privacy disclosures?​

Yes. The enablement flow notes that RB2B visitor de-anonymization may require updates to your privacy policy, privacy choice links, and handling of Global Privacy Control signals. Review the RB2B Add-on Addendum and consult your legal team for your specific obligations.

What happens if I turn it off?​

Syft unregisters your allowed domains from RB2B and your Syft tag returns to the standard bundle after you update the tag on your website. Disabling stops further RB2B collection, but it does not delete data already in RB2B's graph.

Why don't I see RB2B contacts yet?​

Confirm that the RB2B-enabled Syft tag is installed, your allowed domain test passes, and your CSP is not blocking the script. If setup is correct, wait for eligible traffic. RB2B-sourced contacts appear only after Syft's visitor ID waterfall identifies an eligible visitor through RB2B.