Overview#
The HubSpot Fields Mapping feature allows you to map Livestorm people attributes to your HubSpot Contacts properties. Using this feature, you can push standard and custom people attributes from Livestorm to your favorite Contacts properties. For more information about custom people attributes and how to create them, please refer to this article.
Make sure first your event registration page is set up to collect the Livestorm attributes mapped to HubSpot Contacts. If you aren’t collecting registrant data properly for your mapped attributes, no data coming from registrants input will be sent to HubSpot.
Default Mapping#
Once you have enabled the HubSpot integration on your workspace, we apply a default synchronization between Livestorm standard attributes and standard HubSpot properties, called default mapping.
On the Livestorm side this default mapping only concerns the registration attributes. To map attendance or engagement data, you need to edit the mapping and apply your custom one.
At the Contact level, the following default mapping is used for the default Contact properties. This mapping is applied by default if you do not edit your integration.
Livestorm people attribute |
HubSpot Contact Property |
First Name |
First Name |
Last Name |
Last Name |
Email |
Email |
Company |
Company (matching an Company Name) |
Job Title |
Job Title |
Address |
Street Address |
City |
City |
Country |
Country |
Phone Number |
Phone Number |
Website |
Website |
LinkedIn |
LinkedIn URL |
Twitter |
Twitter Username |
Country Code |
Country/Region Code |
Use a dynamic mapping#
If you want to push data from Livestorm to your HubSpot Contacts, you can define a dynamic custom mapping between a Livestorm attribute and a HubSpot Contact property. We propose a wide variety of attributes on the Livestorm side: registration data entered by your registrants (including your custom attributes), technical information of the visitor's browser (country deduced from IP address, browser info, UTM, …) and also the attendance data (attendance rate, number of questions, …) specific to the participant during the Livestorm session. You can open the mapping page to have the full list of available attributes.
For the complete overview of our integration with HubSpot, feel free to read our dedicated article. This section shows you how to define the custom mapping of your choice between Livestorm attributes and HubSpot Contact properties.
1
After your HubSpot integration is enabled, in the settings tab go to the Attributes mapped section (look for the Edit text and click on it).
2
You can then see the current Contact properties mapping.
3
To add a new attribute to map, click on the blue button Map an attribute at the bottom.
4
Then choose a Livestorm attribute from the drop-down list (you can also start from the right and select a HubSpot Contact property first). Be careful to select compatible types of Livestorm attributes and HubSpot fields: for instance you can’t push a number from Livestorm into a HubSpot datetime property. To avoid mistakes, non-compatible fields are greyed out.
5
Click on the blue button at the bottom right of the page to Save changes for your mapping. If you need to remove a mapping already configured, just hover over the row and click on the trash icon on the right.
If you want to always send the same value instead of a value coming from a Livestorm attribute, you can use a default value. Simply follow those steps:
1
Add a new mapping row and start on the right side to select your HubSpot Contact property first and then search on the left for a value in the Livestorm column.
2
Press the button Use {value} as a default value (please note that if you have selected a drop-down select at the step 1, then the only possible values will be displayed automatically):
3
Then click on Save at the bottom of the page. The row will indicate “Default value” with a Text type. And you’re all set! The value you have entered will be pushed for any Livestorm event for all the registrants!
FAQs#
Yes, of course! You can map the Livestorm connection link to any standard or custom Contact property of your choice on your HubSpot account.
The Livestorm attributes are pushed to HubSpot when someone registers for an event, when a session this person was registered for has ended, and whenever this person watches a replay or an on-demand event.
In order to not tamper with your existing data in HubSpot, Livestorm will always only update when the target field is empty. Meaning we will only update your properties in HubSpot if they are not already filled.
Yes, Livestorm natively proposes the 5 UTMs as attributes. Simply map these 5 Livestorm standard attributes to the HubSpot properties where you need the data to be stored. Since HubSpot does not have by default properties for the UTM, we recommend you to create 5 custom properties on your Contact for the UTMs.
Not only the form fields! You can also map technical data (such as the browser or the country of the attendee) and attendance/engagement data (such as the number of polls answered or the attendance rate). Check here to discover all the data you can map. This means you can also use attributes mapping if you register your contacts from an external website outside of Livestorm (such as an HubSpot form).
Yes, this is possible. The value contained in a Livestorm attribute can be useful into different HubSpot properties for different workflows or different teams using the CRM with different properties.
No, this is not possible. One HubSpot property can receive only one value from Livestorm. Otherwise, there can be competition and data overwritten. So, a property can be mapped only once, then this property mapped disappears from the list of the remaining fields.
To view data for your Contacts, go to a Contact record page and check the properties on the right panel. If the properties you wish to review do not appear in the list, you can go on "View all properties" or you can also manually change the layout.
If you delete a Livestorm custom attribute or a HubSpot property, Livestorm will remove this field from the mapping before sending data to HubSpot to avoid introducing broken values. You will be asked in the interface of the fields mapping to use a new valid attribute before saving your mapping again.
We allow to map any field but it's important to select compatibles types for your fields between Livestorm and HubSpot. Because if you push an incorrect data to a field, HubSpot will refuse it and block the creation of the Contact. To prevent this potential issue, a protection exists to only map fields with a compatible type: the fields with a not compatible type are displayed but greyed to prevent error. For example, you can't push a number to a date and you need to map a HubSpot drop-down select (containing defined values) with a drop-down list on Livestorm. If you want to keep a maximum of freedom, use a text type on HubSpot.