The Splash Admin app in Salesforce AppExchange makes it easy to configure the integration between Splash and Salesforce to ensure that your event data in Splash is up-to-date with your campaign data in Salesforce. The integration provides a single version of the truth to your sales and marketing organizations about event and guest data so that you don’t have to bounce between systems.

In this guide, you'll learn how to:

• Install and authenticate the app to connect Splash and Salesforce.
• Configure global settings to define how actions in Splash trigger updates to Salesforce contacts, leads, and campaign members.
• Configure event type settings to map data fields between Splash and Salesforce.

	This feature is available to Basic, Pro, and Enterprise plans
	Roles available: Admin, Admin (Basic), and Integrations Specialist
	This feature is in Beta

On this page:

There are many reasons to integrate Splash with Salesforce. Fundamentally, integrating the two systems allows sales and marketing to perform their day-to-day functions in their tools of choice while accessing the same information. For example:

• An event marketer working in Splash and a sales colleague working exclusively in Salesforce have complete visibility into event and guest activity.
• Due to the integration's bidirectional nature, the event marketer can access, and email guests added to the Salesforce campaign from Splash.

How does data sync between Splash and Salesforce?

Before configuring the integration settings, it’s essential to understand your business requirements and the data relationship between Splash and Salesforce.

Integration and configuration settings

• The integration is configured in Salesforce in the AppExchange app, and changes to the integration settings send updated configuration settings to Splash.

Events and campaigns

• Splash events and Salesforce campaigns have a 1:1 relationship, which means one Splash event connects to one Salesforce campaign.
• When an event is created in Splash, it automatically creates a corresponding campaign in Salesforce, given that there's a setup for the Splash event type mapping and it's activated, unless the choice has been made to exclude that specific event from integrating with Salesforce.

Guests, leads, contacts, and campaign members

• Splash event guests sync to the connected Salesforce campaign.
  • Existing leads and contacts are added as campaign members.
  • Unmatched guests are added to Salesforce as new leads or contacts – as defined in Global Settings – and added as campaign members.
  • If a new guest in Splash has a status that does not match a selected action trigger, the campaign member is created in the Salesforce campaign with only the required fields – First Name, Last Name, Email, and Company (Company is for lead only).
  • If a new guest in Splash has a status that matches a selected action trigger, the campaign member is created in the Salesforce campaign with all available data mappings.
• Campaign members created in Salesforce sync to the corresponding Splash event.
  • Existing leads and contacts are added as event guests.
  • Unmatched guests are added to Splash as new guests.
  • If a new campaign member in Salesforce has a status that does not match a selected action trigger, the guest is created in the Splash event with only the required fields – First Name, Last Name, Email, and Company (Company is for lead only).
  • If a new campaign member in Salesforce has a status that matches a selected action trigger, the guest is created in the Splash event with all available data mappings.

Data fields

• Guest status triggers updates to data fields. For example, if “attending” is a selected action trigger, when a status changes to attending, and first name, last name, email, and job title are all mapped to update, the integration will trigger those fields to sync and be updated. If attending isn’t an action trigger, only the status is updated.
• Guest status will sync, regardless of whether that status is a selected action trigger.

Install and authenticate the app

Now that we’ve explored the functionality of the Splash Salesforce integration and how data syncs between the platforms, let’s install and authenticate the application.

Install the app

1. From the Splash dashboard, navigate to the Integrations tab. Or, you can go to https://app.splashthat.com/integrations in your browser.
2. Select the New Integration button and then select the Salesforce via AppExchange card from the integration options to launch the Salesforce AppExchange.
3. If prompted, enter your Salesforce credentials and click Log In.
   
   Alternatively, go to the Splash download page on the Salesforce AppExchange, or navigate to the AppExchange Marketplace and search for “Splash.” Then, follow the AppExchange download and installation instructions.
   

   Note: Ensure you select Install for Admins Only from the installation options.

   
   

   Note: The Salesforce integration via AppExchange is included in your paid Splash plan. There is no additional charge to download and use the app. You might see a fee listed to download the app. You can ignore this.

