Skip to main content

​
Introduction

HubSpot is an inbound marketing, sales, and customer-service platform organized around a central CRM. Contacts, companies, deals, tickets, marketing emails, and engagement records all live within a single portal, where lifecycle stages and properties describe how each record progresses. The connector exposes CRM and marketing data — contacts, companies, deals, emails, marketing emails, and marketing-email statistics — for use in dashboards and widgets. For contacts, companies, and deals, only the properties selected during data source creation are available; for emails and marketing emails, all standard properties are exposed. Typical use cases include funnel reporting from lead to customer, marketing-email performance tracking, and cross-channel attribution between paid campaigns and CRM outcomes. Deal pipeline analytics — deal amount, MRR, and TCV broken down by pipeline stage — are served by a separate connector; see the HubSpot Deals data reference. To connect this data source, see How to connect HubSpot to Adriel.

​
Data refresh strategy

​
Architecture data

Architecture covers object catalogs — pipelines, deal stages, lifecycle stages, owners, lists, and marketing-email metadata. It refreshes once daily in UTC. Newly created HubSpot objects and renamed pipeline stages become available on the next architecture refresh.

​
Reports data

Reports include CRM and marketing records — contacts, companies, deals, emails, marketing emails, and marketing-email statistics. Not real-time. HubSpot is a batch-synced connector. Records sync from the HubSpot API into a per-asset PostgreSQL cache table once daily at 04:00 UTC, and all queries are served from that cache — there are no live API reads at query time. Refresh window. Created and updated records are picked up on the next sync, so new contacts, deal-stage changes, and marketing-email events typically appear in dashboards within 24 hours of activity in HubSpot. Marketing-email statistics are fetched from two days before the last sync through yesterday; the initial sync backfills the last 90 days.

​
Architecture levels

Account / portal → Object type (Contact, Company, Deal, Ticket, Email, Marketing Email) → Record
  • Account / portal — a single HubSpot portal (Hub ID) authorized through OAuth.
  • Object type — Contact, Company, Deal, Ticket, Email, or Marketing Email.
  • Record — an individual contact, company, deal, ticket, or email send, addressable by its HubSpot ID.

​
Metrics

This is a generic data source. The fields below are the built-in metrics and breakdowns Adriel provides for file, spreadsheet, and database connectors. The data fields you actually report on come from the columns in your connected source. Data type uses Adriel’s vocabulary; an italic API Key marks a value Adriel derives rather than a platform field.

​
General

​
Date Calculation

​
Breakdowns

​
General

​
Limitations

  • Selected-properties model — for contacts, companies, and deals, only the properties chosen at data source creation are available. Adding a newly created custom property to existing widgets requires editing the data source. Emails and marketing emails are not restricted; all standard properties are available.
  • Not real-time — data reflects the last nightly sync (04:00 UTC); changes in HubSpot appear in dashboards within roughly 24 hours.
  • 10,000-row query cap — a query returning more than 10,000 rows is truncated and flagged with a TOO_MUCH_DATA_REQUESTED_INCOMPLETE warning; rows beyond 10,000 are not returned.
  • Lifecycle stage is current-state — the lifecycle-stage breakdown reflects each contact’s present stage. Stage-change history is not retained, so funnel widgets show contacts by their current stage rather than a time series of transitions.
  • Deleted records — data for records deleted on the HubSpot side becomes unavailable after deletion.
  • Separate OAuth app from HubSpot Deals — the HubSpot and HubSpot Deals connectors register as different OAuth applications with separate client credentials and require independent authorization flows, even when both point at the same portal.

​
API references

​
See also