HubSpot Audience Destination

RudderStack now supports the HubSpot Audience destination — you can use it to keep a HubSpot static contact list in sync with a warehouse table, SQL model, or Lookout audience. HubSpot Audience adds contacts who enter the source and removes contacts who leave it. This sync changes list membership only — it does not create or update HubSpot contacts.

HubSpot Audience is in Private Beta.

Reach out to Customer Success to enable it for your workspace.

Why we built this integration

The Event Stream HubSpot destination creates and updates contacts and sends event data. HubSpot campaigns run from static contact lists, and those lists go stale when membership lives in the warehouse or in Lookout.

HubSpot Audience keeps one static contact list aligned with that membership. You attach an existing list or create an empty one during setup. Mirror mode adds people who join and removes people who leave, so the list stays current for campaigns.

Key features

• List membership only: The sync adds and removes contacts on a static list. It does not create or update contact records.
• Existing or new list: Select a static contact list that already exists, or create an empty one during setup. Active lists do not appear in the picker.
• Record ID, then email: A mapped HubSpot Record ID is used first. Email is used only when the Record ID is empty. A Record ID that HubSpot does not recognize does not fall back to email.
• Warehouse, Audience Builder, and Lookout: Connect a Reverse ETL source, sync an Audience Builder audience, or activate a Lookout audience.

Get started

1. Create a HubSpot Service Key with crm.lists.read, crm.lists.write, crm.objects.contacts.read, and crm.objects.contacts.write.
2. Connect a Reverse ETL source to HubSpot Audience, add an Audience Builder sync, or activate a Lookout audience.
3. Select an existing static contact list, or create a new one.
4. Map at least one identifier: HubSpot Record ID, email, or both.

See the HubSpot Audience documentation for scopes, list behavior, and what a sync does.

Known limitations

• A full sync adds everyone currently in the source and removes no one. Contacts who left before that run can stay on the list.
• An email that does not match a HubSpot contact fails on both add and delete. This sync never creates the contact.

Resources

• HubSpot Audience: Scopes, sync failures, and what happens when you stop a sync
• How membership is written to HubSpot: Insert, delete, and full sync behavior
• Connect Reverse ETL Source to HubSpot Audience: Connect a warehouse table or SQL model
• Sync Audiences to HubSpot Audience: Sync an Audience Builder audience
• How to Activate an Audience to a Destination: Activate a Lookout audience