Overview
Gem offers an integration with Splash, the event marketing platform, to allow you to easily and automatically upload potential candidates into Gem. This enables your events to effortlessly become true top-of-funnel recruiting sources that you can nurture into candidates with Gem sequences.
Requirements
- This integration requires your organization to have Splash for Business.
Benefits of syncing Splash with Gem
- Sequence users that RSVP yes to your events.
- Sequence users that attend your events.
- Measure the ROI of your events by tracking candidates that came to your events throughout the entire recruiting funnel.
- Auto-upload other custom information about candidates to Gem, such as resume, which departments they are interested in, how they heard about the event, etc.
How does it work?
You must connect your Gem account to your Splash account so we can create two Gem projects that are linked to your Splash event:
- One project for RSVPs;
- One project for people who attended your event (checked-in).
The two projects will be automatically created after the first person RSVPs Yes and after the first person checks in to your event.
- The first Gem project will contain the people that RSVP’d Yes for your event. Those guests will be sent to an automatically-generated Gem project, which will be named: Event: {Event Name} - RSVPs.
- At the event, use Splash’s check-in feature to automatically send check-ins to another automatically generated project, which will be named: Event: [Event Name] - Checkins.
- From here, you will be able to sequence your candidates as you see fit. You will also be able to track the source (Splash) of this candidate if they move into process with your company.
- In the Splash registration form, you can include whatever questions you’d like besides just name and email. For example, many customers like to ask for the LinkedIn profile URL, resume drop, what departments they’re interested in, how they heard about the event, etc.
What if I have a team of people hosting recruiting events?
We only need to set up the integration once across your company. When someone on your team creates an event in Splash and they also have a Gem account, the project is created in their individual Gem account. If an event is created by someone who doesn’t have a Gem account / we don’t find a matching Gem user for the Splash user, the projects will be owned by the default project owner (you decide who that default project owner is).
One thing to note: by default, the projects will be private projects, so if you create a Splash event and want that event’s project to be accessed by your team in Gem, you need to change the settings of that project to a shared project. To change the settings, click on the “Share” button in the top right corner:
What if I host a multitude of events, not just recruiting events?
If you use Splash to create events that are outside of recruiting, we give you the ability to limit the integration to send event activity of only selected types of events, such as Recruiting events only.
How do I set up the integration?
- Ask your Gem point of contact for your team ID & the secret key to enter in your Splash account (this is unique to your company). You will use this information in Step 7. Once you have these two pieces of information, proceed to step 2.
- Head to your Splash account to set up the integration. Go to https://app.splashthat.com/integrations and click the “New Integration” button.
- Select the “Simple Postback” type of integration:
5. In the first section of fields, set the following values:
- Type/Method →
POST - Postback URL →
https://webhooks.gem.com/splash/splashWebhookHandler - Content-Type →
application/json
6. After you’re done, that first section should look like this:
7. Headers: The next section of fields will ask for the following values, which you can add by clicking the “Add a key-value pair” button:
- team_id → {get your team ID from Gem}
- secret_key → {get secret key from Gem}
- default_owner_email → enter your email address (all lowercase), or that of another Gem user on your team. The integration will add your Splash event invitees and guests to Gem Projects that will be automatically created under this user.
- Integration Settings
- Donot check:
Ignore empty Values - Integration Name:
Gem Integration - Trigger:
Attendee - Action: Check
RSVP Yes&Check-Indon’t select other values here - they aren’t supported yet
- Trigger Conditions
If you want to limit the Gem integration to run only on certain Splash event types, you can go to your set the following:
- Only Trigger for specific event types:
Yes(checked) - Event Type:
Recruiting Event(or whatever event type you want to limit the integration to)
- Field Mappings
There are a set of default fields you’ll need to map to make the integration work, and then additional fields that you’ll map based on what information you’re collecting from guests in your registration form.
Here’s how to map the default fields:
Click the
button to add the following information:
- Splash Object:
Event - Splash Field:
Event ID - Remote Field:
event_id - Splash Object:
EventSplash - Field:
Title - Remote Field:
event_title - Splash Object:
Event - Splash Field:
Event Owner Email - Remote Field:
event_owner_email - Splash Object:
Event - Splash Field:
Event URL - Remote Field:
event_url - Splash Object:
Contact - Splash Field:
Email - Remote Field:
contact_email - Splash Object:
Contact - Splash Field:
First Name - Remote Field:
contact_first_name - Splash Object:
Contact - Splash Field:
Last Name - Remote Field:
contact_last_name - Splash Object:
Trigger - Splash Field:
Action - Remote Field:
trigger_action - Splash Object:
Trigger - Splash Field:
Timestamp - Remote Field:
trigger_ts - Splash Object:
Contact - Splash Field:
field for current company name - Remote Field:
contact_current_company
To make sure that fields on your registration form get sent back to the Gem project too, you’ll need to map them accordingly. You should first create your registration form and then come back here to add the mappings, as outlined below.
Keep in mind that we only support the following field types in Gem, so if you have other field types in your Splash registration form, you may not have a way to map them back to Gem.
Field types we currently support:
- Multi-select list
- Single-select list
- Date
- Text
To map these registration form fields, you’ll need to map them as follows:
- Splash Object:
Contact - Splash Field:
\{select the field you added to your registration form\}
where Field Name is the name of the field as you want it to appear in Gem (i.e. as a column header in your Gem project). This field is case sensitive and will appear in Gem as entered in the integration setup.
Finally, if you plan on asking for guests to provide their LinkedIn URLs on your registration form, you’ll need one final mapping. Splash unfortunately doesn’t have an out-of-the-box LinkedIn field available, so you’ll first need to create a text custom field on the Contact object called “LinkedIn,” add that custom field to your registration form, and then map it to:
contact_linkedin
This will map back to the primary LinkedIn URL on the prospect profile in Gem, and not as a project custom field.
Gem validates the LinkedIn URL before setting it to the LinkedIn field in Gem. If the candidate enters an invalid LinkedIn URL, we will capture it in a project custom field called Invalid LinkedIn. It will show up in the Gem project as shown below.
Have any issues or questions on this topic? Please feel free to contact your dedicated Gem Customer Success Manager directly or our Support team at support@gem.com.