Connect Livestorm and Account Engagement (Pardot)

Account Engagement (formerly Pardot) is Salesforce’s B2B marketing automation platform, covering email automation, targeted campaigns, and lead management.

Our connector links your Livestorm workspace to your Account Engagement instance: every session gets its own campaign and list, every registrant becomes a prospect, and their attendance and engagement are recorded automatically—with no manual import.

This article explains what the connector does, how it works, and which setup guide you need.

Related Articles & Sub-Pages#

• Set up the Account Engagement (Pardot) connector

• Advanced Salesforce configuration

What the Connector Does#

Once the connector is active on a Livestorm workspace, this happens automatically for every new session in that workspace:

People can register either through your Livestorm registration forms or through your own Account Engagement forms—the connector supports both.

Everything lands on the prospect record, where it can feed your automation rules, segmentation rules, and Engagement Studio programs—within the limits that Account Engagement applies to external activities.

What It Does Not Do#

Worth knowing before you start:

• It is not retroactive. It only creates campaigns, lists, prospects, and external activities for sessions created after it was activated. If you test on a session created beforehand, nothing will sync.

• It cannot use a campaign you already have. A session can only be mapped to a campaign the connector created itself. (The exception is when you also run our Salesforce native connector.)

• It does not create Leads, Contacts, or Campaign Members. Those are handled by our separate Salesforce native connector, which you can run alongside this one.

Which Guide Should I Follow?#

Everyone follows Setup the Account Engagement (Pardot) connector. That is the whole setup for most customers.

Two situations need some extra Salesforce configuration first:

Both apply? Do both, in that order, then the setup guide.

Prerequisites and Permissions#

The Livestorm/Account Engagement integration is only available to Livestorm Enterprise customers, as a paid add-on.

Before you set up the connector, make sure that:

1. You have a Plus, Advanced, or Premium Account Engagement account, and you are using the Account Engagement Lightning app.

2. You have activated Connected Campaigns between Account Engagement and Salesforce.

3. You have access to both your Livestorm workspace and your Account Engagement instance.

User Permissions#

To check your current profile and permissions, go to the Users section of your Salesforce setup admin panel.

Key Concepts & Architecture#

Key Objects Used#

About External Activities#

External Activities is an Account Engagement feature for tracking prospect engagement that happens outside Account Engagement. By capturing attendance data as an external activity, you can see which prospects attended your event and follow up with them afterwards.

Data from active external activities can be used in automation rules, segmentation rules, and Engagement Studio programs. Account Engagement does apply its own rules and limits to how external activities work in each of those tools, so please check Salesforce’s Considerations for Using External Activity before you build a workflow around them.

Key Triggers and Actions#

Whenever you create a session in Livestorm, the connector will:

• Create a campaign in Salesforce, which Connected Campaigns then syncs to Account Engagement (if you also run the Salesforce native connector, the campaign it created for that session is reused instead, so you do not end up with two).

• Create a list associated with that campaign.

Whenever someone registers for that session, it will:

• Create or update a prospect, using the fields you mapped between Livestorm and Account Engagement:

  • If a prospect with the same email address already exists, it is updated with the mapped Livestorm fields and added to the associated list.

  • Otherwise, a new prospect is created and added to both the associated campaign (as Source Campaign) and the associated list.

• Create an external activity storing the registration data on the prospect.

Whenever the session ends, it will:

• Update the prospect and create external activities storing the attendance data.

Whenever someone watches the replay of the session, it will:

• Create external activities storing the replay-watching data.

Key External Activities List#

Nine external activities are available. Each one includes the date and time it was created:

Data Flow & Integration Patterns#

All prospects who register are added to the list. In addition, brand-new prospects are also added to the campaign.

Using Both Salesforce and Account Engagement Connectors#

Livestorm has two independent connectors, and you can run both on the same workspace. They are complementary:

Running both gives you attendance on the Salesforce side and prospect-level engagement in Account Engagement, without duplicate campaigns: the Account Engagement connector looks for an existing campaign using a session ID field on the Campaign object and enriches that campaign instead of creating a second one.

Setting up that session ID field is the one extra thing you have to do.
See 🔗 Advanced Salesforce configuration → Running alongside the Salesforce native connector.

Working with Several Business Units#

