# HubSpot integration for paid acquisition

Hendrik reads HubSpot contacts, companies, deals, property history, pipelines, forms, submissions, and engagements so you can compare paid lead volume with pipeline quality.

## Questions Hendrik can help answer

- Are reported leads becoming qualified deals?
- Did stage definitions or forms change?
- Should the next ad budget choice depend on pipeline quality?

## Illustrative example

### Review lead growth against qualified pipeline

Same 30-day USD windows

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Reported leads (Google Ads): 150 → 210
- Deals entering qualified stage (HubSpot): 34 → 31
- Form submissions (HubSpot): 120 → 190

### What Hendrik checks

- **Check conversion definition:** Record the Google Ads lead conversion action.
- **Check form change history:** Review whether form routing or required fields changed.
- **Check stage rules:** Use the same HubSpot qualification criteria across windows.

### What Hendrik sees

Reported leads and form submissions increased, while deals entering the qualified stage fell.

### What to do next

Review lead quality and form routing before increasing spend.

**Limit:** No individual ad lead is attributed to a HubSpot deal here.

## What HubSpot contributes

Use HubSpot with Google Ads, Meta Ads, or LinkedIn Ads to see whether reported leads became qualified deals.

## Data Hendrik reads

- **Contacts and companies:** CRM contact and company records.
- **Deals:** Deal and deal history.
- **Pipelines:** Pipeline and stage definitions.
- **Forms:** Forms and submission records.
- **Engagements:** Recorded engagement context.

## Setup and access

- **Setup:** When enabled, sign in with HubSpot and confirm the portal.
- **Permissions:** HubSpot read scopes for contacts, companies, deals, schemas, and forms.
- **Accounts:** One HubSpot portal.
- **History:** The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to daily. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** HubSpot starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** Connecting reads HubSpot data. It does not change contacts, deals, forms, or pipelines.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- Confirm the HubSpot portal and qualified-stage definition.
- Use consistent deal creation and stage-change dates.
- Establish campaign or person identity before entity-level attribution.

## Important limits

- A CRM deal is not a payment or closed-won cash receipt.
- Contact identity cannot be assumed to match ad-platform or analytics identity.
- Account-wide pipeline movement is not campaign attribution.

## Provider documentation

- [HubSpot CRM API](https://developers.hubspot.com/docs/api/crm/understanding-the-crm)
- [HubSpot API](https://developers.hubspot.com/docs/api/overview)

## Start with HubSpot

[Create a workspace and connect HubSpot](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-hubspot&integration=hubspot)