HubSpot CRM integration
HubSpot CRM is on the map, not in the product yet.
We read HubSpot contacts to connect real leads back to the landing pages that created them.
How it works
The HubSpot integration is an OAuth public app requesting read-only CRM scopes. We read Contacts, specifically email, lifecycle stage, and original source properties, and correlate lead creation with the published landing pages those leads arrived through. Nothing is written to your CRM: no properties added, no records changed, no workflows touched.
In the loop, HubSpot upgrades the measure step from traffic to leads. GA4 can show that a page converts; HubSpot shows the actual contacts a page produced and where they sit in your lifecycle now. That closes the argument content marketing usually cannot close, connecting a published article to named leads in the pipeline, using the CRM your team already trusts.
Best forTeams running HubSpot who want published content credited with the leads it generates, not just the sessions it drives.
Setup, step by step
- Click Connect on the HubSpot card, which starts HubSpot's OAuth flow.
- Sign in and choose the HubSpot account to connect.
- Approve the read-only CRM scopes on the consent screen.
- Confirm the source properties available on your tier, which we detect and report during setup.
- Review the first attribution report linking recent contacts to their landing pages.
Best practices
Keep original source data intact
Attribution rides HubSpot's original source properties. Imports and manual edits that overwrite source fields erase the trail, so protect those properties in your team's data hygiene rules.
Know what your tier records
The richest attribution properties depend on your HubSpot subscription tier. We detect what your portal exposes at connect and report attribution at the depth your data actually supports.
Read lifecycle stage, not just creation
A page that creates contacts who stall at subscriber differs from one producing qualified leads. We include lifecycle stage in attribution so pages are judged on lead quality, not just lead count.
Use a connecting user with stable access
The OAuth connection lives under the HubSpot user who approves it. Connect with an account that will keep portal access, and reconnect promptly if that user is deactivated.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Attribution depth follows your HubSpot tier
The richest source and attribution properties exist only on higher HubSpot tiers, so portals on lower tiers yield coarser attribution.
How we handle itWe detect the properties your portal exposes and build attribution from what is there, telling you plainly which level of depth your tier supports instead of showing empty columns.
developers.hubspot.com
API rate limits on large portals
HubSpot enforces API rate limits, and portals with large contact databases can take a while to sync if reads are naive.
How we handle itWe sync incrementally, reading only contacts created or updated since the last pass, and throttle inside HubSpot's limits so syncs complete without ever tripping them.
developers.hubspot.com
Questions teams ask
- Can SearchHandled modify our CRM data?
No. The app requests read-only CRM scopes and HubSpot enforces them. We read contact properties for attribution and cannot create, edit, or delete anything in your portal.
- Which contact fields do you read?
Email, lifecycle stage, and original source properties. That is what lead attribution needs, and the scope list on HubSpot's consent screen matches it.
- Why does attribution look richer on some portals than others?
HubSpot exposes deeper attribution properties on higher tiers. We use whatever your portal records, so depth follows your subscription, and we tell you during setup exactly what your tier provides.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us HubSpot CRM matters moves it up the rollout.