HubSpot

HubSpot is a system for managing customer relationships and storing data. You can use Hevo Pipelines to replicate data from your HubSpot account to the Destination database or data warehouse using HubSpot REST API.

You can use Open Authorization (OAuth) to authenticate your HubSpot account with Hevo.

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.


Source Considerations

  • HubSpot does not allow fetching deleted records based on a timestamp. While this can lead to a higher number of ingested Events, Hevo deduplicates such Events upon ingestion. Only the Events that were deleted after the last run of the Pipeline (based on the archived_at timestamp) count as new Events and are treated as billable.

  • Due to an open issue with Hubspot relating to the Contacts object, the exact time at which a contact was deleted or archived cannot be determined. For the archived_at timestamp, the HubSpot API returns the last updated_at timestamp instead of the actual deletion/archival time. Due to this, the last tracked deletion of Contacts data cannot be definitively identified, and Hevo must ingest all the deleted contacts and de-duplicate them while loading to the Destination. Therefore, it is always a full load of archived Contacts data, and these Events are included in your billable Events count.

    Read Announcing a new definition for the archivedAt endpoint response value.

  • HubSpot does not allow the capture of deletes in custom objects.

    Read Paging through deleted objects is not yet supported for custom objects.


Limitations

  • Hevo supports only the CRM API v3 to fetch HubSpot data. If any object or record does not support v3 endpoint such as Form, Hevo uses the legacy API to fetch or synchronize data with the Destination.

    Note: Refer the HubSpot API Docs to identify the API associated with the objects you want to ingest.

  • HubSpot CRM API returns the updates for up to 10,000 records for the same modified timestamp. If other records are updated at that particular point of time, they are not reflected or synchronized with the Destination.


See Also


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-21-2022 1.98 Updated sections, Data Model and Source Considerations to include information about custom objects.
Sep-05-2022 NA - Updated section, Data Replication to restructure the content for better understanding and coherence.
- Updated section, Configuring HubSpot as a Source to reflect the latest UI changes.
Apr-25-2022 1.87 Updated section, Limitations about Hevo using the CRM API v3 to fetch HubSpot data.
Nov-22-2021 1.76 In the Data Model section:
- Added the Owner object.
- Changed the description for the Email Campaigns object.
- Added a note to indicate that Email Campaign and Owner are Full Load objects.
Oct-25-2021 1.74 - Updated the page overview.
- Added the section, Source Considerations.
- Added information about handling of deleted records and the available Pipeline frequencies in the Data Replication section.
Aug-09-2021 1.69 Added a note in the Data Replication section about archived objects ingested from the Source.
Jul-12-2021 1.67 Updated the Data Model section with additional objects that Hevo now supports.
Last updated on 21 Sep 2022

Tell us what went wrong