Once connected - RB2B creates a non-editable form aptly named RB2B Form within HubSpot CRM. RB2B uses that form to submit newly identified profiles to HubSpot CRM via an API call and properly link it to a cookie.

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

To disconnect your HubSpot CRM integration, navigate to Integrations from the sidebar menu. Locate HubSpot CRM among the integration options and select View Integration.

To disconnect RB2B from HubSpot CRM, click the Disconnect from HubSpot button or, click Close to abandon the process.

To change or re-authenticate your HubSpot CRM integration, navigate to Integrations from the sidebar menu. Locate HubSpot CRM among the integration options and select View Integration.

To change or re-authenticate your HubSpot CRM integration, click the Re-authenticate with HubSpot button or, click Close to abandon the process.

HubSpot supports creativity and innovation by letting anyone create apps or integrations with its platform. For your safety, HubSpot 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’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 to include recent page view activity should they return to your website.

RB2B's HubSpot CRM integration does not send the visitor's LinkedIn URL to HubSpot CRM at the present time.

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.

RB2B's HubSpot CRM integration matches data using email addresses and HubSpot cookies. When a visitor comes to the website, HubSpot places a cookie on their browser, even if their identity is unknown. If HubSpot doesn't recognize the user, we can still use this cookie to connect their activity to a profile in our system. Once the user is identified, past events tracked by the cookie are linked to their profile.

RB2B ensures that only profiles containing both a first and last name, along with an email address and the page on which the user was captured, are sent to HubSpot CRM. The inclusion of a LinkedIn URL is not a requirement for a user to be sent to HubSpot CRM, and RB2B does not transmit LinkedIn URLs to HubSpot CRM.

Key Points

RB2B tags visitor information sent to HubSpot CRM as marketing leads to effectively leverage the visitor's existing cookie information. This integration allows us to merge the visitor's traffic and history into HubSpot, providing a comprehensive view of their behavior.

If you use HubSpot to host your website or have installed the HubSpot tracking code, HubSpot sets several tracking cookies when a visitor lands on your site. These cookies help HubSpot understand visitor behavior better. RB2B can link the identified visitor information to these cookies, ensuring seamless tracking and a unified data flow into HubSpot.

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.