You need: Salesforce Administrator access. Allow 30–60 minutes, plus about 15 minutes per extra Business Unit. We recommend completing these steps with your Salesforce Administrator.
In this article
Running Alongside the Salesforce Native ConnectorHow It Works:Step 1: Create the Livestorm Session ID fieldStep 2: Install the Salesforce native connector firstStep 3: Answer "Yes" to Salesforce compatibilityRouting Campaigns to Several Business UnitsSetup Pattern:Step 1: Create the Record TypesStep 2: Create an Integration UserStep 3: Configure Connected Campaigns per Business UnitStep 4: Assign Marketing App ExtensionStep 5: Install Connector per WorkspaceTroubleshooting Advanced Setup
Advanced Salesforce configuration
Do the section(s) that match your setup before installing the connector in Integry—the installer asks for values you create here. Then go back to Set up the Account Engagement (Pardot) connector.
| What you want to do | What you need from this page |
|---|---|
| Account Engagement connector only, one Business Unit | Nothing — the base setup is enough |
| Run it alongside the Salesforce native connector | Running alongside the Salesforce native connector |
| Route campaigns to several Business Units | Routing campaigns to several Business Units |
| Both of those | Both sections, in that order |
In this article
Running Alongside the Salesforce Native Connector#
Both connectors create a campaign for every session. To avoid ending up with two, the Account Engagement connector looks for an existing campaign using a custom field on the Campaign object before creating its own.
How It Works:#
1 Salesforce native connector creates the campaign and writes the session ID into Livestorm_Session_ID__c.
2Account Engagement connector checks for a campaign with that session ID:
FOUND: Reuses that campaign.
NOT FOUND: Creates a new campaign.
RESULT: one Salesforce campaign, one Account Engagement campaign
Step 1: Create the Livestorm Session ID field#
1 Go to Setup → Object Manager → Campaign → Fields & Relationships → New.
2 Select field type Text, then click Next.
3 Configure the field parameters:
| Setting | Value |
|---|---|
| Field Label |
Livestorm Session ID |
| Length | 80 |
| Field API Name |
Livestorm_Session_ID__c |
| External ID | ✓ Recommended |
| Unique | ✓ Recommended |
4 Set Field-Level Security: Ensure visible for relevant profiles (including integration user).
5 Add to Campaign page layout(s) and click Save.
Critical: The API name MUST be exactly Livestorm_Session_ID__c. Salesforce derives it from the label, so entering the label above gives the right result — but check before saving. A different API name means the connector never finds existing campaigns, and you get two campaigns per session.
Step 2: Install the Salesforce native connector first#
Install it in each workspace before the Account Engagement connector, so campaigns and session IDs exist when the Account Engagement connector runs. See the Salesforce native connector setup guide.
Step 3: Answer "Yes" to Salesforce compatibility#
During Part 2, Step 7 of the Account Engagement connector setup, answer Yes to the Salesforce compatibility question.
Routing Campaigns to Several Business Units#
Routing uses campaign record types. Each Business Unit is configured to sync only its own record type, and each workspace’s connector stamps that record type on the campaigns it creates.
Setup Pattern:#
1 Workspace + 1 Record Type per Business Unit.
Three Business Units, require three workspaces and three record types.
| Workspace "EMEA Events" | → connector configured with Record Type = BU_EMEA |
| → connector configured with Record Type = BU_EMEA | |
| → only the EMEA Business Unit syncs BU_EMEA | |
| → campaign lands in the EMEA Business Unit |
Several Business Units but only one Livestorm workspace? This setup will not work with a single workspace because all events would route to the same Business Unit. Contact your CSM to discuss options.
Record type names have no technical meaning. Name them so it’s obvious which one routes where. This guide uses BU_US, BU_EMEA, BU_APAC as an example.
Step 1: Create the Record Types#
Go to Setup → Object Manager → Campaign → Record Types → New.
Create one record type per Business Unit. If running both connectors, add one additional holding record type:
| Record Type | Routes to | Purpose |
|---|---|---|
| Livestorm_Pending (only with the Salesforce native connector) | None | Default holding state — never syncs anywhere |
| BU_US | US Business Unit | Campaigns from the US workspace |
| BU_EMEA | EMEA Business Unit | Campaigns from the EMEA workspace |
| BU_APAC | APAC Business Unit | Campaigns from the APAC workspace |
For each Record Type:
Enter Label (e.g., BU_US), verify active status.
Enable for the profiles that need access, including your integration user’s profile
Select Campaign Layout and Save.
** Why Livestorm_Pending is needed when running both connectors**: the Salesforce native connector creates the campaign first, before anything knows which Business Unit it belongs to. Giving it a record type that syncs nowhere keeps it in a holding state until the Account Engagement connector assigns the real one. Without it, campaigns route to whichever Business Unit matches the default record type.
Step 2: Create an Integration User#
We recommend a dedicated Salesforce integration user to control record type defaults.
Alternatives: an existing System Administrator user, or a Permission Set instead of a profile. See the Salesforce native connector documentation.
1 Clone Profile: Go to Setup → Profiles, clone Standard User (or Minimum Access), and name it Livestorm Integration Profile.
2 Set System & User Permissions:
| Category | Permissions |
|---|---|
| System Permissions | ✓ API Enabled · ✓ Approve Uninstalled Connected Apps |
| User Permissions | ✓ Marketing User |
| Campaigns | Read, Create, Edit, View All — plus all fields |
| Leads, Contacts, Accounts (only with the Salesforce native connector) | Read, Create, Edit, View All — plus all fields |
Approve Uninstalled Connected Apps” lets the user authorize the Pardot connected app. It is granted by default on the System Administrator profile but must be added manually on a custom profile: Setup → Profiles → Livestorm Integration Profile → System Permissions → check it → Save.
3 Create User: Go to Setup → Users → New User, assign Livestorm Integration Profile, and check Marketing User. Keep the credentials — you’ll need them to authenticate the connector.
4 Assign Record Types: On Livestorm Integration Profile → Object Settings → Campaigns:
Move all Business Unit record types to Selected.
If running both connectors: Set Livestorm_Pending as the Default record type.
Save
Crucial: If running both connectors across multiple Business Units, Livestorm_Pending must be the default record type. This is the step most likely to be missed. If the default is anything else, campaigns sync to the wrong Business Unit — or to all of them.
Step 3: Configure Connected Campaigns per Business Unit#
In Account Engagement Settings:
1 Switch to the target Business Unit.
2 Go to Account Engagement Settings → Connectors → Edit Salesforce Connector → Campaigns tab.
3 Select sync rules:
✅ Check the record type for THIS Business Unit.
❌Uncheck all other Business Unit record types.
❌Uncheck Livestorm_Pending.
4 Save, then repeat for the next Business Unit
Never let two Business Units sync the same record type, the same campaign is created in both.
Step 4: Assign Marketing App Extension#
Ensure all Business Units are assigned in the Marketing App Extension (Part 1, Step 3 of setup guide).
Step 5: Install Connector per Workspace#
Install the connector in each workspace using its dedicated Business Unit ID and Record Type.
Troubleshooting Advanced Setup#
| Symptom | Check |
|---|---|
| Two campaigns per session | Salesforce compatibility answered No, wrong Livestorm_Session_ID__c API name, or two Pardot Campaigns flows active |
| Livestorm_Session_ID__c empty | The Salesforce native connector isn’t installed on this workspace, or the field isn’t visible to its user |
| Record type stuck on Livestorm_Pending | The Pardot connector isn’t active on this workspace, or the profile lacks Edit access to the target record type |
| Campaign never reaches Account Engagement | No Business Unit syncs that record type, or Connected Campaigns is disabled. Allow up to 30 minutes first |
| Campaign in the wrong Business Unit | The workspace connector’s record type or Business Unit ID, the Connected Campaigns selection per Business Unit, or, when running both connectors, the integration user’s default record type |
| Campaign in several Business Units | Two Business Units sync the same record type, or one syncs Livestorm_Pending |
| Prospect created, no external activities | The Marketing App Extension isn’t assigned to that Business Unit |
Join our Livestorm Live Product Demo
During this 30-minute live event, we will introduce you to the platform. You will learn how to use Livestorm for your webinars.