HubSpot is an inbound marketing software platform that helps companies attract visitors, convert leads, and close customers. Visit Website
Take your company’s analysis to the next level by adding Hubspot as a Source to Segment. We’ll automatically collect events like
Form Submissions and objects such as
Email Campaigns and load them into your data warehouse.
From your workspace’s
Give the source a nickname and a schema name. The nickname will be used to designate the source in the Segment interface, and the schema name is the namespace you’ll be querying against in your warehouse. Both can be whatever you like, but we recommend sticking to something that reflects the source itself, like
Hubspotfor nickname and
hubspot_prodfor the schema name.
Note that you can add multiple instances if you have multiple Hubspot accounts. That’s why we allow you to customize the source’s nickname and schema name!
Finally, connect an account with admin API permissions to access your Hubspot data. This account should be an active user on a Professional or Enterprise plan. Check out Hubspot’s docs on how to get your API Key.
Voila! We’ll begin syncing your HubSpot data into Segment momentarily, and it will be written to your warehouse at your next Warehouse run.
Hubspot has a sync component, which means we’ll make requests to their API on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we’ll grab all the Hubspot objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance’s schema name you designated upon creation. For example, if you went with
contacts collection will be accessible at
hubspot_prod.contacts in SQL.
Our sync component uses an upsert API, so the data in your warehouse loaded via sync will reflect the latest state of the corresponding resource in Hubspot. For example, if
inactive between syncs, on its next sync that tickets status will be
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
At the moment, we don’t support filtering which objects or properties get synced. If you’re interested in this feature, please let us know!
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
Due to HubSpot’s API Rate Limits, by default, the HubSpot source only syncs the past month of data for
email_subscription_event_changes. If you need more, just let us know, and we’ll arrange a one-off run to pull further history.
|contacts||Object||Contacts represent people in an Organization’s address book. For more info, check out HubSpot’s API docs|
|contact_identity_profiles||Object||Contact identity profiles represent identities of a contact.|
|contact_identities||Object||Contact identities represent communication methods for a contact’s profile (email, lead, etc.).|
|form_submissions||Event||Form submissions represent input from contacts in forms created via HubSpot|
|deals||Object||Deals for HubSpot CRM.|
|contact_lists||Object||Contact lists are lists of contacts in an Organization’s address book. For more info, check out HubSpot’s API docs about the resource|
|companies||Object||Companies visible to the portal in the HubSpot CRM. For more info, check out HubSpot’s API docs about the resource|
|email_campaigns||Object||Email campaigns for marketing automation. For more info, check out HubSpot’s API docs about the resource|
|email_events||Event||Email events based on user actions. For more info, check out HubSpot’s API docs about the resource|
|email_subscriptions||Object||Email subscriptions of campaign contacts.|
|email_subscription_event_changes||Event||Email subscription event changes represent changes to a recipient’s subscription that came about as a result of an email event|