Skip to main content

Controlling Company-Level Visitor Identification for Individual Integrations

Updated yesterday

In RB2B, controlling how your identified visitor data is shared across integrations is both flexible and straightforward. While there is no global toggle to manage the flow of Company-Level identified visitors across all integrations at once, each integration comes with its own individual setting to enable or disable this functionality.

How It Works

Each integration you connect to RB2B has the option to receive or ignore Company-Level identified visitors. This setting is available directly within the configuration panel for each integration.

If you choose to toggle the setting ON, that specific integration will begin receiving Company-Level profiles—including key details about companies identified through your website traffic, such as industry, size, and location (when available).

If the setting is toggled OFF, the integration will not receive any Company-Level profiles, regardless of what is being captured by RB2B elsewhere in your account.

Why This Matters

  • Granular Control: You can customize data sharing on a per-integration basis to align with your privacy preferences, data policies, or specific use cases.

  • Improved Targeting: Enable Company-Level data only for the integrations where it's actionable—such as your CRM or account-based marketing tools—while disabling it for others that don't require it.

  • Compliance Flexibility: For teams working under strict data governance or with region-specific restrictions, this level of control helps ensure data is only sent where it’s permitted.

How to Update the Setting

  1. Navigate to the Integrations section of your RB2B dashboard.

  2. Select the integration you want to configure.

  3. Locate the "Send company-only profiles" setting.

  4. Use the toggle to enable or disable as needed.

  5. Save your changes.

These settings can be adjusted at any time, giving you full control over how RB2B shares identified visitor data with each platform in your stack.

Did this answer your question?