HubSpot
Managed destination - Vendo can model HubSpot as an activation destination for events, contact profiles, company records, and audiences. Confirm the destination is enabled in your Vendo environment before running a production sync.
HubSpot is also available as a source for CRM objects, activities, forms, and marketing data.
Activation Capabilities
The Vendo app catalog marks HubSpot as accepting these destination data types:
| Data type | What Vendo prepares |
|---|---|
| Events | Behavioral or modeled events with a timestamp, event name, user identity, and mapped properties |
| User profiles | Contact traits such as email, phone, name, lifecycle stage, location, and custom fields |
| Groups | Company or account-level properties for B2B activation |
| Audiences | Segment memberships for CRM lists or workflow enrollment |
Required Identity
Map at least one stable identifier before enabling a HubSpot activation sync.
| Identifier | Use |
|---|---|
| Primary contact match key for most HubSpot records | |
| HubSpot contact ID | Exact contact match when the source data already contains HubSpot IDs |
| Phone | Secondary contact match key when available |
| Company domain or company ID | Company/group updates and account-level enrichment |
Setup
HubSpot activation uses the same OAuth connection model as the HubSpot source.
- Connect HubSpot from Apps and complete the OAuth flow.
- Create a destination sync to HubSpot from Destinations.
- Choose the source, model, or audience segment to activate.
- Select the data type: events, user profiles, groups, or audiences.
- Map the required identity fields and any HubSpot properties you want Vendo to update.
- Save the destination and run a small test sync before enabling a schedule.
Platform Details
| Setting | Value |
|---|---|
| Auth method | HubSpot OAuth 2.0 |
| Destination types | Events, user profiles, groups, audiences |
| Common identity | Email or HubSpot contact ID |
| Source compatibility | Any Vendo source or model that provides the required identifiers |
| Current setup model | Managed activation; verify environment support before production use |
What Vendo Does Not Do
| Data or action | Status |
|---|---|
| HubSpot data import | Use the HubSpot source |
| Creating custom HubSpot properties automatically | Configure required properties in HubSpot before mapping them |
| Production activation without environment validation | Run a test sync and confirm delivery counts first |
Verify Setup
- Confirm the HubSpot destination is connected and active in Vendo.
- Run a small test sync with one or two known contacts.
- Check the contact timeline or contact properties in HubSpot.
- Confirm Vendo job logs show rows sent, skipped, and failed.
- Review mapped properties against the expected HubSpot field names.
Troubleshooting
| Symptom | What to check |
|---|---|
| Destination cannot be selected | Confirm the HubSpot app is connected and has destination capability in Vendo |
| Records are skipped | Confirm email, contact ID, or another required identifier is mapped |
| Properties are not updated | Confirm the target HubSpot property exists and the mapped type matches |
| Audience sync is empty | Confirm the Vendo segment has members and the identity field matches HubSpot contacts |
Last updated on