How to Get HubSpot Data Into Looker Studio, Step by Step

Can you connect HubSpot directly to Looker Studio?

HubSpot has no first-party Looker Studio connector built by Google. Looker Studio's list of Google-built connectors names exactly four products -- Google Sheets, Google Ads, BigQuery, and Google Analytics -- and HubSpot isn't among them, as of August 12, 2026. Every working route into a HubSpot report instead runs through a community connector (one built by a developer or company other than Google), a manual Google Sheets export, or a third-party pipeline such as Supermetrics, Windsor.ai, or Improvado.

Looker Studio lists more than 1,300 community connectors in that gallery, plus the option to build a custom one through Google's Looker Studio developer portal. This guide compares those routes on facts each vendor publishes about its own product -- entry price, listed destinations, row limits -- not on marketing copy. Readers who want the contrast with a channel Google does connect natively can compare the Google Ads to Looker Studio setup, which needs no third-party account at all.

What do you need before connecting HubSpot to Looker Studio?

Four things need to be in place: a HubSpot account on a plan that covers the CRM objects (the separate record types HubSpot stores -- contacts, companies, deals) you want to report on, a Google account for Looker Studio, a decision on which objects the report covers, and a decision on which route to take. HubSpot's Free Tools CRM costs $0 per month for up to 2 users and 1,000 contacts, with no credit card required, as of August 12, 2026 -- enough to test any route.

• A HubSpot account with the right access level. Free Tools CRM is "100% free with no expiration date," capped at 2 users and 1,000 contacts, as of August 12, 2026. Reporting on more contacts or more CRM objects may require a paid tier, such as HubSpot's Starter Customer Platform at $20 per seat per month, with a promotional price from $7 per seat per month for new customers on monthly billing, as of the same date.
• A separate Google account for Looker Studio. HubSpot login and Google login are two different identities. Unlike the Google Ads connector, which inherits access from a Google account that already touches Google Ads, a HubSpot connector needs its own authorization step against the HubSpot account, on top of the Looker Studio sign-in.
• A decision on which CRM objects the report needs. Contacts, companies, and deals each carry different fields. That choice determines which route -- and which fields -- are available once you start building the data source.
• A plan for the route itself. A community connector or Sheets export needs nothing beyond the two accounts above. A paid pipeline route through Supermetrics, Windsor.ai, or Improvado adds its own account and its own free-tier caps to check first.

Looker Studio's connector gallery covers HubSpot alongside dozens of other data source integrations, all reached through the same sign-in-and-authorize pattern once the accounts above are in place.

Which routes actually get HubSpot data into Looker Studio?

Three route categories connect HubSpot to Looker Studio, since no first-party Google connector exists. Route A is a partner connector that plugs directly into Looker Studio as a live data source -- Supermetrics or Windsor.ai. Route B is a manual export into Google Sheets, which Looker Studio's native Sheets connector then reads. Route C is a warehouse-first pipeline such as Improvado, which lands HubSpot data in BigQuery or Snowflake rather than in Looker Studio itself.

Route B costs nothing beyond time: someone exports HubSpot records into a spreadsheet on a recurring basis, and Looker Studio reads that file through its native Sheets connector. It carries the most manual upkeep of the three, since nothing refreshes between exports on its own. A stakeholder relying on it sees whatever data was last exported, not the current day's records.

Supermetrics and Windsor.ai both name Looker Studio explicitly among their supported destinations. Either one is a direct stand-in for the native connector HubSpot lacks. Improvado's destination list runs to warehouses instead -- BigQuery, Snowflake, and similar systems -- with Looker Studio absent, a structural fact about where Improvado writes data rather than a shortcoming of the product. Readers comparing pipelines in more depth can start with Supermetrics alternatives or Windsor.ai alternatives.

How do you connect HubSpot to Looker Studio step by step?

