HubSpot (Edge)

Configure HubSpot as a Source in your Pipeline

Perform the following steps to configure your HubSpot Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select HubSpot.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing HubSpot Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, do the following:

   

   • Source Name: Specify a unique name for your Source, not exceeding 255 characters. For example, HubSpot Source.

   • In the Connect to your HubSpot account section, click Authenticate Your HubSpot Account and perform the following steps to configure your account:

     1. If you are not already signed in to your HubSpot account, sign in when prompted. Otherwise, proceed to step 2.

     2. Select the HubSpot account from which you want Hevo to ingest data and copy the corresponding account ID. Specify this value in the HubSpot Account ID (Portal ID) field.

        

     3. Click Choose Account.

     4. Select the acknowledgment check box, and then click Connect app to authorize Hevo to access your HubSpot account data. During authorization, Hevo installs an app in your account that registers webhook subscriptions for the company, contact, and deal objects. This is required for Hevo to capture delete events for these objects.

        

        You are redirected to the Configure Source screen.

   • HubSpot Account ID (Portal ID): The ID of the HubSpot account from which you want Hevo to ingest data.

7. Click Test & Continue to test the connection to your HubSpot Source.

   When you click this button, Hevo makes an API call to retrieve your HubSpot account details. If the API call is successful, it verifies that Hevo can access your account data, and the connection test is marked as successful. You can then proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Note: Selecting a parent object automatically includes all its associated child objects for replication. Child objects cannot be selected or deselected individually.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

• Refresher Data: Hevo ensures that your analytics and event data remain accurate and up to date by re-ingesting records for a defined duration and loading them into the Destination. The refresher task runs every 24 hours to maintain the accuracy and completeness of the data.

  Hevo supports data refresh for the following objects:

  Note: In the table below, * represents the specific analytics report or event type. For analytics reports, this includes Geolocation, Sessions, Sources, Totals, and Urchin Tracking Module (UTM). For email events, this includes event types such as Bounce, Click, and Delivered.

  Objects	Purpose	Data Refresh Duration
  *_analytics_daily_report	Aggregates analytics data for the current day.	30 days
  *_analytics_weekly_report	Provides a summarized view of analytics metrics for the week.	4 weeks
  *_analytics_monthly_report	Provides an overview of monthly trends and traffic.	2 months
  email_event_*	Captures email delivery, open, click, and interaction events.	25 hours
  custom_event	Captures user-defined events and activity data.	25 hours

  For example, let us suppose the geolocation_analytics_daily_report data was ingested till 2025-05-18 during the last Pipeline run. In the current run, Hevo refreshes data for the past 30 days and ingests records from 2025-04-19 to 2025-05-19, ensuring that any updated analytics data within this period is captured correctly.

For the following objects, Hevo ingests the entire data during each Pipeline run:

For all other objects, Hevo ingests only incremental data in subsequent Pipeline runs using timestamp fields such as hs_lastmodifieddate and lastmodifieddate.

Note:

• HubSpot enforces a rate limit on the number of API calls that can be made within a specific time period. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

• HubSpot objects support only the Merge and History load modes. The Append mode is not supported. The load mode for each object is predefined and cannot be changed.

Engagement Data

Hevo supports ingesting data for the following engagement types:

• Calls

• Emails

• Notes

• Tasks

• Meetings

• Publishing Tasks (marketing calendar tasks associated with HubSpot campaigns)

If HubSpot introduces a new engagement type that is not currently supported, Hevo does not ingest data for it.

Custom Objects

Hevo supports ingesting custom objects from your HubSpot account. For each custom object, a corresponding Destination object is created using the standard object naming convention.

Hevo also creates association objects to capture relationships:

• Between different custom objects.

• Between custom objects and standard HubSpot objects.

Associations between custom objects and the following objects are supported:

• Company

• Contact

• Deal

• Email

• Engagement

• Goal

• Line Item

• Product

• Ticket

Note: In HubSpot, association changes for custom objects do not update the updatedAt timestamp field. Due to this limitation, some association changes may not be ingested immediately during incremental ingestion. Hevo ingests these changes when the custom object’s updatedAt value changes because of another property update.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. Each schema has its own Entity-Relationship Diagram (ERD) that shows how the different HubSpot objects are structured and linked to each other in your Destination.

• CRM and Sales Hub

• Goals

• Marketing Hub

• Service Hub

• Web Analytics Reports

Note: In these ERDs, the property_ field in an object represents multiple fields that start with property_. Each of these fields stores a specific detail about the record. For example, property_createdate stores the creation time of the record, and property_content stores the content associated with the record. Instead of listing all such fields individually, these ERDs use the property_ field to represent all of them.

CRM and Sales Hub Schema

This schema contains objects related to core CRM entities, such as contacts, companies, deals, and leads, along with associated sales activities such as calls, meetings, tasks, and interactions. For a detailed view of the objects, fields, and relationships, click the ERD.

Goals Schema

This schema contains objects related to goal tracking and performance measurement across sales and service teams, along with their associations with CRM entities. For a detailed view of the objects, fields, and relationships, click the ERD.

Marketing Hub Schema

This schema contains objects related to marketing campaigns, events, and email activities, along with details of user interactions with these activities, including registrations, cancellations, and attendance records. For a detailed view of the objects, fields, and relationships, click the ERD.

Service Hub Schema

This schema contains objects related to support tickets, conversations, and customer interactions, along with details of customer issues and support requests. For a detailed view of the objects, fields, and relationships, click the ERD.

Web Analytics Reports Schema

This schema contains objects related to website visits, user sessions, and analytics reports, along with details of where users come from and their interactions with the website. For a detailed view of the objects, fields, and relationships, click the ERD.

Note:

• For weekly and monthly analytics reports, the date field represents the starting date of the week or month. For instance, a record in the weekly analytics report with a date of 2025-04-06 represents data from the week beginning on April 6, 2025, and ending on April 12, 2025.

• The breakdown field in analytics reports is used to categorize data based on specific attributes, such as country code or traffic source.

  For example, if the breakdown field contains values such as organic, paid, and referral, each value represents a different traffic source, and the report shows separate records with their corresponding metrics such as user sessions or visits.

• In overall analytics reports, the totals value in the breakdown field indicates that the record contains the aggregated count across all breakdown values in the report.

  For example, if the breakdown field includes traffic sources such as organic, paid, and referral with user session counts of 500, 200, and 300 respectively, the totals value shows a session count of 1000, representing the sum of sessions from all these sources.

• In the geolocation analytics reports, if the breakdown field has the value 7081c5b2-d128-4ec1-a9be-cba29cfc540a, it means HubSpot could not identify the country code for those visits.

---

Data Model

Hevo supports the following API versions for ingesting data from your HubSpot account:

• Legacy API (v1 and v2)

• v3 API

• v4 API

HubSpot Legacy API (v1 and v2)

Hevo ingests the following object using the HubSpot Legacy API:

HubSpot v3 API

Hevo ingests the following objects using the HubSpot v3 API:

HubSpot v4 API

Hevo uses the HubSpot v4 API to ingest data from association objects that define relationships between different CRM objects in your account. These objects capture how entities such as contacts, companies, deals, line items, and engagements are linked to one another. This helps you understand how records are connected and analyze relationships across your HubSpot data.

Association object names follow the format <primary_object>_<related_object>, where the first part is the object from which the relationship is defined and the second part is the object linked to it. For example, company_contact represents the contacts associated with a company.

---