Use Salesforce With Livestorm

Livestorm's Salesforce integration streamlines the lead generation and lead qualification process. 

Here's what is included in this integration:

  • Create Leads in Salesforce for every new registrant to your Livestorm events, if they don't exist yet.
  • Choose whether to create Campaigns in Salesforce for every new Livestorm event that is published.
  • Choose whether to attach every registrant — who is replicated either as a Lead in Salesforce — as a Campaign Member, linked to the Campaign they registered for. Therefore, you'll have a per-event overview of all your registrants.
  • After an event ends, all Campaign Members will be updated with their own attendance status en engagement information so that you can qualify/score them and nurture them accordingly. Additionally, this per event/registrant zooming lens will let you analyze the impact of your Livestorm events if new Salesforce Oppositions are created/won following an event.

This integration is only available in private beta at the moment for Enterprise customers.

You can activate it first on your Salesforce's sandbox account, in case you want to make a few tests before activating it on your production account.

In this article

Requirements & Permissions

To use our Salesforce integration, we require the following profile and set of permissions:

  • System Administrator: we need the user who activates the Salesforce integration to have a System Administrator profile. This profile is mandatory as it grants Livestorm API access to your Salesforce account.
  • Marketing User: the user who manages Livestorm's Salesforce integration needs to have the Marketing user capability, which is used to interact with the native Campaign and Campaign Member objects.
  • No mandatory custom fields: this first version can not handle mandatory custom fields. The integration can't be activated in such case.

If these profile and permissions requirements are not met, the authentication will not succeed. 

Don't hesitate to ask your Salesforce System Administrator for any help on these requirements.

In order to check your current profile and permissions, navigate to the Users section in your Salesforce setup admin panel, and check that you have the following profile and permissions.

Object Properties Managed by Livestorm

Livestorm’s Salesforce integration needs to initially set up custom properties that are required to properly work. These properties will allow you to have a detailed overview of your attendees’ engagement during your Livestorm events.

Lead object

  • A new custom field named 'Livestorm ID' (ID: Livestorm_ID__c) will be created for the Lead object. This field will store an internal Livestorm ID used to identify the relationship with their Livestorm counterpart.

Campaign Object

Two custom fields will be created by Livestorm on the Campaign object:

  • A new custom field on the Campaign object named 'Livestorm URL' (ID: Livestorm_Custom_Event_URL__c) will be created, which will store the event's Livestorm URL.
  • Similar to the Lead, Contact, and Account objects, an internal ID called 'Livestorm ID' (ID: Livestorm_ID__c) will be created and will store the relationship between a Campaign and its related Livestorm event.

Campaign Member Object

Livestorm will create the following new custom fields on the Campaign Member object to store detailed engagement data on behalf of a Lead/Contact for a given Livestorm event session:

  • Similar to the Lead, Contact, and Account objects, an internal ID called 'Livestorm ID' (ID: Livestorm_ID__c) will be created and will store the relationship between a Campaign Member and its related Livestorm event and registrant counterparts.
  • 'Livestorm status' (ID: Livestorm_Custom_Event_Status__c): The attendance status of the registrant: Registered, Attended live, Watched replay, Watched on-demand.
  • 'Livestorm attendance duration' (ID: Livestorm_Custom_Attendance_Duration__c): The attendance duration of the attendee in seconds, for instance, 2880 (for 48 minutes).
  • 'Livestorm attendance rate': (ID: Livestorm_Custom_Attendance_Rate__c): The attendance rate of the attendee, for instance, 78 (for 78%).
  • 'Livestorm number of comments' (ID: Livestorm_Custom_Comments_Count__c): The number of comments the attendee posted.
  • 'Livestorm number of questions asked' (ID: Livestorm_Custom_Questions_Count__c): The number of questions the attendee sent.
  • 'Livestorm number of poll answers' (ID: Livestorm_Custom_Polls_Count__c): The number of poll answers the attendee answered.
  • 'Livestorm number of upvotes' (ID: Livestorm_Custom_Upvotes_Count__c): The number of upvotes the attendee did.

Limitations

As this is the first version of a Salesforce integration, here are its current limitations:

  • This version doesn't support custom fields on the Lead object: If some of your custom fields on these objects are mandatory in order to create new entries, Livestorm won't be able to create them for now.
  • If the multi-currency mode is enabled on your Salesforce account, our integration won't be able to support it out of the box, as all objects (e.g Lead, Contact, Account) will have a new mandatory "Lead currency" property that Livestorm won't be able to fill automatically. This field would have to be removed from the Lead views to make the integration work.

Set Up Salesforce With Livestorm

To start using the Salesforce integration, you first need to activate it and authenticate your Salesforce account with Livestorm.

1
Go to your App marketplace and select the Salesforce card.

2
Then, you need to Connect your Salesforce account with Livestorm.

3
Choose which Salesforce environment you'd like to connect with Livestorm. We currently support the following environments:
  • Production: you'll be redirected to Salesforce's production environment, to authenticate with your real Salesforce account.
  • Sandbox: you'll be redirected to Salesforce's testing/sandbox account.
After selecting the environment that suits you, click on the Connect button.

4
You'll be redirected to Salesforce to authenticate your account with Livestorm.

5
After allowing access to your Salesforce account, you'll be redirected back to Livestorm where you'll now be able to configure your integration.

Select which configuration suits you the most. Here's what Livestorm offers:
  • Create new Contacts if they don't exist yet
  • Create new Leads if they don't exist yet
  • Create new Accounts if they don't exist yet
  • Create Campaigns
  • Create Campaign members
For the Leads, Contacts, and Accounts objects, we give you the ability to choose which trigger is more relevant for you, to create new entries. The available triggers that can be used are the following ones:
  • Someone registered for an event
  • Someone attended a live event
  • Someone watched the recording of an event
  • Someone watched an on-demand event
In any case, Livestorm will always check first that a Lead/Contact doesn't exist before creating it.

To use the "Create Account" triggers, you must activate the "Company" registration field in your registration pages. We use this field to create the Account entry and link it with the relevant Leads and Contacts.
As our customers use Salesforce in many different ways, it's up to you to decide which objects to create, and after which trigger. For instance, here's what we suggest:
  • Create a new lead when someone registers to one of your events
  • Create a new contact when someone watches a live event
  • Create a new account when someone watches a live event
  • Create new campaigns when new Livestorm events are scheduled
  • Create new campaign member when leads and contacts engage with your events
  • ...etc
6
At any time, you can disable your Salesforce integration and disconnect your account by clicking on the Disconnect red button. It can be useful in case you test the integration in sandbox mode and then switch to the production mode.
Just Confirm disconnection and your account will no longer be connected.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.