HubSpot is a CRM platform with all the software, integrations, and resources you need to connect marketing, sales, content management, and customer service. It allows you to connect your data, teams, and customers on one CRM platform.
This Adobe Experience Platform destination leverages the HubSpot Contacts API, to update contacts within HubSpot from an existing Experience Platform audience after activation.
Instructions to authenticate to your HubSpot instance are further below, in the Authenticate to destination section.
To help you better understand how and when you should use the HubSpot destination, here is a sample use case that Adobe Experience Platform customers can solve by using this destination.
HubSpot contacts store information about the individuals that interact with your business. Your team uses the contacts that exist in HubSpot to build the Experience Platform audiences. After sending these audiences to HubSpot, their information is updated and each contact is assigned a property with its value as the audience name that indicates which audience the contact belongs to.
Refer to the sections below for any prerequisites that you need to set up in Experience Platform and HubSpot and for information that you must gather before working with the HubSpot destination.
Before activating data to the HubSpot destination, you must have a schema, a dataset, and audiences created in Experience Platform.
Refer to Experience Platform documentation for Audience Membership Details schema field group if you need guidance on audience statuses.
Note the following prerequisites in order to export data from Platform to your HubSpot account:
In order to export data from Platform to your Hubspot account you need to have a HubSpot account. If you do not have one already, visit the Set up your HubSpot account page and follow the guidance to register and create your account.
You need your HubSpot Access token
to allow the HubSpot destination to make API calls through your HubSpot private app within your HubSpot account. The Access token
serves as the Bearer token
when you authenticate the destination.
If you do not have a private app, follow the documentation to Create a private app in HubSpot.
The private app should be assigned the scopes below:
crm.objects.contacts.write
, crm.objects.contacts.read
crm.schemas.contacts.write
, crm.schemas.contacts.read
Credential | Description | Example |
---|---|---|
Bearer token |
The Access token of your HubSpot private app. To obtain your HubSpot Access token follow the HubSpot documentation to make API calls with your app’s access token. |
pat-na1-11223344-abcde-12345-9876-1234a1b23456 |
HubSpot private apps are subject to Rate Limits. The number of calls your private app can make is based on your HubSpot account subscription and whether you’ve purchased the API add-on. Additionally also refer to the Other Limits.
HubSpot supports update of identities described in the table below. Learn more about identities.
Target Identity | Example | Description | Considerations |
---|---|---|---|
email |
test@test.com |
Email address of the contact. | Mandatory |
This section describes all the audiences that you can export to this destination.
This destination supports the activation of all audiences generated through the Experience Platform Segmentation Service.
This destination also supports the activation of the audiences described in the table below.
Audience type | Description |
---|---|
Custom uploads | Audiences imported into Experience Platform from CSV files. |
Refer to the table below for information about the destination export type and frequency.
Item | Type | Notes |
---|---|---|
Export type | Profile-based |
|
Export frequency | Streaming |
|
To connect to the destination, you need the View Destinations and Manage Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.
Within Destinations > Catalog search for HubSpot. Alternatively you can locate it under the CRM category.
Fill in the required fields below. Refer to the Gather the HubSpot private app access token section for any guidance.
To authenticate to the destination, select Connect to destination.
If the details provided are valid, the UI displays a Connected status with a green check mark. You can then proceed to the next step.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
Read Activate profiles and audiences to streaming audience export destinations for instructions on activating audiences to this destination.
To correctly send your audience data from Adobe Experience Platform to the HubSpot destination, you must go through the field mapping step. Mapping consists of creating a link between your Experience Data Model (XDM) schema fields in your Platform account and their corresponding equivalents from the target destination.
To correctly map your XDM fields to the HubSpot destination fields, follow the steps below:
Email
identityThe Email
identity is a mandatory mapping for this destination. Follow the steps below to map it:
email
.Source Field | Target Field | Mandatory |
---|---|---|
IdentityMap: Email |
Identity: email |
Yes |
An example with the identity mapping is shown below:
To add any other attributes you want to update between your XDM profile schema and your HubSpot account repeat the steps below:
A few available mappings between your XDM profile schema and Hubspot are shown below:
Source Field | Target Field |
---|---|
xdm: person.name.firstName |
Attribute: firstname |
xdm: person.name.lastName |
Attribute: lastname |
xdm: workAddress.street1 |
Attribute: address |
xdm: workAddress.city |
Attribute: city |
xdm: workAddress.country |
Attribute: country |
An example using these attributes mappings is shown below:
When you are finished providing the mappings for your destination connection, select Next.
To validate that you have correctly set up the destination, follow the steps below:
Log in to the HubSpot website, then navigate to the Contacts page to check the audience statuses. This list can be configured to display columns for the custom properties created with the audience name with their value being the audience statuses.
You can alternatively drill down into an individual Person page and navigate to the properties displaying the audience name and audience statuses.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.
Additional useful information from the HubSpot documentation is below:
This section captures the functionality and significant documentation updates made to this destination connector.
Release month | Update type | Description |
---|---|---|
September 2023 | Initial release | Initial destination release and documentation publish. |