We deliver new features and updates regularly to help you get the most out of your integration between Salesforce and Splash. Below is a list of enhancements organized by release date and what you need to know to update your Salesforce AppExchange Splash Admin app.

May 9, 2024

Version: 1.7.0

Bug fixes

• Disassociate lead company fields with account. Fixed an issue where the company field in Salesforce was always set to Unknown even though the Company field was correctly mapped and configured in their field mapping. Now, we will be disassociating the lead’s company from the account.

• Auto-create custom campaign member statuses if it does not exist in the campaign. This will resolve the issues where a campaign member gets created with invited status if the custom campaign member status provided via custom RSVP mapping does not exist in the campaign.

• Saving mappings. Fixed issue where during the event type mapping step, if the Lead / Contact / Account / Campaign tabs are not explicitly clicked, and the Save button is clicked, the default field mappings did not save.

April 11, 2024

Version: 1.6.2

Bug fixes

• Duplicate Guest Creation: This update addresses a scenario occurring in events with a maximum RSVP per email set to 1. Previously, if a guest existed in Splash without being connected to a Campaign Member in Salesforce, and a Campaign Member with the same email was subsequently added in Salesforce, it resulted in the creation of a duplicate guest in Splash. This issue has been rectified to prevent the creation of duplicate guests in Splash under the described circumstances.
• Lead and Contact Lookup Conditions: This update addresses a bug related to lead and contact lookup conditions, specifically:
  • Previously, when a guest was added in Splash with the same email as a lead or contact already associated with a different campaign, the lookup conditions logic skipped these existing leads/contacts and created new ones. This behavior caused problems for organizations with uniqueness constraints on leads, leading to failures in campaign member creation. This issue has been fixed to ensure that existing leads and contacts are properly utilized via lookup conditions, resolving the associated campaign member creation failures.

April 5, 2024

Version: 1.6.1

Guest Sync Debugger

We released a new feature designed to empower users to generate debug logs for guest sync processes.

How can debug logs be beneficial? In instances where you encounter issues during guest sync that prove difficult to resolve independently, you can activate the debugger and share the generated debug logs with Splash support. This will assist our technical team in efficiently triaging and resolving the issue at hand.

December 7, 2023

Version: 1.5.0

Searchable dropdowns

Search is in our drop-downs for Look Up Conditions and Event Type Field mappings, so you can quickly find the option you're looking for.  

Support for multiple Splash guests with the same email 

We have added support for multiple Splash guests to be added to an event with the same email address. Each guest will be associated with a unique campaign member. 

• • Note: These guests should not be updated as any update triggered to one contact will update all contacts with the same email address.

Additional Logging

New logs are now available to identify which guests failed, and the reason for the failure, when the “Sync from Salesforce” button is clicked. 

Bug fixes

• Fixed an issue regarding how Account Fallback applies to Contacts and Leads. Please check the updated set up guide to see additional steps to correctly set Account Fallback.
• Identified and resolved the root cause of an issue resulting in the following error during a Splash -> Salesforce guest sync: “intermittent duplicate error.” 
• Fixed a reported issue around “Never Update” and “Only when Empty” update methods not being respected for the Event Name field.

October 11, 2023

Version: 1.4.0

Enhanced logging options

The Splash Logs tab now includes more comprehensive logs for you to understand when data syncs between Splash and Salesforce are successful or have failed, with additional details to help you troubleshoot. Use the improved logs for Splash Guest <> Salesforce Campaign Member syncs, Splash Event <> Salesforce Campaigns sync, and with the Sync From Salesforce” button to manually trigger a data sync from Salesforce to Splash.

Improved scalability

Performance enhancements were implemented to ensure your events are able to scale without introducing errors or slow performance on the Splash-Salesforce integration. As a result of these enhancements, users should no longer experience “Too many queueable jobs error” or “Too many SQL queries: 201” errors.

Sync from Salesforce performance updates

Optimizations were made to the "Sync From Salesforce" process to eliminate unnecessary API calls between Splash and Salesforce, and introduce a new PUT endpoint within the Splash API to create and update guests more efficiently, which significantly reduces the sync time from Salesforce to Splash.

Bug fixes

• Failed guest syncs when First Name and Last Name field update methods were not selected as “Always Update” for Contacts and Leads.
• Disabling an event from the Salesforce integration on event-create would prevent a user from manually integrating the event with Salesforce at a later time.

July 24, 2023

Version: 1.3.0

Now available in EMEA

The Splash Salesforce Integration via AppExchange is now available for EMEA customers.

Configure lookup conditions for Leads and Contacts

You can now configure lookup conditions that determine how a Splash guest is matched to a Salesforce Contact or Lead.

In Global Settings, Admins have a new option, Lookup Conditions, that allows you to 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, a 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.

Configuring duplication rules for leads and contacts

In Global Settings, Admins have a new option, Duplicate Selection Policy, to define which objects to use for updates when duplicates are found during a lookup. You can select whether to update the first object created, the most recent object created, or the most recently updated object.

RSVP status mappings for leads and contacts

In Global Settings, there’s new Status Mapping mapping functionality that allows Admins to map Splash guest statuses to Salesforce campaign member statuses. Note, that 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.

Option to turn off Account Fallbacks for new contacts

Prior to this release, Admins could turn off the account fallback option for leads. In this release, Admins can also turn off this option for contacts. When this option is enabled, any lead or contact not associated with an existing account in Salesforce will default to a selected account.

For more information on how to set up the integration, see the Salesforce Integration via AppExchange Setup Guide. 

How to update the Splash Admin app in Salesforce AppExchange

To update the application:

1. Go to the Splash download page on the Salesforce AppExchange. Alternatively, navigate to the AppExchange and search for “Splash.”
2. View the app details under More Details for the package version and the latest release date.
3. Select whether to update the app directly into your production org or sandbox instance, and click the respective install button.

How do I know which version of that app I have installed?

In Salesforce, navigate to Setup > Apps > Packages > Installed Packages and click Splash Now to view the package details.

Triplelift follow-up

March 7, 2024

• Fixed an issue where events were disconnected after an update was made to an event in Splash. This caused the guest sync to fail as the campaign was no longer connected to the event. This happened when the Update if Empty option was selected in the event field mapping. Changing the option Update if Empty to Always Update Value in the event field mapping remediated the Splash event / campaign disconnect problem.

January 4, 2024

• Fixed an issue where an event created in Splash successfully created a campaign in Salesforce. However, any subsequent update in Splash event disconnects the event from the SalesForce campaign.

November 9, 2023

• Fixed the converted lead causing Too Many queuable jobs error preventing guests from syncing to Salesforce. The issue was resolved and the new package was released on November 16, 2023, with the fix.

February 1, 2023

• Added additional logs to improve the observability in case this happens again.
  Note: Post-release, we cloned an event in the organization, and noticed the event connecting successfully to the campaign.