Marketing Tools

HubSpot Salesforce Integration: Segment in Salesforce, Market in HubSpot

Why HubSpot lists can't use most of your Salesforce data, how selective sync and inclusion lists work – and how to push Salesforce segments into HubSpot lists via API.

A glass block gliding into the missing gap of a glass bridge between two canyon cliffs – HubSpot Salesforce integration

If you run Salesforce as your CRM and HubSpot for marketing, the cleanest way to target the right people is to build the segment where the data lives – in Salesforce – and push the result into a HubSpot list automatically. With Campaign Audience Builder, you segment on any Salesforce object, and a custom API integration creates the HubSpot list, creates missing contacts and adds every member – no exports, no duplicated data.

This article explains why the native HubSpot–Salesforce integration doesn’t solve segmentation, what selective sync and inclusion lists actually do, and how the API-based approach works step by step.

Why HubSpot lists can’t see your Salesforce segments

Many companies combine both platforms for good reasons: Salesforce runs sales and service – accounts, opportunities, products, contracts, cases, custom objects. HubSpot runs email, nurturing and marketing automation.

HubSpot’s native Salesforce integration keeps records in sync: contacts, companies, deals and – in newer versions – tickets and selected custom objects. But it syncs records, not segments. HubSpot lists (in newer HubSpot versions called segments) can only filter on data that exists in HubSpot. That leads to a few hard limits:

  • Campaigns don’t sync. HubSpot only sees the IDs of the Salesforce campaigns a contact belongs to – no campaign member status, and no connection to HubSpot campaigns.
  • Lookup fields don’t sync, and related records like opportunity products, contracts, assets or cases are not available for list filters.
  • Custom objects can only be synced in HubSpot Enterprise, are limited in number and need API-based setup.
  • Every sync uses Salesforce API calls, which are shared with all your other integrations.

The result: the segments your sales and service data could power – “customers with product A but not product B”, “accounts with a renewal in the next 90 days”, “contacts with an open escalation” – can’t be built in HubSpot unless you copy all that data over first.

Selective sync vs. inclusion list

Two HubSpot settings are often mentioned in this context – and often confused. Both control which records sync, not which segments marketing can use.

Selective sync Inclusion list
Direction Salesforce → HubSpot HubSpot → Salesforce
Purpose Only bring relevant Salesforce leads/contacts into HubSpot Only push qualified HubSpot records into Salesforce
Based on Salesforce side (e.g. visibility of the integration user, criteria) An active HubSpot list/segment
Typical use Keep the HubSpot database (and contact tier) lean Keep unqualified leads out of the CRM
Solves segmentation? No No

Both are worth configuring – but neither lets you build a HubSpot list from Salesforce data that HubSpot doesn’t have.


Why the usual workarounds fall short

Teams typically try one of these approaches before looking for something cleaner:

Approach How it works The catch
Copy data into HubSpot properties Map rollups like “Bought product X” or “Renewal date” to contact properties and filter on them in HubSpot Every new segment needs new fields, syncs and maintenance in two systems; more API calls; data drifts apart
Filter on Salesforce campaign IDs Fill a Salesforce campaign, then build a HubSpot list on that campaign ID No member status, no removal logic, timing depends on the sync; still needs someone to maintain the campaign
Export and import Build a report in Salesforce, export a CSV, import it into a HubSpot list Manual, error-prone, outdated the next day, sensitive data leaves the system
Segment in Salesforce + API transfer Build the audience in Salesforce and push it into a HubSpot list automatically Set up once, then runs automatically – see below

The solution: Campaign Audience Builder + HubSpot API integration

The idea is simple: Salesforce stays the single source of truth for segmentation, HubSpot stays the execution engine for marketing. Campaign Audience Builder connects the two.

How it works

  1. Segment in Salesforce. Build the audience in Campaign Audience Builder with criteria on any standard or custom object – opportunities and products, contracts, cases, activities, custom objects – including AND/OR logic and exclusions.
  2. Keep it current. Schedule the audience so it refreshes automatically – daily, hourly or before each campaign.
  3. Trigger the transfer. On each run, CAB hands the audience result to a Salesforce Flow or Apex action through its Flow & Apex integration.
  4. Push to HubSpot via API. The action calls the HubSpot API and
    • creates contacts in HubSpot that don’t exist yet,
    • creates the target list in HubSpot,
    • adds all audience members to that list.
  5. Market in HubSpot. Use the list for emails, workflows and ads as usual.