If you have more than one Account Engagement Business Unit, the connector can send each Livestorm workspace’s data to a specific Business Unit. Routing works through 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.

The pattern is one Livestorm workspace and one record type per Business Unit—three Business Units means three Livestorm workspaces and three record types.

🔗 Advanced Salesforce configuration → Routing campaigns to several Business Units.

Setting Up and Testing#

We built the Livestorm/Account Engagement integration with our partner Integry, an Integration Platform as a Service (iPaaS) that lets us build cloud-based integrations quickly.

To set up your integration, simply go to your Integry marketplace (ask the link to your Customer Success Manager), select the Salesforce Pardot card, and install the Pardot Campaigns flow.

Before you use the connector for real events, run a test on a new session: publish it, wait for the campaign to appear in Account Engagement, register a test email, then attend and check the external activities on the prospect.

See 🔗  Set up the Account Engagement (Pardot) connector → Test your setup.

If your setup needs advanced Salesforce configuration, do that first — the installer asks for values you create there. Not sure? See #Which guide should I follow?

Frequently Asked Questions#

Is the connector retroactive?

Not at the moment. It only creates a new campaign, list, prospects, and external activities for sessions created after activation. If you test on a session created before you enabled it, the data will simply not synchronize with your Account Engagement instance.

How do I enable the integration in my Livestorm account?

Because the connector is built with our partner Integry, it cannot be enabled from your Livestorm account at the moment.

Go to our Integry Marketplace (ask the link to your Customer Success Manager) and follow the setup guide: 🔗 Set up your integration

How does the integration work with Livestorm?

It lets Enterprise customers with the paid add-on link their Livestorm workspace to their Account Engagement instance. It creates campaigns, lists, and prospects associated with Livestorm sessions and stores attendance data on the Prospect object using External Activities.

Can I map Livestorm sessions to campaigns I already have?

Not at the moment. A session can only be mapped to a campaign that our connector created in your Account Engagement instance.

Can I rename the campaigns the connector creates to match my own naming conventions?

Absolutely. The mapping is done at the campaign/session ID level, so renaming a campaign afterward will not break the connection.

What are External Activities in Account Engagement?

A feature that lets you track prospect engagement data from outside Account Engagement. By capturing attendance data as an external activity, you can track which prospects attended your Livestorm event. Data from active external activities can be used in automation rules, segmentation rules, and Engagement Studio programs, subject to Account Engagement’s own rules and limits — see Salesforce’s Considerations for Using External Activity.

Where can I see these external activities?

External activities are stored on the Prospect object when someone registers and when a session ends. To view them, click the prospect and open the External Activities tab.

Where can I find all the registrants for my session?

Every prospect who registers for a session is added to the list created for that session.

What is the difference between a list and a campaign?

A list resembles the more traditional CRM definition of a marketing campaign, so every prospect who registers for a session is stored in the corresponding list.

A campaign exists mainly to track a prospect’s first interaction with you—the source—so we associate only new prospects originating from that session with the campaign our connector creates.

In simpler terms: a new prospect is added to both the list and the campaign; an existing prospect is added to the list only.

What if there are several sessions for the same event?

Each session is handled individually, whether or not it belongs to the same event. Each session gets its own campaign and list, both of which include the session date and time, so you can distinguish sessions from the same event.

Will registering create duplicate prospects if the person already exists?

No. When someone registers, we check whether a prospect with the same email address already exists. If not, we create one; if they do exist, we simply update them with the new registration information. More about lists and campaigns.

What if several prospects already exist with the same email address?

We update the prospect with the most recent activity, based on Account Engagement’s existing logic.

Can I use the Account Engagement connector and the Salesforce native connector at the same time?

Yes, and many customers do. The Salesforce native connector handles Leads, Contacts, and Campaign Members; this connector handles Prospects, Lists, and External Activities.

What should I do if I encounter an issue?
Start with Set up the Account Engagement (Pardot) connector → If something did not sync. If that does not help, contact our support team.

To avoid duplicate campaigns, complete: 🔗Advanced Salesforce configuration → Running alongside the Salesforce native connector first.

Can I send different Livestorm workspaces to different Business Units?

Yes — one workspace per Business Unit, routed with campaign record types.

See: 🔗Advanced Salesforce configuration → Routing campaigns to several Business Units.