Once you have your integration authenticated with Marketo’s API, you’ll need to name it and tell it when and how it should fire. Start off with typing a descriptive name into the Integration Name field.

Below the Integration Name is the trigger configuration. This is split into the actions that the integration can take on the left, and the triggers that will elicit those actions on the right.

Integration Triggers

Action: Clone Program

The first action handles cloning Marketo programs to create new Splash events or update an existing Marketo Program. To enable this option, select Create or Update from the Trigger dropdown. We recommend selecting Update, as this trigger also fires when an event is created.

Action: Create or Update Leads

The second action focuses on guests: when to create and update Marketo leads to match your Splash guests. This is controlled by attendee status changes. In the dropdown, choose the attendee statuses you want to result in synchronizations with Marketo. You can also leave it blank to never fire.

Action: Sync Lead and Program Member Data from Splash into Marketo

This setting allows you to choose the frequency in which Splash information is synced with Marketo. Information can be synced hourly or in 15 or 30 minute intervals.

Action: Pull Lead and Program Member Data from Marketo into Splash

This setting activates the integration’s bi-directional capabilities. This means that any changes made in Marketo will also be reflected in Splash. For instance, adding a member to the Marketo program will a them as a guest in Splash as well, and vice versa. If you only want to send information one-way from Splash to Marketo, choose Never from the dropdown list.

Trigger Conditions

You can configure additional rules for when the integration fires with Trigger Conditions. These can be set up to limit this integration’s firing to only certain event types or groups.

Next, you'll need to select a Marketo Program template for Splash to copy.