Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Expected HubSpot Data

HubSpot Info
The info in this article only applies to HubSpot integrations created on or before February 28, 2017.

If you created a HubSpot integration after this date, refer to the Singer version of this doc.

Now that HubSpot is successfully connected to your Stitch account, what comes next? In this article, we'll cover:

Replicating HubSpot Data

Historical Sync

By default, a historical sync of HubSpot data goes back one year from the Stitch connection date.

Frequency

Stitch will replicate HubSpot data based on the frequency you define. The default setting is every half hour, but you can change it to more or less frequent based on your needs.

Replication Method

The majority of HubSpot data is replicated using Full Table Replication. This means that every time HubSpot data is queued for replication, all rows in a table - including existing, new, and updated - will be replicated. only new and updated rows will be replicated to your data warehouse.

There are a few exceptions to this, however. The following tables (and their subtables, if there are any) use Incremental Replication. This means that when these tables are queued for replication, only new and updated rows will be replicated: 

  • campaign_lists
  • companies
  • contacts
  • email_events
  • subscription_changes

HubSpot Tables in Your Data Warehouse

Below is a list of the HubSpot tables that will be created in your data warehouse. Because HubSpot uses nested arrays to structure data in some of its API's endpoints, Stitch will de-nest these arrays and create subtables. Refer to the Handling of nested data structures doc for more info.

Click the table name to view a full list of attributes for that table in HubSpot's API documentation.

campaigns

Primary Key: id
The campaigns table contains information about your campaigns. Attributes include the campaign ID (id), name, number included, number queued, subtype, subject, type, app ID, app name, content ID, and counters.

campaign_lists

Primary Key: id
The campaign_lists table contains information about campaigns with recent activity. Attributes include the campaign ID (id), app ID, app name, and last updated time.

companies

Primary Key: companyId
The companies table contains information about the companies your contacts belong to. Attributes include the company ID, description, name, and created at date.

contacts

Primary Key: vid
The contacts table contains information about individual contacts in HubSpot. Attributes include the contact ID (vid), first and last name, and custom attributes.

Subtables

  • contacts__form-submissions - This subtable is created from the form-submissions array, which contains form submission data.

    The composite key for this table - made up of the contact ID and row ID - can be used to tie it back to its parent, contacts: _sdc_source_key_vid:_sdc_level_0_id
  • contacts__identity-profiles - This subtable is created from the identity profiles array, which contains identity profile data.

    The composite key for this table - made up of the contact ID and row ID - can be used to tie it back to its parent, contacts: _sdc_source_key_vid:_sdc_level_0_id
    • contacts__identity-profiles__identities - This subtable is created from the identities subarray.

      The composite key for this table can be used to tie it back to its parent, contacts: _sdc_source_key_vid:_sdc_level_0_id:_sdc_level_1_id

contacts_by_company

Primary Key: companyId:contactId
The contacts_by_company table contains contact information, segmented by company.

contact_lists

Primary Key: listId
The contact_lists table contains information about your HubSpot contact lists. Attributes include the list ID, name, internal list ID, portal ID, meta data, and created and updated at timestamps.

  • contacts_lists__filters - This subtable is created from the filters array, which contains contact list filter info.

    The composite key for this table - made up of the contact list ID and row ID - can be used to tie it back to its parent, contact_lists: _sdc_source_key_listid:_sdc_level_0_id

deals

Primary Key: dealId
The deals table contains information about all deals in a portal. Attributes include the deal ID, deal name, deal stage, amount, close date, associated company and/or deal IDs, deal type, number of associated contacts, and created and updated at timestamps.

email_events

Primary Key: id
The email_events table contains information about email events and how recipients interact with content. Attributes include the email event ID (id), event type, recipient, portal ID, app ID, app name, email campaign ID, IP address, location, and created at timestamp. Sent by data is also included, if applicable.

forms

Primary Key: guid
The forms table contains information about your HubSpot website forms. Attributes include the form ID (guid), name, action, method, CSS class, redirect, follow up ID, notify recipients setting, campaign guid, captcha settings, and created and updated at timestamps.

Subtables

  • forms__forms__sociallogintypes - This subtable is created from the social login types array, which contains info about the social media login types.

    The composite key for this table - made up of the contact list ID and row ID - can be used to tie it back to its parent, forms: _sdc_source_key_guid:_sdc_level_0_id
  • forms__formfieldgroups - This subtable is created from the form field groups array, which contains field group data.

    The composite key for this table - made up of the contact list ID and row ID - can be used to tie it back to its parent, forms: _sdc_source_key_guid:_sdc_level_0_id
    • forms__formfieldgroups__fields - This subtable is created from the fields subarray, which contains data about form fields groups. For example: default value, description, display order.

      The composite key for this table can be used to tie it back to its parent, forms: _sdc_source_key_guid:_sdc_level_0_id:_sdc_level_1_id
      • forms__formfieldgroups__fields__options - This subtable is created from the options subarray, which contains info about form field group options.

        The composite key for this table can be used to tie it back to its parent, forms: _sdc_source_key_guid:_sdc_level_0_id:_sdc_level_1_id:_sdc_level_2_id
      • forms__formfieldgroups__fields__selectedoptions - This subtable is created from the selected options array, which contains info about selected field options.

        The composite key for this table can be used to tie it back to its parent, forms: _sdc_source_key_guid:_sdc_level_0_id:_sdc_level_1_id:_sdc_level_2_id

keywords

Primary Key: keyword_guid
The keywords table contains information your portal keywords. Attributes include the keyword, keyword guid, country, visits, contacts, leads, and created at timestamp.

owners

Primary Key: ownerId
The owners table contains information about all the owners that exist inside your HubSpot portal. Attributes include the portal ID, owner ID, type, first and last name, email address, and created and updated at timestamps.

  • owners__remotelist - This subtable is created from the remote list array.

    The composite key for this table - made up of the owner ID and row ID - can be used to tie it back to its parent, owners: _sdc_source_key_ownerid:_sdc_level_0_id

subscription_changes

Primary Key: recipient:timestamp
The subscription_changes table contains information about changes made to subscriptions. Attributes include the event ID (id), portal ID, recipient email address, change type, and created at timestamp.

workflows

Primary Key: id
The workflows table contains metadata about the workflows in your HubSpot portal. Attributes include the workflow ID (id), name, type, enabled setting, enrolled and active IDs, original author user ID, and updated and inserted at timestamps.

  • workflows__contactlistids__steps - This subtable is created from the steps array.

    The composite key for this table - made up of the workflow ID and row ID - can be used to tie it back to its parent, workflows: _sdc_source_key_id:_sdc_level_0_id

RELATED

Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!