If a contact already exists in HubSpot CRM at the time of identification by RB2B, RB2B will pass the identification data to HubSpot CRM and update the contact accordingly.

HubSpot CRM supports creativity and innovation by letting anyone create apps or integrations with its platform. For your safety, HubSpot CRM gives you a heads-up if an app hasn’t been officially reviewed or verified by their team.

Currently, our HubSpot CRM integration at RB2B hasn't gone through HubSpot CRM's review process yet, which is why you see that message. We want to ensure you have all the information you need to use our services confidently.

Yes, RB2B will update previously sent contacts in HubSpot CRM to include recent page view activity should they return to your website.

Yes, RB2B's HubSpot CRM integration sends the contact's LinkedIn information if it was collected.

When RB2B updates an existing contact in HubSpot CRM with information identified by RB2B, it also tags the user as 'known' to indicate that they were a confirmed visitor to your website. In order to do that, RB2B must first check to see if the contact exists within your HubSpot CRM - hence the read access to that information.

This functionality exists purely so RB2B can tag the user within the dashboard or Slack notification as already being known to you via your CRM.

Once a user is tagged as being known to you in your CRM, you'll see them outlined in orange on your Profiles page and a 'CRM' tag will appear under their avatar.

A full list of all profile information available to be sent to HubSpot CRM by RB2B can be found at https://support.rb2b.com/en/articles/10138207-how-rb2b-s-hubspot-crm-integration-works

Unlike our now retired "HubSpot Marketing" integration, the "HubSpot CRM" integration does not tag leads as marketing leads by default. You'll find contacts submitted by RB2B labeled as "Non-marketing Contact" in your HubSpot contact list.

RB2B is designed to permit a single integration connection per account. For users integrating with HubSpot CRM, this means you can push data to only one selected HubSpot CRM instance of your choice.

This setup ensures a streamlined and efficient data flow between RB2B and HubSpot CRM, making it easier to manage and analyze your data within a singular, cohesive environment.

Yes, multiple RB2B accounts can be connected to the same HubSpot CRM account. This allows each RB2B account to push notifications of newly identified visitors directly into the shared HubSpot CRM.

This capability facilitates the consolidation of visitor data from different RB2B accounts into one central CRM system, enhancing your ability to manage and analyze leads effectively. It ensures that your team can access comprehensive visitor insights and notifications in one place, streamlining your engagement and follow-up processes.

RB2B integrates with HubSpot CRM via the crm.export API to pull specific, necessary information. Despite the broad capabilities of this API, RB2B ensures that only essential data is retrieved. The following information is extracted:

HubSpot CRM's crm.export API allows exporting records for all CRM data types, reflecting its broad scope. However, RB2B strictly limits the data pulled to what is necessary for its operations.

If HubSpot CRM introduces a more restrictive API, RB2B will promptly switch to that, minimizing data access to align with best practices for data privacy and security. Until then, RB2B continues to use the crm.export API responsibly, ensuring only essential information is collected.

No, the HubSpot CRM integration will only send net-new profiles that are identified the integration is successfully connected. Previously identified users will not be sent.