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.
The first action handles cloning Marketo programs to match new Splash events. You can turn this action on to fire with every new event or leave it turned off.
The second action, on the other hand, 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.
Note: You can also leave it blank to never fire.
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.
Note: This can be used automatically link together program templates with event types, creating different automation rulesets for different kinds of events.