Understanding how the Hubspot connector affects MAR
Hubspot Connector MAR Overview
- Fivetran’s Hubspot connector delivers data from both the Hubspot Marketing and Sales/CRM tables. For reference, Fivetran provides entity relationship diagrams for each of these data relationships which are linked to above.
What Contributes Towards MAR?
There are 5 primary actions that will contribute toward MAR:
- Size of the Hubspot account source data set
- Hubspot API constraints regarding deleted data - Our HubSpot connector re-syncs several tables every day because the HubSpot API does not offer a mechanism to capture deletes. By re-syncing these tables, we can infer deletes. Learn more in our HubSpot documentation around the tables we infer deletes from and their update frequency. These re-syncs increase consumption for HubSpot.
- The important contact_property_history table is a typical significant driver of MAR delivered to the destination due to its size.
- Syncing tables which contain data that may not be useful for your analysis from the configurable Hubspot schema page in the Fivetran UI
Managing MAR for this Connector
- Before running your first historical sync, we recommend that you review the tables included in the standard Hubspot schema that Fivetran will create in the destination in the Schema page of the Fivetran UI. In the schema page, you can block any tables containing data that you do not need. This can help keep your MAR quantity down.