4. After installing the app package, navigate to Setup > App Manager in Salesforce, and scroll to find Splash Integration. From the dropdown, click Manage.
   
5. On the Splash Integration Connected App Detail page, click Edit Policies and navigate to the OAuth Policies section. Next, click Permitted Users and select Admin approved users are pre-authorized. Then click Save.
   
6. On the Splash Integration Connected App Detail page, navigate to the Profiles section and click Manage Profiles. Select the checkbox for System Administrator, and then click Save.
7. Navigate to Users > Users. Then, click on your user’s name and Edit Assignments in the Permission Set Assignments section. Add Splash Admin to Enabled Permission Sets, and then click Save.
8. With the Splash Admin app installed, click the App Switcher and search for Splash.
   
9. Click Splash Admin to launch the app.

Authenticate the app

Everything you need to configure Splash and Salesforce to work together is in the integration app. Follow these steps to authenticate the connection:

1. Click the Authentication tab.
2. Click the Edit button, and then enter your Splash account username and password and select your region.
   
   

   Note: If you switch data regions between AMER and EMEA, you must redo your event type settings and field mappings. The event type setting ID that connects your Splash event to your Salesforce campaign is specific to the data region the event was set in.

3. Under Splash Connection Status, click Authenticate.
4. If required, click the Reauthenticate button to re-establish the connection.

With the integration authenticated and an understanding of how data flows between Splash and Salesforce, we’ll use the two main pages in the integration, Global Settings and Event Type Settings, to configure the data syncing for your business requirements.

Configure Global Settings

On the Global Settings page, you can:

• Configure the lookup conditions that determine how a Splash guest is matched to a Salesforce contact or lead, and choose how to handle duplicate objects.
• Map the Splash action triggers that determine when data fields are synced between Splash and Salesforce. Don’t worry about the data field mapping for now. You’ll configure that later on the Event Type Settings page.
• Map Splash guest statuses to corresponding Salesforce campaign member statuses.
  
  

1. Click the Global Settings tab.
   
2. In Lookup Conditions, select the fields you want to use to look up a Salesforce object when a contact is added to Splash. By default, objects are looked up by email, but you can add additional fields. Note that if you add more than one field, all conditions have to be met to have to match. For example:
   • Splash guest Jane Doe with an email address of jane.doe@testing.com would NOT match a Salesforce contact Jane Smith-Doe with an email address of jane.doe@testing.com if you configure the lookup conditions to be email, first name, and last name because all conditions are not met. While first name and email match, last name does not.
3. Next, under Duplicate Selection Policy, choose what object to use when duplicates are found during a lookup.
4. Under New Contact Type, select if a new Splash guest will create a lead or a contact in Salesforce. The integration will check whether a Splash contact matches a lead or contact in your Salesforce instance. If there’s no match, one will be created in Salesforce.
5. In the Splash Action Trigger section, select which actions will trigger data mapping updates to leads, contacts, and campaign members in Salesforce.
   
   The available action triggers are:
   • Added
   • Checkin
   • Checkout
   • Invited
   • RSVP No
   • RSVP Yes
   • Unsubscribe (from Organization)
   • Waitlist
     

     Note: Action triggers will only apply for active event types, and currently only apply for Splash to Salesforce. For syncs from Salesforce to Splash, data is always updated regardless of whether or not a contact’s status updated to an action trigger or not.

6. Under Account Fallback, enable whether any lead or contact not associated with an existing account in Salesforce can default to a selected account. This can be useful for quickly identifying your Salesforce contacts without an existing account. To assign an account fallback, one must first exist as an Account in Salesforce.
   

   Note: Company is a required field for leads in Salesforce. Therefore, if you don’t assign an account fallback and the Company field is empty for a guest in Splash, the Company field in Salesforce will default to “Unknown” for that lead.

   
   

   Note: If you are using the Lead object and want to enable Account Fallback, ensure you have the field “Company” (Splash field) mapped to “Company” (Salesforce field) in the Lead tab of your Field Mappings. If you are using the Contact object and want to enable Account Fallback, ensure you have “Company” (Splash field) mapped to “Account Name” (Salesforce field) in the Account tab of your Field Mappings.

