Skip to main content
Splash connects with a Client ID and Client Secret issued to your organization by Splash, together with a Splash login that Conversion uses once to establish access. Once connected, everything in Field Event Platform Sync applies; this page covers getting the credentials, the connection, and where Splash behaves differently.

​
Get your Splash API credentials

Splash doesn’t let you generate API credentials yourself. They come from Splash on request.
  1. Contact your Splash Customer Success Manager and ask for API access. Say what it’s for: syncing event details, RSVPs, and check-ins to Conversion.
  2. Splash generates a Client ID and Client Secret for your organization and delivers them through a secure channel. Store them somewhere safe; the secret is not shown again.
  3. Decide which Splash user Conversion will connect as. Conversion sees only the events that user can see, so pick a user with access to every event you want to sync. A dedicated integration user works well.
If your organization already uses the Splash API for another tool, you can reuse the same Client ID and Client Secret. See Rate limits for what sharing them means.

​
Connect Splash

Prerequisites: You are a workspace Administrator, you have the Client ID and Client Secret, and you know the email address and password of the Splash user Conversion will connect as.
  1. Open workspace Settings and go to the Integrations tab.
  2. Find Splash and click Connect.
  3. Enter the Client ID and Client Secret.
  4. Enter the Splash user’s email address and password.
  5. Click Connect.
Conversion signs in to Splash once with those details and keeps the resulting access current on its own. The password is used for that one sign-in and is not stored. The Client ID and Client Secret are stored so the access can be renewed. Once connected, the card shows the Splash user and how many events Conversion can see. Use Update connection to connect as a different user or with new credentials, and Disconnect to remove the integration. Connected field events keep their members but stop syncing.
If Splash’s renewal ever fails, for example because the credentials were revoked or the user’s password changed and Splash ended its sessions, the card stops showing Connected and you reconnect with the current password. Nothing is lost in between; syncing resumes once reconnected.

​
Choosing an event

Events are listed newest start first. Search by title, or narrow by start date, to find older ones. Only events visible to the connected Splash user appear.

​
Registration and attendance

Splash has no notifications for guests, so Conversion reads changes on an hourly sync. An RSVP made on Splash appears in Conversion within the hour. Guests without an email address on Splash are skipped, because there’s nothing to match them to a contact with.

​
Event details

Splash fills in the title, times, registration link, whether RSVPs are open and waitlisting is enabled, capacity, RSVP count, venue and address, and the event owner as organizer. The format is set to in-person when the event has a venue and left blank otherwise. Splash doesn’t expose an event’s time zone through its API, so Time Zone stays empty on a Splash-connected event. Start and end times are still exact moments; only the zone label is missing.

​
Rate limits

Splash allows two API requests per second per Client ID, shared across everything using those credentials. Conversion paces itself to stay under that, so a large event’s guest list takes a few minutes to sync rather than a few seconds. If another tool uses the same Client ID heavily, Splash may throttle both; the sync retries and catches up on its next run.

​
Troubleshooting