Connecting HubSpot to Looker Studio through a partner connector takes six main steps, all inside Looker Studio's own interface: opening a new data source, searching the connector gallery, authorizing both accounts, choosing which HubSpot objects to pull, reviewing the fields Looker Studio detects, and connecting the finished data source to a report. The manual Google Sheets bridge swaps the middle steps for an export, then continues through Looker Studio's native Sheets connector.

1. 1

   Open a new data source

   In Looker Studio, start a new report or a new data source from the home screen -- the same starting point used for any connector.

2. 2

   Search the connector gallery for HubSpot

   Looker Studio's connector gallery lists partner and community connectors separately from Google's built-in ones; search it for a HubSpot connector.

3. 3

   Sign in to Looker Studio

   Sign in with the Google account that will own the report. This identity is separate from the HubSpot login used in the next step.

4. 4

   Authorize the connector's access to HubSpot

   Approve the connector's request to read the HubSpot account. Most connectors authenticate through a private app (an app scoped to a single HubSpot account, authorized with a generated access token) or an OAuth app (an authorized connection that lets one tool read another's data without sharing a password).

5. 5

   Choose which HubSpot objects to include

   Select contacts, companies, deals, or another CRM object, plus the specific properties needed on each, since the objects chosen here set what the report can show later.

6. 6

   Review the auto-detected fields

   Check the fields Looker Studio pulls in against what the report actually needs before adding the data source, since not every property carries over by default.

7. 7

   Connect the data source to a report

   Add the connected data source to a new or existing Looker Studio report and begin building charts and tables from its fields.

8. 8

   Set a refresh schedule and share

   Set how often the connector should refresh, then share the finished report using Looker Studio's own sharing controls.

The Sheets-bridge route replaces the middle steps: export HubSpot records into a spreadsheet first, then add Looker Studio's native Google Sheets connector and point it at that file. Choosing objects and properties happens at export time instead of inside a live authorization screen. HubSpot's API uses dated versioning such as GET /crm/objects/2026-03/contacts, which most export tools and community connectors call behind the scenes on either route.

How do HubSpot CRM objects map into a Looker Studio report?

HubSpot stores contacts, companies, and deals as three separate CRM objects. Each lands in Looker Studio as its own flat table rather than one already-joined dataset. A deals table carries a pipeline and a stage field but no company name by default, and a contacts table carries none of a deal's dollar value. Rebuilding the connection between them happens inside Looker Studio itself, through data blending.