7. In the Status Mapping section, map Splash guest statuses to Salesforce campaign member statuses. While you can map multiple Splash RSVP statuses to one Salesforce status, Splash will use the order they appear in the list when synching data from Salesforce to Splash.
   
   In order for the custom statuses to be correctly synced, you must configure them within your campaigns in Salesforce. You do not need to follow the next steps if you are only using the Splash default mapped statuses. 
   
   
   
   Steps to configure custom statuses in Salesforce 
   
   1. Go to the Sales section in Salesforce, click Campaigns and select the campaign you want the new statuses to apply for. 
   2. Scroll down to Campaign Member Statuses and click New
   
   3. Add the custom statuses you want to be reflected in the campaign. Note: these must match the custom status values in the RSVP Mapping section within the Global Settings tab of the Splash App. 
   
   
   The custom status has now been added to your campaign. Now, you must add these statuses to all the campaigns you want the custom statuses to be reflected on. If the custom statuses are not added to a campaign, then the campaign member statuses will reflect the default checked status. 
   
   

   Note: The responded checkbox in status mapping will only be applied to new campaigns, and will not retroactively update campaign member statuses on existing campaigns.  The responded checkbox in status mapping will only be applied to the default campaign statuses, and will not update the custom campaign member statuses added to the campaign.

8. Under Event Level Integration, select Allow user to disable integration for specific events, if you want to allow users to turn off the Salesforce integration for Splash events in the event level integration settings
   1. When this checkbox is selected, any user in your Splash instance will have the option to exclude a newly created event from the Salesforce integration. This means a Salesforce campaign will not automatically be created for the associated event to sync to. 
      
      

Splash Action Triggers

Mapped data fields sync bidirectionally, but ONLY if a status update triggers the sync, as defined in global settings. This configuration provides flexibility to control when data syncs between Splash and Salesforce. Status updates will always sync, regardless of whether those are selected action triggers. The selected action triggers indicate when data fields sync. Changes to mapped data fields will only sync when a guest status updates to one of the selected action triggers.

In other words:

• Action triggers define when data syncs.
• Field mapping defines what data updates – and how.

Understanding the relationship between action triggers and field mapping ensures your integration respects your organization’s business rules.

Configure Event Type Settings

You configured the Splash action triggers in Global Settings that determine when data fields sync. In Event Type Settings, you’ll map the data fields between Splash and Salesforce that get updated when those action triggers occur and manage which event types are active and inactive.

Configure a new Event Mapping

1. Click the Event Type Settings tab.
2. Click the Add New Event Mapping button.
   
3. Select the event type you want to map from the Splash Event Type dropdown list, then click Create. The list includes event types available to your Splash organization, including custom event types.
   
4. In Field Mapping & Settings, map Splash fields to your Salesforce fields for Campaign, Lead, Contact, Account, and Campaign Member objects by selecting fields from the Splash Field and Salesforce Field dropdown lists. Then, click the Map New Field button to map additional fields.
   
   Take note of the following when mapping fields:
   
   • Splash fields available to your organization are selectable in the Splash Field dropdown list.
   • Salesforce fields available per object (Campaign, Lead, Contact, Account, Campaign Member) are selectable in the Salesforce Field dropdown list.
   • Splash and Salesforce fields can be mapped only once per Salesforce object.
   • The Splash and Salesforce fields in each mapping row must be the same data type. If the data types don't match, you'll see an error message and won't be able to save the field mappings until you select a valid field.
   • Ensure you don’t change the fields that are pre-mapped. Those are required for successful syncing.
   • Event Type (Splash field) must be mapped to Splash Event Type (Salesforce field).
   • To map Campaign Member statuses, please use the RSVP value mapping section – you should not configure these in the Field Mappings and Settings.
     
     
     

     Note: Event ID in Splash is mapped automatically to Splash Event ID in Salesforce upon campaign creation. If you don't see Splash Event ID in your Salesforce campaign details after the integration is complete and active, you can add it using Object Manager > Campaign > Page Layouts in Salesforce.

     
     

     Note: When an event is connected to a campaign for the first time, the campaign name will always be updated to match the event name (regardless of the update method selected). If you want the event name and campaign name to have distinct naming conventions, make sure you connect the event to the campaign first, and then update the campaign name. You would also need to have “Event Name” in your field mappings set to ‘Only Update if Empty’ or ‘Never Update’.

     
     

     Note: For Custom Event Create Flow questions, they will be prefixed with “Event -”.

