Setting up this connector involves two steps:
1 In Account Engagement: Register Livestorm external activity types so attendance data can be captured.
2 In the Integry marketplace: Install and configure the Pardot Campaigns flow.
For a full breakdown of connector features and behavior, consult the main documentation:
đź”— Connect Livestorm and Account Engagement (Pardot)Â
Before You Start#
The integration is available to Livestorm Enterprise customers as a paid add-on.
You need Salesforce Administrator or Marketing Setup Administrator access and admin access to your Livestorm workspace.
Connected Campaigns must be enabled between Salesforce and Account Engagement.
Does your setup need extra Salesforce configuration?
If you use the native Salesforce connector or manage multiple Business Units, complete those setup configurations first. Please check this article: Connect Livestorm and Account Engagement (Pardot)
- Complete the connection between Livestorm and Account Engagement (Pardot) prior to moving to Part 2.
- The Part 2 installer will explicitly ask for credentials, tokens, or configuration values generated during the Livestorm-Pardot connection steps.
Not sure? Please check your Advanced Salesforce configuration
Part 1: Register the Livestorm External Activity Types#
To start tracking attendance data as external activities in Account Engagement, you need to create a Marketing App Extension and register the external activity types.
Step 1: Create a new Marketing App Extension#
1Log in to Account Engagement
2Access setup: Log in to Account Engagement and head to Setup > Account Engagement > Marketing App Extensions, and select New
3Fill in the extension settings:
Name: Enter Livestorm
API Name: Enter Livestorm
Permissions: Enable Active in Automations to make Livestorm activity data accessible across Account Engagement. (automation rules, segmentation rules, and Engagement Studio programs, within Account Engagement’s own limits)
Step 2: Create the Livestorm activity types#
1Go to the Related tab of your Livestorm Marketing App Extension.
2Next to Activity Types, select New.
3Create the first activity type:
Activity Name: People registered
API Name: People_registered
Check Active in Automations.
4Repeat those steps to create the remaining activity types:
Session attended — API Name: Session_attended
Session not attended — API Name: Session_not_attended
Attendance rate — API Name: Attendance_rate
Attendance duration — API Name: Attendance_duration
Questions asked — API Name: Questions_asked
Messages sent — API Name: Messages_sent
Has watched replay — API Name: Has_watched_replay
Has watched on-demand— API Name: Has_watched_on_demand
Critical: Ensure that the API name matches the exact name mentioned in this documentation for accurate tracking. API names are case-sensitive — SessionAttended will not work, **it has to be Sessionattended**. A single mismatch silently drops that one activity type.
Already set this up previously? Attendance rate (Attendance_rate) is a recent addition. Add it the same way as the others. If you do not, everything else keeps syncing — you simply will not see attendance rate on your prospects.
5 Once completed, you should have 9 activity types created under your Livestorm Marketing App Extension:
Step 3: Assign your Business Unit#
Go to the Related tab of your Livestorm Marketing App Extension.
In Business Unit Assignments, make sure the correct Business Unit is assigned. If not, click New and add your Business Unit.
Several Business Units? Add every Business Unit that will receive Livestorm data. An unassigned Business Unit still receives campaigns and prospects, but no external activities at all. This is the step most often missed in multi-Business-Unit setups.
Step 1: Integry Marketplace Authentication#
Access the Integry marketplace endpoint provided by your CSM. Select Sign in → Login to the app using your Livestorm integration credentials (a dedicated service account is recommended).
Step 2: Install the Pardot Campaigns flow#
Under Guided Flows, locate the Salesforce Pardot card and click Setup to install the Pardot Campaigns flow.
No “Salesforce Pardot” card? The connector may not be enabled on your plan or workspace yet. Contact your Customer Success Manager or our support team.
Step 3: Connect to Account Engagement#
Enter your Host URL and Business Unit ID:
Host URL:
Business Unit ID:
In Salesforce, locate the 18-character string starting with 0Uv under Marketing Setup > Business Unit Setup.
Business Unit ID: Detailed information can be found in the Pardot API documentation
Then log into Account Engagement using your usual credentials. Once you are connected, click Next.
First time setting this up? You can run through the whole setup on a sandbox first.
Several Business Units? Double-check the Business Unit ID. It decides where this workspace’s prospects and lists are created.
Step 4: Connect with Salesforce#
1 Select your environment (Sandbox or Production).
2 Connect to your Salesforce account based on your setup:
| One Business Unit |
A user with the System Administrator profile |
| Several Business Units |
Your dedicated Livestorm integration user — see Advanced Salesforce configuration → Routing campaigns to several Business Units |
Step 5: Map your fields#
Now the fun part begins. You will be asked to map the fields of your Account Engagement Prospect with the fields available on the Livestorm Registrant object: for every Account Engagement field you want to fill with Livestorm data, select the corresponding Livestorm field. You will also see your own Account Engagement custom fields in the list, letting you tailor the flow to your specific rules and needs.
| Campaign Type |
Whatever suits your organisation — we suggest Webinar |
| Record Type |
One Business Unit: leave it empty. Several Business Units: select the campaign record type for this workspace’s Business Unit. |
Even with a single Business Unit, you can set a record type here if your Salesforce → Account Engagement campaign routing already relies on one. Otherwise leave it empty.
Step 7: Answer the Salesforce compatibility question#
This is what prevents duplicate campaigns. Answering Yes tells the connector to look for the campaign the Salesforce native connector already created, instead of creating its own.
Step 8: Save and activate#
🎉 Your integration is ready to be enabled — click Save to enable the integration. Make sure the new flow is set to active. You will then see the new flow created.
The integration is enabled across all your events by default, so you do not need to enable it for each event in the Livestorm platform, as you do with other integrations.
Make sure you only have one Pardot flow activated under My Flows. Two or more active flows will create duplicates in your Account Engagement instance and cause connector errors.
Managing Multiple Livestorm Workspaces#
If you have several Livestorm workspaces, repeat Part 2 in each workspace:
One Business Unit: Use the same Business Unit ID everywhere, and leave the record type empty.
Several Business Units: Each workspace needs its own Business Unit ID and record type.
For example:
| US Events |
0Uv...(US) |
BU_US |
US Business Unit |
| EMEA Events |
0Uv...(EMEA) |
BU_EMEA |
EMEA Business Unit |
| APAC Events |
0Uv...(APAC) |
BU_APAC |
APAC Business Unit |
Adapt this to your own workspace names, Business Units, and record types.
Test your setup#
Run this on a test session before you use the connector for a real event.
Before you test#
Create a new session for the test. The connector is not retroactive, so a session created before you activated it will never sync.
Use a fresh test email — one that is not already a prospect, a teammate, or an existing
registrant in Livestorm.
Check that only one Pardot Campaigns flow is active under My Flows in Integry. Two active flows create duplicates.
Check that the Business Unit ID you entered matches the Business Unit you are testing in.
The test#
1Create and publish a session in Livestorm — call it “Pardot test event”, for example.
2Wait for the campaign. In Account Engagement, look for a campaign with the same name under Account Engagement Campaigns and a list with the same name under Prospects → Segmentation Lists. This usually takes under 10 minutes and occasionally up to 30.
Do not go further until the Account Engagement campaign exists — the next step depends on it.
Review the following to determine whether they apply to you:
| Run the Salesforce native connector too |
There is exactly one campaign in Salesforce, and
Livestorm_Session_ID__c is filled in
|
| Have several Business Units |
The campaign is in the right Business Unit — and in no other |
3 Register a test person. Use whichever form you actually use:
A Livestorm registration form — open the session’s registration page and submit it with your
test email address.
One of your own Account Engagement forms — create a form (Content → Forms → Add Form), and in its Campaign field select the campaign the connector created. Open the form link and submit it. The prospect is registered to the matching Livestorm session; this can take up to 10 minutes if registering from Pardot to Livestorm. Confirm it worked by opening the People tab in Livestorm and filtering for the session.
If you use your own Account Engagement forms, the form must point at the campaign for the session you are testing. A form linked to the wrong campaign registers the prospect for the wrong session.
4 Check the prospect. Find them by email in Account Engagement:
A new prospect is added to both the list and the campaign
An existing prospect is updated and added to the list
A People-registered external activity is recorded
5 Run the session. Start the event, join with the test email, stay for at least a minute, send a
chat message and ask a question, then end the event.
6 Check the external activities. After a few minutes, open the prospect and go to the
External Activities tab. You should see Session attended, Attendance duration,
Attendance rate, Messages sent and Questions asked.
7 Check your mapped fields. Confirm the custom fields you mapped in Part 2, Step 5 have been
filled in. If they have, your connector is ready to use. 🎉
To see the other side of it, register a second test email and do not attend. After the session ends, that prospect gets a Session not attended activity instead.
Troubleshooting#
| No campaign at all |
The session predates the connector’s activation, or the flow is inactive. |
| Campaign in Salesforce but not in Account Engagement |
Connected Campaigns is disabled, or you haven't waited 30 minutes yet. |
| One session generated two campaigns |
Disable the duplicate flow or review the Salesforce native connector’s session ID field and Part 2, Step 7. |
| Campaign in the wrong Business Unit |
The Business Unit ID or record type on that workspace’s connector, or the Connected Campaigns record type selection for that Business Unit |
| Prospect created, but no external activities |
The Livestorm Marketing App Extension is not assigned to that Business Unit (Part 1, Step 3) |
| Some external activities missing, others fine |
An API name does not match exactly, or Active in Automations is unchecked on those activity types |
| Prospect updated instead of created |
Expected — the connector matches on email address |
| Custom fields empty on the prospect |
Field mapping was not completed at Part 2, Step 5 |
