Download the PDF Guide

The following User Guide will provide an end to end walk-through of how to configure an integration between Splash and Salesforce — detailing both the "why" and the "how to" with equal depth and breadth.

Before you dive into setup, you may want to check out the below rundown of available integration functionality or check out the demo video below.

This will allow you to approach the integration with the end in mind so that you strategize your setup around a variety of possible outcomes.  

Integration Functionality

Campaigns & Campaign Members

• When an event is created in Splash, it can automatically create a new Campaign in Salesforce. Salesforce Campaigns and Splash events have a 1:1 relationship. This means one Splash event connects to one Salesforce Campaign.
  
  • You also have the option to associate a pre-created Salesforce Campaign to any Splash event.
• All of your Splash event guests will automatically become Campaign Members; Splash Guest List statuses (Invited, Attending, etc.) will sync over to Salesforce as Campaign Member statuses.
• When a guest activity — such as an RSVP or Check-in — happens in Splash, the information will immediately sync back to the Salesforce Campaign.
  
  • Similarly, Campaign Members additions and Campaign Member status changes can be synced from Salesforce to the Splash event's Guest List.
    
    • This is what makes the integration "bi-directional." 
• You are also able to rename Splash Guest statuses (i.e. RSVP_Yes, Checked_In, Invited) to follow your desired Campaign Member statuses conventions in Salesforce.

Why is this important?

• The close relationship between the Salesforce Campaign and Splash event allows you to automate and standardize the creation of new Campaigns, and maintain a "single source of truth" between the two systems. 
  
  In other words, because the Campaign and the Splash event are always talking to each other, they will never be out of sync.
• The flexibility of the integration enables multiple processes:
  
  Event Managers working in Splash can rest assured co-workers who operate exclusively in Salesforce have full visibility into event activity via the Campaign.
  
  Because of the integration's bi-directional nature, invitees added to the Salesforce Campaign can be accessed — and emailed — from Splash by the Event Manager.

Leads & Contact

• The integration can be configured to create new Leads or Contacts in Salesforce when a guest registers or buys a ticket to a Splash event.
  
  
  • Contacts can be auto-associated to an existing Account based on the Company information entered during registration.
  • You can also associate contacts with a Fallback Account if the company information entered does not match one that exists in your Salesforce instance.
    
    Email Address is typically used as the way to uniquely identify a Lead or Contact between the systems.

• Lead and Contact information, such as Job Titles, Phone Numbers, etc, can also be updated when new information is submitted through the registration process.
  
  
  • Note: Splash will ONLY update existing Lead or Contact information if it's programmed to do so — this is not a default setting.

Why is this important?

• You're able to use all of the information submitted through registration, including answers to custom questions, to create new Leads/Contacts and update existing ones.
  
  Put simply: Any question that you ask in Splash can be tied back to any Lead/Contact fields you have in Salesforce.

Opportunities

• When a guest buys a ticket in Splash, the buyer becomes a Campaign Member and the transaction can become a new Opportunity.
• You're able to set a default Opportunity stage (i.e. Closed Won) upon ticket purchase.
• You're able to generate custom Opportunity names using a variety of mappable Splash fields relating to the buyer, the event, or the ticket transaction.

We'll explore each of these topics in more depth throughout the guide. But now that you know what the integration is capable of, you can begin the setup process.

Next Article: Chapter 1: Integration Requirements