5. In Field Mapping & Settings, for each field mapping, select an Update Method to specify how fields get updated between Splash and Salesforce.
   • Never Update Value: Changes to the Splash field will never update the Salesforce field value.
   • Update Existing Value: Changes to the Splash field will always update the Salesforce field value.
   • Only Update When Empty: Changes to the Splash field will only update if the current Salesforce field value is empty or Null. If there's a value in Salesforce, it will never be updated.
     

     

     If changes are made in both Splash and Salesforce, the most recent change persists.

6. When you've finished mapping fields, ensure you've met the following conditions, and then click Save.

   • The required Salesforce fields have been mapped for Lead and Contact
     • First Name, Last Name, Email, and Company (For Lead only). By default, these fields are mapped for you.
   • There are no duplicate mappings. Only 1:1 mappings are supported for Splash fields to Salesforce fields.
   • Update Method has been selected for all fields.
7. By default, new event types are inactive, which means any field mappings will not be synced. Only active event types will trigger data syncing between Splash and Salesforce. In the Event Type Settings section, you can update the following settings by clicking the down arrow next to the event types:
   • Activate: Enables data syncing between Splash and Salesforce for that event type.
   • Deactivate: Disables data syncing between Splash and Salesforce for that event type. This is only available for activated event types.
   • Edit: Allows you to edit data mappings and update methods for that event type.
   • Clone: Clones an existing event type mapping and creates a new one with identical field mappings. The cloned event type mapping must be a different event type. For example, if you clone a Conference event type, you can’t create a new Conference event type with the same field mappings, but you can create a Happy Hour event type with the same field mappings.
   • Delete: Deletes an event type mapping. This is a permanent action that can’t be undone. This will also disable the integration for all Splash events of that event type that you previously connected to Salesforce.
     
     

     Note: Only active event types will trigger data syncing between Splash and Salesforce. If you deactivate an event type, all events of that event type will stop syncing data.

Confirm the Integration is connected

With the integration setup complete and at least one event type configured and activated, your integration will be live in Splash.

To confirm the integration is live:

1. From the Splash dashboard, navigate to the Integrations tab. Alternatively, go to https://app.splashthat.com/integrations in your browser.
2. Under Integrations, you should see the new Salesforce via AppExchange integration listed with a green dot indicating the connection.
   
   

Splash Logs

To view the integration logs on Salesforce, click the “Splash Logs” tab next to “Admin App” once you’ve opened the application:

Once you are in the Splash Logs tab, you will be able to see logs for the following scenarios (and click to expand the logs to see a more detailed stack trace):

Splash to Salesforce:

• Successful campaign creation (this will be logged on initial Campaign creation from an Event, as well as when an existing Campaign has been manually connected to a Splash event)
• Failed campaign creation and reason for failure
• Successful campaign updates or failed campaign updates (and reason for failure)
• Campaign Member creation success or failure (and reason for failure)
• Campaign Member update success or failure (and reason for failure)

Salesforce to Splash:

• Request sent to Splash to create guests (and failure in the request sent as well as campaign member ID’s of those who failed)
• Request sent to Splash to update guests (and failure in the request sent as well as campaign member ID’s of those who failed)
• Request for Manual “Sync from Salesforce” triggered for Campaign ID X (This will be logged when someone clicks the “Sync from Salesforce” button on Splash)

Sync from Salesforce Option

A data sync can be manually forced by clicking the "Sync From Salesforce" button in your Splash guest list. This will pull all guest updates from the connected Salesforce campaign into the Splash event without waiting for a configured action trigger to occur.