This page describes how to use Census with HubSpot.
In this guide, we will show you how to connect HubSpot to Census and create your first sync.
- Have your HubSpot account ready.
Follow HubSpot OAuth flow to connect HubSpot. Your end state should look something like this below.
In the " What data do you want to sync?" section
- For the Connection, select the data warehouse you connected in step 2
- For the Source, select the model you created in step 3
Next up is the "Where do you want to sync data to?" section
- Pick HubSpot as the Connection
- For Object, pick the one you want to sync data to; Contact or Company.
For the " How should changes to the source be synced?" section
- Select your desired Sync Behavior from Update or Create, Update Only, or Mirror
- Pick the right mapping key, it could be Email for Contacts, Domain for Companies but we recommend you use your own internal id if possible
Finally, select the fields you want to update in the Mapper in the "Which Fields should be updated?" section
- Here simply map the field from your HubSpot instance to the column from your model.
The end result should look something like this
Click the Next button to see the final preview which will have a recap of what will happen when you start the sync
Now go back to your HubSpot and go view a record type (Contact or Company) that should have been updated. If everything went well, you should see your data in HubSpot
That's it, in just a few steps, you've connected Census to HubSpot and started syncing data from your warehouse to HubSpot 🎉
Census connects to HubSpot using their "Connected App" model, which are not subject to the daily HubSpot API call limit, only to the burst limit (100 requests/10 sec). Your Census syncs will not impact your HubSpot daily API limits or nor any other HubSpot integrations. For more information, see HubSpot docs.
Please be aware that with Custom Objects require extra API calls and are even slower as a result (about 1/3 the speed).
Custom Objects are available on HubSpot Enterprise plans.
As of March 2021, only properties in the searchableProperties set are usable as sync identifiers to HubSpot Custom Objects. This is a bit confusing as this label only appears in the HubSpot API. A searchable property can be added to a Custom Object via HubSpot's API. The calls to make this update can be found in HubSpot's Custom Objects API Docs > Object Schema Tab > searchableProperties.
If you need a hand making one of your existing Custom Object fields as searchable, please contact Census's Support team and we can walk you through it!
- They're supported between all HubSpot object pairs, including custom objects.
- They can represent one-to-many and many-to-many relationships.
- Associations can be labeled or unlabeled. HubSpot Professional and Enterprise plans also support custom labels.
Many-to-many associations can be updated in Census syncs on either side of the associations, while one-to-many associations can only be set on the child or many side.
Labels in HubSpot are a bit strange and Census provides some advanced configuration to make updating and removing labels a bit more straightforward.
When creating a labeled association between two objects in HubSpot, HubSpot will also automatically create an unlabeled association. Additionally, when creating an association from a contact to a company, HubSpot will create another association labeled Primary. That means that adding a labeled association with a Census sync may actually create up to three actual associations.
Unfortunately, HubSpot does not offer a way to remove these default associations when they're no longer necessary when removing the labeled association Census created. These associations may have actually been created intentionally so Census also cannot delete them automatically.
To navigate this, Census provides an advanced configuration for HubSpot syncs: Automatically clean up orphaned default associations when removing any associations.
When this behavior is enabled and a Census sync removes a labeled association, we'll also check to see if the remaining associations are only the unlabeled and Primary labeled associations, if so, we'll automatically remove those associations as well.
By default, this feature is not enabled to avoid accidentally deleting associations that were created outside the sync and should still exist.
You'll need to both create the event AND add all of the custom properties beforehand. Once you've done so, copy and paste HubSpot's internal name for object, you'll need to provide that to the
Event Nameproperty during the Census sync.
Note: The custom fields you've added will not show inside Census, you'll need to use the
New Custom Fieldoption to create the matching fields on Census, make sure they're named exactly the same (keep in mind, names are case sensitive!).
Census requires that the connecting HubSpot user have Super Admin permissions in order to access all supported HubSpot objects. If you have limited permissions and still want to connect Census to HubSpot, contact the contact the Census support team.