HubSpot calls contacts and companies a "unified database," but that describes how they relate inside HubSpot, not how they arrive in a report. Looker Studio pulls them as two separate tables regardless. Deals move through a deal pipeline (the stages a deal passes through on its way to closed-won or closed-lost), and a report tracking revenue needs that pipeline and stage field, not just a raw count. Custom properties (any field added on top of HubSpot's defaults) are not guaranteed to arrive automatically; whether they do depends entirely on how the connector or export was configured.

Associations -- the links HubSpot maintains between a contact, its company, and any deals tied to that contact -- are what let a Looker Studio blend combine people-level data with revenue-level data. Two tables pulled in side by side without their association attached do not merge on their own.

Decide a report's grain before picking a route. One row per contact, or one row per deal? Which associated properties that grain needs. This avoids rebuilding the data source later. Once contacts, deals, and their associations sit correctly in one report, that same structure feeds marketing attribution models, where a touchpoint needs to be traceable back to a specific deal and its revenue.

What actually breaks a HubSpot to Looker Studio connection?

HubSpot enforces published rate limits on any tool reading CRM data, and those limits -- not the connector itself -- usually break a HubSpot to Looker Studio report under real use. A private app (a HubSpot integration built for a single account) on the Free or Starter tier is capped at 100 requests per 10 seconds and 250,000 requests per day, rising to 190 requests per 10 seconds and 1,000,000 per day on Enterprise, as of August 12, 2026.

HubSpot publishes these figures in its API documentation. Professional-tier private apps sit between the two, at 190 requests per 10 seconds and 625,000 per day. An API Limit Increase Add-on adds 250 requests per 10 seconds and 1,000,000 more requests per day per increase, capped at a maximum of two increases.

Each HubSpot account that installs an OAuth app is limited to 110 requests every 10 seconds -- stated verbatim on HubSpot's own developer documentation, as of August 12, 2026, and separate from the private-app limits above.

A HubSpot to Looker Studio pipeline tends to fail in one of five ways:

1. A connector syncing contacts, companies, and deals on the same schedule multiplies request volume across three objects, pushing a private app past its 10-second cap during one sync window.
2. A HubSpot account on the Free tier, capped at 2 users and 1,000 contacts, as of August 12, 2026, hits its own record ceiling before any API rate limit becomes the bottleneck.
3. A refresh schedule set tighter than a connector's plan allows goes unnoticed until a report shows stale numbers -- Supermetrics' Starter plan refreshes weekly, into Google Sheets only, while its Growth plan refreshes daily, as of September 6, 2026.
4. Windsor.ai syncs daily on its Free and Basic plans, moves to hourly from its Standard plan, and reaches 15-minute intervals only from its Professional plan, as of September 6, 2026. A report expecting near-real-time numbers on a lower tier will not get them.
5. Custom properties and object associations silently drop out of a sync when the connector or export was never configured to include them. This looks identical to a rate-limit failure but has nothing to do with API quotas.

Looker Studio's own pages do not publish a row or data-volume limit for any data source, as of August 12, 2026 -- a gap in what Looker Studio discloses, not confirmation that no ceiling exists.

When does a paid HubSpot data pipeline earn its cost?

A paid pipeline earns its cost once a report needs channels beyond HubSpot inside Looker Studio, a published row cap to plan against, or a warehouse landing spot for modeling. Supermetrics' Starter plan costs $55 per month, Windsor.ai's Free plan runs at $0 per month, and Improvado's Free Limited plan is also $0 per month, each as of September 6, 2026.

Supermetrics and Windsor.ai both list Looker Studio explicitly among their supported destinations, which fits a report reading directly out of Looker Studio. Supermetrics' Starter plan costs $55 per month ($44 billed yearly) for 3 data sources, 1 user, and 50,000 API rows per month; its Growth plan costs $222 per month ($177 billed yearly) for 6 data sources, 2 users, and 250,000 API rows per month, as of September 6, 2026, with a 14-day free trial and no credit card needed. Windsor.ai's Free plan covers 1 user, 10 data sources, 15 accounts, and 30 days of history at $0 per month; its Basic plan costs $23 per month ($19 billed annually); its Standard plan costs $118 per month for 7 data sources, same date.

Improvado publishes different destinations: BigQuery, Snowflake, Amazon Redshift, Amazon Athena, Azure SQL, Microsoft SQL Server, MySQL, PostgreSQL, Tableau, Metabase, and Redash -- Looker Studio is not on that list, as of September 6, 2026. That makes Improvado a warehouse-first route rather than a direct Looker Studio connector. A report still needs Looker Studio's own BigQuery connector to read from wherever Improvado lands the data. Improvado's Free Limited plan costs $0 per month for 50 MCP (Model Context Protocol) actions per week; its MCP Only plan costs $100 per month for 2,000,000 rows per year and daily sync; Advanced and Enterprise plans are custom pricing, same date. Readers weighing that route can compare it against other Improvado alternatives.

A paid pipeline doesn't replace the object-mapping work. HubSpot contacts, companies, and deals still move into Looker Studio as separate tables, and a warehouse or connector destination doesn't rebuild the associations automatically. What a paid pipeline buys is a published, plannable ceiling instead of an undocumented one, which matters most once a report feeds marketing ROI reporting that a budget decision depends on.

Teams that would rather not maintain a connector stack at all take a different path: AdMetric is an AI marketing automation and analytics platform for small and mid-size businesses and agencies, which pulls CRM and advertising data into one reporting view instead of into a chart library that someone has to rebuild. Its pricing runs on a 7-day free trial with no credit card required.

Frequently asked questions about connecting HubSpot to Looker Studio