Why this approach is clean

  • No data duplication: You don’t need to mirror products, contracts or cases in HubSpot. Only the contacts you actually market to are transferred.
  • One source of truth: Segment logic lives in one place – Salesforce – and uses the full data model.
  • No manual steps: No exports, no CSV imports, no copy-paste between tools.
  • Fewer moving parts: No extra helper fields in either system, no growing field mappings.
  • Repeatable: Once set up, every new segment uses the same integration – marketing just builds a new audience.

What you need

  • Campaign Audience Builder with the Flow & Apex integration (Professional plan and above).
  • A HubSpot private app (access token) with permissions for contacts and lists.
  • The HubSpot integration action, which we set up with you and adapt to your data model and naming conventions.

Example: cross-sell campaign from Salesforce data in HubSpot

Goal: email all decision makers at customers who bought Product A in the last 24 months but don’t own Product B – excluding contacts with an open support case.

  1. Audience in CAB: Contacts with role “Decision Maker” → Account → Closed Won opportunity with opportunity product Product A in the last 24 months → no asset or opportunity product Product B → no open case.
  2. Schedule: daily at 6:00.
  3. Transfer: the Flow action sends the result to HubSpot; contacts that don’t exist in HubSpot yet are created, and all members are added to the list “Cross-sell – Product B”.
  4. HubSpot: a nurturing workflow enrols the list and sends the sequence.

None of these criteria would be available in a HubSpot list without syncing product, asset and case data into HubSpot first.

Best practices

  • Respect consent in both systems. Exclude opted-out and unsubscribed contacts in the Salesforce audience and keep HubSpot’s subscription types as the final gate before sending.
  • Name lists consistently. A clear prefix (e.g. SF – ) shows marketers which lists are fed from Salesforce and shouldn’t be edited by hand.
  • Plan the refresh logic. Decide per use case whether a run creates a new list (snapshot, e.g. for a one-off campaign) or updates an existing one (ongoing nurturing).
  • Watch API usage. Schedule transfers at sensible intervals and only transfer the fields HubSpot really needs.
  • Configure selective sync and inclusion lists anyway. They keep both databases clean – the audience transfer complements them, it doesn’t replace them.

Conclusion

The native HubSpot–Salesforce integration is good at keeping records in sync, but it was never designed to turn Salesforce data into HubSpot segments. Copying ever more data into HubSpot or exporting CSVs only moves the problem around.

Segmenting in Salesforce with Campaign Audience Builder and pushing the result into HubSpot lists via API closes that gap: one source of truth, the full Salesforce data model for targeting, and HubSpot doing what it does best. Want to set it up for your org? Talk to us – we’ll walk through your use case and the integration setup.

Campaign Audience Builder

Segment in Salesforce, market in HubSpot

Campaign Audience Builder segments in Salesforce and hands the result to HubSpot or any other tool through Flow or Apex – on a schedule.

  • Hand audiences to any tool via Flow or Apex
  • Keep audiences current on a schedule
  • Segment on any Salesforce object
Audience in Campaign Audience Builder
Start for freeBook a demo

FAQ

Does HubSpot integrate with Salesforce?

Yes. HubSpot offers a native Salesforce integration that syncs contacts, companies, deals and – in newer versions – tickets and custom objects between both systems. It's built for keeping records in sync, not for transferring Salesforce-based segments into HubSpot lists.

What is a Salesforce inclusion list in HubSpot?

An inclusion list is an active HubSpot list (segment) that limits which HubSpot records are allowed to sync to Salesforce. Records outside the list don't sync. It controls the direction HubSpot → Salesforce; for Salesforce → HubSpot you use selective sync.

What is selective sync?

Selective sync limits which Salesforce leads and contacts are synced into HubSpot, typically based on the Salesforce user permissions of the integration user or criteria you define. It keeps your HubSpot database focused on records you actually market to.

Can HubSpot lists filter on Salesforce campaigns?

Only partially. HubSpot sees the IDs of the Salesforce campaigns a contact belongs to, but not campaign member statuses, and Salesforce campaigns don't sync to HubSpot campaigns. Segments based on products, contracts, cases or custom objects can't be rebuilt in HubSpot without copying that data over.

Can the transfer from Salesforce to HubSpot be automated?

Yes. With Campaign Audience Builder, audiences are refreshed on a schedule in Salesforce, and a Flow or Apex action sends the result to HubSpot via API – creating missing contacts, creating the list and adding the members without manual exports or imports.