After setting up your integration with Accelevents and Oracle Eloqua, the attendee contact records will be added to Shared Lists in Oracle Eloqua. Two shared lists will be generated after the first event registration. Registrations can also appear as Form Submission Data if you've associated an Oracle Eloqua form in the integration settings.

In this article, you'll learn about the default rules for contact creation and updating, where to find the attendees in Oracle Eloqua.

If you still need to integrate, follow the steps in this article to set up the Integration to Export Event Data from Accelevents Into Oracle Eloqua.

When a new registration comes in, Accelevents checks Oracle Eloqua if there is a contact record that has matching email address as the attendee. If a match is found, the existing contact record is updated. If no match is found, a new contact record will be added.

When updates are made to the ticket holder information in the order in Accelevents, the information also updates in Oracle Eloqua. It will not update the Form Submission Data if this is generated during registration.

When updates are made in the Oracle Eloqua contact record, it does not update in Accelevents.

After connecting your integration, do a test registration to trigger the creation of the 2 shared lists in Oracle Eloqua. The lists will not automatically generate after connecting the integration, it's the first registration after connecting the integration that will trigger the creation.

When the order is created in Accelevents for the first time after the integration setup, two shared lists are automatically created in Oracle Eloqua.

The lists will be named after your event URL: "eventURL-Registered" and "eventURL-Registered-Not-Attended."

For example, if my event URL is https://www.accelevents.com/e/demovirtualevent, my two lists will be automatically named "demovirtualevent-Registered" and "demovirtualevent-Registered-Not-Attended."

After the event lists are created, new ticket holders will be automatically added to both lists. Once the attendees check in to the event, they will be automatically removed from the "Registered-Not-Attended" list while remaining in the "Registered" list.

Click one of the shared lists to see all the attendee contacts. Everyone who registered for the event should show here.

Aside from the name and email address, the other registration data should appear in the contact record if you mapped them.

Some of the contact fields will be display here depending on your contact views. In the example below, we have the Standard View where the Title and Company are displayed.

If the other fields are not showing in this view, use the "All Contact Fields" view, where we can see the Mobile Phone field.

You can also go to the Contacts menu, search for the attendee record using the email address and double click the record to open it. Click View More to see the other fields, then select the All Contact Fields view and search for the fields.

If you mapped Check In Status to a contact field, you'll see the contact field update depending on the attendee's check in status, whether they are only registered for the event, if they've checked in, or if their ticket was refunded or deleted.

If in the integration settings you associated an Oracle Eloqua form and mapped the form fields, Form Submission Data will populate after registering for the event.

If you mapped Check In Status to a form field, the Form Submission Data will not update if the attendee has checked in or the ticket was cancelled as it cannot be overridden, instead a new Form Submission Data item will be generated with the updated Check In Status.