Understand the Livestorm Attributes for the Fields Mapping with your CRM

Livestorm provides a way to map Livestorm attributes with your CRM fields, allowing a smooth data synchronization between the two tools.

This article lists all the Livestorm attributes available in the mapping and the meaning of each attribute. For the complete overview of the integrations capabilities, please check out our dedicated documentations:
- Marketo
- HubSpot
- Salesforce
- Pardot

In this article

• List of Standard attributes in Livestorm
• Standard attributes used for registration
• System attributes related to the people in the session
• Important Information

List of Standard attributes in Livestorm

Standard attributes used for registration

Below are the Livestorm attributes you can add in your registration form (check here to see how you can customize your registration page with the attributes you need). The value of the attribute come from your registrant manual entry. Note: the list below is alphabetical, not by importance.

Attribute name (English)	API Name	Attribute Type	Notes
Address	address	Text
Avatar	avatar	Text	The avatar will be provided as a link leading to the picture
City	city	Text
Company	company	Text
Country	country	Text	Warning: this country has to be filled manually on the form! If you want to capture the country automatically based on the visitor IP address, please use the system attribute called "ip_country_name"
Email address	email	Email
Facebook	facebook	URL
First Name	first_name	Text
Job Title	job_title	Text
Last Name	last_name	Text
LinkedIn	linkedin	URL
Phone	phone	Text
Twitter	twitter	Text
Website	website	URL

Note: those are just the standard attributes for the registration. You can add as many custom attributes as you want if you need more or customization info in your forms. Check here for more details.

System attributes related to the people in the session

Below are the Livestorm system attributes. The value of the attribute is populated by Livestorm at each session's steps or people actions, you can't tamper with the value. Note: the list below is alphabetical, not by importance.

Attribute name (English)	API Name	Attribute Type	Notes
Attendance duration	attendance_duration	Integer	Attendance duration (in minutes) of the people for the specific session. Value populated when the session is over.
Attendance rate	attendance_rate	Float	Attendance duration rate (in %) of the people for the specific session. Value populated when the session is over.
Browser name	browser_name	Text	Web browser name used by the people
Browser version	browser_version	Text	Web browser version used by the people
Connection link	connection_link	URL	Unique personal link (URL) of the people to connect to the session
Country code	ip_country_code	Text	Country code deducted from the IP address
Country name	ip_country_name	Text	Name of the country deducted from the IP address
Email status	email_status	Text	Did the people received the Livestorm email(s)?
Event ID	event_id	Text	The unique ID of the Livestorm event
Event name	event_name	Text	The name of the Livestorm event
Geo city	geo_city / ip_city	Text	Name of the city deducted from the IP address
Has attended	attended	Boolean	True if the registrant has attended the live session. False, otherwise. Value populated when the session is over.
Has viewed replay	has_viewed_replay	Boolean	True if the registrant has viewed the replay of a live session (not concerning on-demand views). False, otherwise. Value populated when the session is over.
Messages count	messages_count	Integer	Total number of messages sent in the chat by the participant for the session
OS name	os_name	Text	Operating system (OS) name used by the people
OS version	os_version	Text	Operating system (OS) version used by the people
Password key	password_key	Text	Unique personal key of the people for the session
People ID	people_id	Text	The unique ID of the people
Questions count	questions_count	Integer	Total number of questions asked by the participant for the session
Referrer	referer	Text	Information provided by the web browser to determine the page where the visitor originated from when they arrive on the registration page (not used anymore - use UTM instead).
Registered at	registered_at	Datetime	Datetime when the people registered to the session
Screen height	screen_height	Text	Screen height of the computer used by the people
Screen width	screen_width	Text	Screen width of the computer used by the people
Session date	session_date	Datetime	The estimated started datetime of the session (part of the Livestorm event)
Session ID	session_id	Text	The unique ID of the session (part of the Livestorm event)
Session name	session_name	Text	The name of the session (part of the Livestorm event)
Up votes count	up_votes_count	Integer	Total number of questions upvoted by the participant for the session
UTM campaign	utm_campaign	Text	UTM tag about the campaign
UTM content	utm_content	Text	UTM tag about the content
UTM medium	utm_medium	Text	UTM tag about the medium
UTM source	utm_source	Text	UTM tag about the source
UTM term	utm_term	Text	UTM tag about the term
Votes count	votes_count	Integer	Total number of polls answered by the participant for the session

Important Information

• UTMs fields should be passed through your registration page URL to capture data and then pushed to your CRM. Check here to learn how to configure UTMs.
• The Connection link attribute is more than 100 characters, so choose your target field accordingly in your CRM with a sufficient maximum length.
• The attributes "Has attended" and "Has viewed replay" are set to False by default when the people registers to the session and updated later when the session is over.