Intro to Splash's Eloqua Integration
Splash's integration with Eloqua is configured on an organization-level; this means that every event in your Splash organization will be tied to your Eloqua instance.
Currently, the integration is one-way; this means any event activity occurring in Splash, such as an RSVP, ticket purchase, check-in, unsubscribe, etc., will be sent over to Eloqua.
When a guest's action is recorded in Splash, Eloqua will be prompted to create a new lead or contact, or to update information for existing ones.
How it works
After you connect Splash to your Eloqua account, you're able to configure:
- Triggers - The actions in Splash that will send event and attendee information to Eloqua
- Field Mapping - The fields in Eloqua you'd like Splash data to be sent to
The Splash triggers you are able to configure for associated with guest actions:
- Guest is invited (sent an email)
- Guest RSVPs or registers
- Guest purchases a ticket
- Guest checks in
- Guest unsubscribes from an email
Splash objects you can map to Eloqua fields are grouped into a few categories:
- Contact: Any information submitted via RSVP, registration, or ticket purchase, including responses to custom questions.
Examples: First name, last name, email address, company, phone number, dietary restrictions, etc.
- Event: Information entered by a Splash user associated with an organization's events.
Examples: Title, description, start date, end date, venue name, URL, city, state, event owner, etc.
- Ticket Order: Details of a ticket transaction, not including responses to ticket registration questions.
Examples: Order Number, total, amount refunded, purchaser name, etc.
- RSVP: The Splash tracking link registered on.
Note: This trigger only works if the guest registered via a tracking link.
- Custom: Custom can mean a lot of things, but the primary use of the Custom object is to send Eloqua attendee statuses.