Release Noteslink
November 2023link
We have updated the Quickstart packages for the following connectors:
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
October 2023link
We have added the following new tables to support the HubSpot Quotes API:
- QUOTE
- QUOTE_COMPANY
- QUOTE_CONTACT
- QUOTE_DEAL
- QUOTE_LINE_ITEM
- QUOTE_PROPERTY_HISTORY
These tables are available by default for all HubSpot connectors created after October 12, 2023. We are gradually rolling out these changes to all existing HubSpot connectors.
We have introduced the following schema changes for connectors created on or after October 17, 2023:
- We have upgraded to API v3 to sync the
TICKET_PIPELINE
,TICKET_PIPELINE_STAGE
,DEAL_PIPELINE
andDEAL_PIPELINE_STAGE
tables. - We have deprecated the
active
column for all the four tables mentioned above. - We have added a new column,
write_permissions
, to theTICKET_PIPELINE_STAGE
andDEAL_PIPELINE_STAGE
tables.
We are gradually rolling out these changes to all existing HubSpot connectors.
September 2023link
We now perform a weekly table re-sync to capture soft deletes for the CONTACT_LIST_MEMBER
table. We are gradually rolling out this feature to all existing connectors.
We have added the following new tables to support the HubSpot Web Analytics API:
GEOLOCATION_ANALYTICS_DAILY_REPORT
GEOLOCATION_ANALYTICS_MONTHLY_REPORT
GEOLOCATION_ANALYTICS_OVERALL_REPORT
GEOLOCATION_ANALYTICS_WEEKLY_REPORT
SESSIONS_ANALYTICS_DAILY_REPORT
SESSIONS_ANALYTICS_MONTHLY_REPORT
SESSIONS_ANALYTICS_OVERALL_REPORT
SESSIONS_ANALYTICS_WEEKLY_REPORT
SOURCES_ANALYTICS_DAILY_REPORT
SOURCES_ANALYTICS_MONTHLY_REPORT
SOURCES_ANALYTICS_OVERALL_REPORT
SOURCES_ANALYTICS_WEEKLY_REPORT
TOTALS_ANALYTICS_DAILY_REPORT
TOTALS_ANALYTICS_MONTHLY_REPORT
TOTALS_ANALYTICS_WEEKLY_REPORT
UTM_ANALYTICS_DAILY_REPORT
UTM_ANALYTICS_MONTHLY_REPORT
UTM_ANALYTICS_OVERALL_REPORT
UTM_ANALYTICS_WEEKLY_REPORT
We are gradually rolling out these changes to all HubSpot connectors.
July 2023link
We have changed our sync strategy for table properties. Now, depending on your table property selection in the Schema tab, we sync the property’s historical data to the associated property history table.
Now, in the connector’s Schema tab, if you deselect a property in the DEAL
table, we won’t sync the history data of the property to the DEAL_PROPERTY_HISTORY
table. Previously, we synced the property history data. The change in sync strategy impacts the following tables and the associated property history tables:
COMPANY
andCOMPANY_PROPERTY_HISTORY
CONTACT
andCONTACT_PROPERTY_HISTORY
DEAL
andDEAL_PROPERTY_HISTORY
ENGAGEMENT_CALL
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_COMMUNICATION
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_EMAIL
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_MEETING
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_NOTE
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_POSTAL_MAIL
andENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_TASK
andENGAGEMENT_PROPERTY_HISTORY
LINE_ITEM
andLINE_ITEM_PROPERTY_HISTORY
PRODUCT
andPRODUCT_PROPERTY_HISTORY
TICKET
andTICKET_PROPERTY_HISTORY
We have deprecated the following tables as HubSpot is sunsetting its Calendar API:
CALENDAR_EVENT
CALENDAR_TOPIC
CALENDAR_USER
May 2023link
We have added two new tables, ASSOCIATION_TYPE
and CONTACT_COMPANY
.
We have added two new columns, created_at
and updated_at
, to the following tables:
DEAL_PIPELINE
DEAL_PIPELINE_STAGE
PROPERTY
TICKET_PIPELINE
TICKET_PIPELINE_STAGE
We have added the show_currency_symbol
column to the PROPERTY
table.
We have added a new column, type_id
, to the following tables:
DEAL_COMPANY
DEAL_CONTACT
We have also included the type_id
column as a part of the composite primary key for these tables. You can use the type_id
column to identify primary associations.
These changes are available in all HubSpot connectors created after May 8, 2023. We are gradually rolling out these changes to the existing HubSpot connectors.
We have made the following schema changes to support HubSpot API v3:
We have added the following new tables:
ENGAGEMENT_COMMUNICATION
ENGAGEMENT_POSTAL_MAIL
ENGAGEMENT_PROPERTY_HISTORY
LINE_ITEM_DEAL
We no longer support the following tables:
ENGAGEMENT_PUBLISHING_TASK
ENGAGEMENT_EMAIL_BCC
ENGAGEMENT_EMAIL_CC
ENGAGEMENT_EMAIL_TO
We have deprecated the following tables:
ENGAGEMENT_EMAIL_BCC
ENGAGEMENT_EMAIL_CC
ENGAGEMENT_EMAIL_TO
The data from these deprecated tables will be available as columns in the
ENGAGEMENT_EMAIL
table. For more information, see HubSpot's Properties documentation.We have changed the primary key for a few
ENGAGEMENT_*
tables. The new composite primary key is a combination of theid
andtype
columns. Previously, theid
column was the primary key.To support the primary key change for older connectors, we have deleted the
ENGAGEMENT_*
tables and re-synced them.We have deprecated most of the existing columns of the
ENGAGEMENT_*
tables to standardize column naming conventions. We now sync the data only into the child tables'property_*
columns. Check your HubSpot connector dashboard for the properties for each engagement type. However, we won't be able to create the new columns if you have set the Block all option in the SCHEMA CHANGE SETTINGS.We have deprecated the columns of the
ENGAGEMENT
table. We now sync the data into the child table'sproperty_*
columns.We no longer support the following columns in the tables below:
Column Table object_type
TICKET
selected
LINE_ITEM_PROPERTY_HISTORY
deal_id
LINE_ITEM
To standardize the delete column, we have replaced the
is_delete
column with_fivetran_deleted
column for theLINE_ITEM
,TICKET
, andPRODUCT
tables. We will apply the changes to the older connectors as part of the migration.We have added a new table,
LINE_ITEM_DEAL
, to store data related to the association between line_item records and deal records.We have added a new column,
type_id
, to the following tables:ENGAGEMENT_DEAL
ENGAGEMENT_COMPANY
ENGAGEMENT_CONTACT
TICKET_COMPANY
TICKET_CONTACT
TICKET_DEAL
TICKET_ENGAGEMENT
We have added two new columns,
source
and,source_id
, to the following tables:LINE_ITEM_PROPERTY_HISTORY
PRODUCT_PROPERTY_HISTORY
These changes are available for all HubSpot connectors created after May 12, 2023. We are gradually rolling out these changes to all existing HubSpot connectors. See the HubSpot ERDs for more details.
We now use HubSpot API v3 to sync the following parent tables and their associated child tables:
ENGAGEMENT
ENGAGEMENT_CALL
ENGAGEMENT_COMMUNICATION
ENGAGEMENT_COMPANY
ENGAGEMENT_CONTACT
ENGAGEMENT_DEAL
ENGAGEMENT_EMAIL
ENGAGEMENT_MEETING
ENGAGEMENT_NOTE
ENGAGEMENT_POSTAL_MAIL
ENGAGEMENT_PROPERTY_HISTORY
ENGAGEMENT_TASK
LINE_ITEM
LINE_ITEM_DEAL
LINE_ITEM_PROPERTY_HISTORY
PRODUCT
PRODUCT_PROPERTY_HISTORY
TICKET
TICKET_COMPANY
TICKET_CONTACT
TICKET_DEAL
TICKET_ENGAGEMENT
TICKET_PROPERTY_HISTORY
New HubSpot connectors created on or after May 12, 2023, will support this feature by default.
We are gradually rolling out the changes to all existing connectors.
April 2023link
We now use HubSpot API v1 to sync the following deprecated columns of the CONTACT_FORM_SUBMISSION
table:
conversion_id
page_url
title
Previously, we had deprecated these columns for connectors syncing the parent CONTACT
table using API v3. This change only applies to HubSpot connectors created on or after November 11, 2022, or connectors that use API v3 to sync the CONTACT
table.
February 2023link
For connectors created after November 11, 2022, we have removed the sync dependency of the DEAL_STAGE
table on the DEAL_PROPERTY_HISTORY
table. To sync the DEAL_STAGE
table, you no longer need to select the DEAL_PROPERTY_HISTORY
table in the Schema tab. We are gradually rolling out this improvement for connectors created before November 11, 2022.
November 2022link
We now name custom object association tables using the format, [FROM_SCHEMA_NAME]_TO_[TO_SCHEMA_NAME]
.
The composite primary keys for the custom object association tables are the from_id
, to_id
, and type
fields.
We will re-sync all the existing custom object association tables to reflect the changes.
We now use version HubSpot API v3 to sync the following parent tables and their associated child tables:
DEAL
DEAL_STAGE
DEAL_CONTACT
DEAL_COMPANY
DEAL_PROPERTY_HISTORY
MERGED_DEAL
CONTACT
CONTACT_PROPERTY_HISTORY
CONTACT_FORM_SUBMISSION
COMPANY
COMPANY_PROPERTY_HISTORY
New HubSpot connectors created on or after November 11, 2022, will support this feature by default. We are gradually rolling out this improvement to all existing connectors.
For HubSpot connectors created on or after November 11, 2022, we have made the following schema changes:
We no longer support the following tables:
CONTACT_IDENTITY_PROFILE
CONTACT_MERGE_AUDIT
IDENTITY_PROFILE_IDENTITY
NOTE: The
property_hs_calculated_merged_vids
column of theCONTACT
table stores the contact merge data.In the
CONTACT_FORM_SUBMISSION
table, we:- no longer support the
conversion_id
,page_url
, andtitle
columns. - have added a new column,
page_id
. - have changed the primary key. The new composite primary key is a combination of the
contact_id
,timestamp
andform_id
columns. Previously, the primary key was a combination of thecontact_id
andconversion_id
columns.
- no longer support the
In the
CONTACT
table, we no longer support themerged_vids
andcanonical_vid
columns.In the
PROPERTY_OPTION
table, we no longer supportdouble_data
andread_only
columns.In the
FORM
table, we've added a new columnform_type
.
July 2022link
We have added a new table, MERGED_DEAL
. You can use this table to find the merged deals. To learn more, see Merge deals.
We have deprecated the is_merged
column from the DEAL
table. We will not delete the existing column from your destination table. For new records, we will populate this column as NULL
in your destination table.
We now sync the OWNER
table using version 3 of the HubSpot API. For more information, see HubSpot's API documentation. We no longer sync the following columns from the OWNER
table because the new API version does not return them:
portal_id
type
user_id_including_inactive
We will not delete the existing columns from your destination table. For new records, we will populate these columns as NULL
in your destination table.
We have added the following new tables:
OWNER_TEAM
ROLE
TEAM
TEAM_USER
USERS
NOTE: We capture deletes for the
ROLE
,TEAM
,TEAM_USER
, andUSERS
tables.
To sync the TEAM
, ROLE
, and USERS
tables, you must re-authenticate the connector because the endpoints need the settings.users.read
and settings.users.teams.read
scopes.
May 2022link
The HubSpot connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. HubSpot's priority-first syncs fetch the most recent 24 hours' worth of data from the EMAIL_EVENT
table and its child tables. To learn more, see our priority-first sync documentation.
Now, the EMAIL_EVENT
table syncs data for only the event types you define in the source EMAIL_EVENT_*
child tables. For more information, see our documentation.
February 2022link
We have added support for custom objects. You can now sync custom objects from your HubSpot account to your destination. We create a destination table for each custom object. We are gradually rolling out this improvement to all our existing customers.
August 2021link
The HubSpot connector now supports history mode for the following tables:
COMPANY_PROPERTY_HISTORY
CONTACT_PROPERTY_HISTORY
DEAL_PROPERTY_HISTORY
LINE_ITEM_PROPERTY_HISTORY
PRODUCT_PROPERTY_HISTORY
TICKET_PROPERTY_HISTORY
We are gradually rolling out this improvement to all existing customers. For more information about history mode, see our documentation.
July 2021link
We have added a new primary key column, _fivetran_id
, to the EMAIL_SUBSCRIPTION_CHANGE
table. Be sure to update your queries.
June 2021link
We have added the following new tables, to support HubSpot's Marketing Email API:
MARKETING_EMAIL
MARKETING_EMAIL_CAMPAIGN
MARKETING_EMAIL_CONTACT
MARKETING_EMAIL_CONTACT_LIST
May 2021link
We now support incremental updates for the CONTACT_LIST_MEMBER
table.
April 2021link
We have added two new metadata tables, PROPERTY
and PROPERTY_OPTION
, to sync the properties associated with the following objects:
- company
- contact
- deal
- line_item
- product
- ticket
March 2021link
We now re-sync the TICKET
table if we find that the table hasn't been synced in the last 24 hours because of the Tickets API limitations. We re-sync the table to ensure data integrity.
We have added two new tables, TICKET_PIPELINE
and TICKET_PIPELINE_STAGE
to support HubSpot's pipelines object.
February 2021link
We have added a new column, meeting_outcome
, to the ENGAGEMENT_MEETING
table.
We have added a new column, is_merged
, to the DEAL
table to track merged deals. If you'd like to sync historical data for this column, re-sync the DEAL
table.
January 2021link
We have added a new table, DEAL_STAGE
which stores the dealstage
properties data. Previously, we synced the dealstage
data to the DEAL_PROPERTY_HISTORY
table. The HubSpot API returns only the date_entered
value. Use the date_entered
and date_exited
values to calculate the time_in
value.
December 2020link
We have added a new child table, CALENDAR_TOPIC
, to the CALENDAR_EVENT
table.
We have added the following new columns to the OWNER
table:
is_active
active_user_id
user_id_including_inactive
November 2020link
We have expanded the public API endpoints Create a Connector and Modify a Connector. Now you can authorize the following connectors by adding the auth
section to payloads:
We have added the following new tables to support HubSpot's Tickets API:
TICKET
TICKET_COMPANY
TICKET_CONTACT
TICKET_DEAL
TICKET_ENGAGEMENT
TICKET_PROPERTY_HISTORY
See our Service Hub schema for more information.
October 2020link
We now support future timestamp values in the ENGAGEMENT_MEETING
table. If you previously synced future timestamp values, re-sync the table to ensure data integrity.
September 2020link
We have added a new child table, CALENDAR_USER
, to the CALENDAR_EVENT
table.
August 2020link
We have released pre-built, dbt Core-compatible data models for HubSpot. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
We now use webhooks to capture deletes for the COMPANY
, CONTACT
, and DEAL
tables. We are gradually rolling out this new feature to all existing customers. If you'd like to enable this feature on your connector, contact our support team.
July 2020link
We have added a warning to your Fivetran dashboard that asks you to increase your sync frequency if your COMPANY
and COMPANY_PROPERTY_HISTORY
tables have huge recurring updates. Previously, if these tables had more than 9900 updates, we initiated a complete re-sync to prevent data integrity issues. The re-sync caused high MAR (monthly active rows) consumption. You can prevent these re-syncs and avoid impact on your MAR by increasing your sync frequency.
May 2020link
You can now configure your HubSpot connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
April 2020link
We now support future timestamp values in the following tables:
CALENDAR_EVENT
COMPANY_PROPERTY_HISTORY
CONTACT_FORM_SUBMISSION
CONTACT_PROPERTY_HISTORY
DEAL_PROPERTY_HISTORY
EMAIL_SUBSCRIPTION_CHANGE
ENGAGEMENT
LINE_ITEM_PROPERTY_HISTORY
IDENTITY_PROFILE_IDENTITY
If you have previously synced future timestamp values, re-sync the tables to ensure data integrity.
March 2020link
We have added three new fields to the CONTACT
table:
canonical_vid
merged_vids
profile_url
We have added three new tables:
CONTACT_MERGE_AUDIT
CONTACT_IDENTITY_PROFILE
IDENTITY_PROFILE_IDENTITY
August 2019link
- We have added the column
activityType
to theENGAGEMENT
table.
July 2019link
We have added the table blocking feature to all HubSpot tables. You can now choose which tables you'd like to sync or omit from syncing. To select or deselect tables, go to the schema page of your Fivetran dashboard.
If you wish to sync a child table, you must also sync its parent table.
May 2019link
- Changes made through contact batch updates are processed asynchronously, so it can take several minutes for changes to be applied to contact records. To capture all the changes, once a day we take the cursor back by 1 day to capture all the updates.
February 2019link
New fields in ENGAGEMENT_*
tables will be synced automatically.
January 2019link
- We have added the new column
web_conference_meeting_id
to theENGAGEMENT_MEETING
table. - We have also added the new column
unknown_visitor_conversation
to theENGAGEMENT_CALL
table.
September 2018link
We have added a new field, transcription_id
, to the ENGAGEMENT_CALL
table.
The HubSpot connector can now sync e-commerce data for your Sales Hub, including products and line items. We have added the following tables to support this feature:
PRODUCT
PRODUCT_PROPERTY_HISTORY
LINE_ITEM
LINE_ITEM_PROPERTY_HISTORY
August 2018link
We have added two new columns, attachedVideoOpened
and attachedVideoWatched
, to the ENGAGEMENT_EMAIL
table.
July 2018link
We have added the media_processing_status
column to the ENGAGEMENT_EMAIL
table.
May 2018link
We have added two new fields, callee_object_type
and callee_object_id
, to the ENGAGEMENT_CALL
table.
April 2018link
We have added the following columns to the tables below:
TABLE | COLUMN |
---|---|
ENGAGEMENT_META_EMAIL | post_send_status |
ENGAGEMENT_EMAIL | recipient_drop_reasons |
We will now re-sync the entire ENGAGEMENTS
table when there are more than 10,000 changed records, because HubSpot can no longer complete incremental queries to the engagements endpoint when there are so many changed records.
Some HubSpot records have very old timestamps (for example,Jan 1 1970
). These values no longer cause our syncs to fail.