App Installation and Setup

No matter which registration form you are using, start by installing and setting up the app.

Download the app here, then provision a token in the ON24 platform and name it Eloqua App.

Add App to Campaign

In your campaign add the Registrant Data Query Service - API version to the canvas.

Wait for the app image to turn green and double-click on the instance. 

Click on the edit button to configure the app. If there is a problem creating a new instance of the app, the icon will turn red.

Configure Event Details

The Event Details configuration page will prompt you to add the following:

1. Client ID
2. Token Key
3. Token Secret
4. Event ID (if left empty the app will pull data from all events from account)
5. Batch Job Interval

Click Verify and Continue.

Configure Contact Field Mapping

On the Field Mapping for Contacts, select the ON24 Fields from the left column to map to the Eloqua Contact fields in the right column. The ON24 “Email” will automatically map to the Eloqua contact field “Email Address”.

If you want to configure the feeder to map data into a custom object, move on to the next section. 

If you’re using ON24 Registration and would like that registration data passed over to your contact record(s) within Eloqua, the information below will help provide additional context. Within the below screenshots, you will be able to select and map the On24 fields to your Eloqua/Oracle fields that live within the contact object. 

In order to locate these fields, they can be found within the settings of your Eloqua instance (Settings > Manage Fields & View > Contact Fields). Please note that you will only want to pass the registration data to your contact. Please do not map the attendee data. 
 
To view the configuration aspects of the On24 Eloqua Registrant Data Query Service App, please click on the edit button at the bottom right to configure the app. 

Below is the section you will want to update.  The Registrant Field Mapping can include any or all of the fields listed with a yes in the Contact column of this spreadsheet.  Eloqua requires email, which will mapped by default. 

Click on the Configure button and a green checkmark will appear. At this point, you can close the Cloud Feeder Configuration window.  

Registrant and Attendee Data to Custom Objects Field Mapping

The custom object requires the 2 fields below:

1. Email Address: The app will automatically pull in the ON24 Attendee’s email address. In the Custom Object details section assign “Email Address” to the Email Address Field.

2. Event User Id: The app will automatically pull in the ON24 Attendee’s unique identifier in the ON24 platform which is called the Event User Id. In the Custom Object details section assign “Event User Id” to the Unique Code Field.

Note: If you don’t see the custom object in the drop-down list of available custom objects, then the above field mapping was not configured correctly.

The custom object can include any of the fields related to attendee information.  Find a list of all the fields in the Standard Integration API Fields tab of this spreadsheet, using the Custom Objects column.

• Advanced Analytics Users - If you have an Advanced Analytics package in your contract, you can map up to five custom event fields.  Find a list of these fields in the Addtl Advanced Analytics API tab of the spreadsheet. 

After the API fields have been added to the Custom Object, please access the Cloud Feeder Configuration.  Here you will map Registrant data that you would like to sync from ON24 to Eloqua, scrolling down, please select your Custom Object Name to see your newly added API fields, and map your ON24 Attendee Data.

Select the custom object from the drop-down list. The ON24 Registrant and Attendee data is available in the drop-down options in the left-hand column, and the custom object fields are listed in the right-hand column.

Note: Eloqua Custom Objects have a limit of 100 fields in order to pass data over. If this limit is exceeded there is no error message, the data will not pass over.

Click on the Configure button and a green checkmark will appear. At this point, you can close the Cloud Feeder Configuration window.

Add App to Program

Depending on what you want to accomplish, you'll either select Contact Program or Custom Object Program. 

For ON24-related use cases, Contact data = registrant-related information, whereas Custom Object = attendee-related information:

After you select the Program type, select the template from where the canvas will be starting from. In this scenario, it will be a blank template, whether it's for Contact or Custom Object Programs:

Setup Using Eloqua/Third Party

Use the instructions in this tab if you are using Eloqua or a third party's registration form for your events.

Click on the accordion of the ON24 product you're looking to set up, to find the form processing steps.

Note: No matter which product you are using, toggle Login Only ON via the registration page of your ON24 webinar to disable the ON24 registration form, allowing your viewers to use only the Eloqua form.

Webinars

Set up Eloqua Form Fields for Webinar

Create a Form in Eloqua with registration fields.  

Include the below hidden fields as static values, or leave them empty and have your landing pages assign values for these.

• eventid
• key
• You can include hidden fields for multiple eventid and key pairs - name them eventid1, key1, eventid2, key2, etc.  Add checkboxes to allow users to register for multiple events.

The values for eventid and key can be set either as static values which require setting up a new form for each webinar, or you can pass these values over from hidden fields on an Eloqua landing or post from an external form. 

The eventid and key are unique per Webinar and can be pulled from the audience URL.

https://event.on24.com/wcc/r/eventid/key

 

Add Post Data to Server Form Processing Step for Webinar

Go to the Form Processing Steps and add Post Data to Server for each webinar..

For General Settings, select Constant Value and add the URL. 

• For NA, use https://seamlessreg.on24.com/eloqua 
• For EU, use https://seamlessreg.eu.on24.com

In each Post Data to Server,  change the Target Fields so that only one pair of values is passed over for eventid and key. These are case-sensitive.

For custom mapping, edit the Target Fields using the ON24 Target Field values below.

Each post data to server step is conditionally triggered off of the checkbox for the events.

Note: Fields are case sensitive (e.g. 'eventid' and 'key'). Use the exact 'ON24 Target Field' names.

If you are using the older URL (https://event.on24.com/custom/client/eloqua/postreg.jsp) see the v.1 Data Fields accordion to view the fields that can be used when using this URL. It is highly recommended to change the URL you are using to the new one above as this gives you more options for fields to be passed over.

Eloqua Standard Source Fields	ON24 Target Fields	Required (Y/N)
-	eventid	Y
-	key	Y
Email	email	Y
First Name	firstname	N
Last Name	lastname	N
Company	company	N
-	jobfunction	N
Title	jobtitle	N
Street Address 1	address1	N
Street Address 2	address2	N
City	city	N
State	state	N
Postal Code	zip	N
Country	country	N
Work Phone	workphone	N
-	companyindustry	N
-	companysize	N
-	eventemail	N
-	marketingemail	N
-	partnerref	N
-	custom1	N
-	custom2	N
-	custom3	N
-	custom4	N
-	custom5	N
-	custom6	N
-	custom7	N
-	custom8	N
-	custom9	N
-	custom10	N
-	exteventusercd	N
-	utmcampaign	N
-	utmcontent	N
-	utmmedium	N
-	utmsource	N
-	utmterm	N
-	fax	N

Engagement Hub

Setup Eloqua Form Fields 

Create a Form in Eloqua with registration fields

Include the below Hidden Fields as static values, or leave empty and have your landing pages assign values for these.

• eventId
• key
• updateIfExist (always "Y")

The eventId and key are unique per EHub and can be pulled from Engagement Hub > Reg > Seamless Registration URL.

 

Add Post Data to Server Form Processing Step 

Go to the Form Processing Steps and add Post Data to Server.

For General Settings, select Constant Value and add the URL. For NA, use https://seamlessreg.on24.com/eloqua & for EU, use https://seamlessreg.eu.on24.com.

Update the Target Fields names to match our attribute names so that our endpoint can recognize the data POST and add the data to the appropriate ON24 registration fields. See https://apidoc.on24.com/unified-seamless-reg for the full set of attribute names. These are case-sensitive. See below for the required fields.

• eventId
• key
• updateIfExist
• email

Note: Fields are case sensitive (e.g. 'eventid' and 'key'). Use the exact 'ON24 Target Field' names.

Eloqua Standard Source Fields	ON24 Target Fields	Required (Y/N)
-	eventid	Y
-	key	Y
Email	updateIfExist email	Y Y
First Name	firstname	N
Last Name	lastname	N
Company	company	N
Title	job_title	N
Street Address 1	address_street1	N
Street Address 2	address_street2	N
City	city	N
State	state	N
Postal Code	zip	N
Country	country	N
Work Phone	work_phone	N
-	job_function	N
-	company_function	N
-	company_size	N
-	partnerref	N
-	std1	N
-	std2	N
-	std3	N
-	std4	N
-	std5	N
-	std6	N
-	std7	N
-	std8	N
-	std9	N
-	std10	N

Target

Setup Eloqua Form Fields 

Create a Form in Eloqua with registration fields.

Include the below Hidden Fields as static values, or leave empty and have your landing pages assign values for these.

• eventId
• key
• updateIfExist (always "Y")
• experienceId

The eventId, key and experienceId can be pulled from the Seamless Registration URL under Target > Attributes > Seamless Registration URL.

 

Add Post Data to Server Form Processing 

Go to the Form Processing Steps and add Post Data to Server.

For General Settings, select Constant Value and add the URL. For NA, use https://seamlessreg.on24.com/eloqua & for EU, use https://seamlessreg.eu.on24.com

Update the Target Fields names to match our attribute names so that our endpoint can recognize the data POST and add the data to the appropriate ON24 registration fields. 

See https://apidoc.on24.com/unified-seamless-reg for the full set of attribute names. These are case-sensitive.

See below for the required fields.

• eventId
• key
• updateIfExist
• email
• experienceId

Note: Fields are case sensitive (e.g. 'eventid' and 'key'). Use the exact 'ON24 Target Field' names.

Eloqua Standard Source Fields	ON24 Target Fields	Required (Y/N)
-	eventid	Y
-	key	Y
Email	updateIfExist experienceID email	Y Y Y
First Name	firstname	N
Last Name	lastname	N
Company	company	N
Title	job_title	N
Street Address 1	address_street1	N
Street Address 2	address_street2	N
City	city	N
State	state	N
Postal Code	zip	N
Country	country	N
Work Phone	work_phone	N
-	job_function	N
-	company_function	N
-	company_size	N
-	partnerref	N
-	std1	N
-	std2	N
-	std3	N
-	std4	N
-	std5	N
-	std6	N
-	std7	N
-	std8	N
-	std9	N
-	std10	N

Landing Page Redirect

If you want to add a redirect script to the "Thank You for Registering" Eloqua Landing Page, follow these instructions.

On the setup for the post registration landing page, go to Tools > Page Snippet Tools > Open HTML Editor.

Add the redirect script. The code includes the eventid and key for the webinar, as well as a merge field for the contact's email address. 

See the example below where you would replace the eventid and key from the audience URL (http://event.on24.com/wcc/r/eventid/key)

<meta http-equiv="refresh" content="0; URL=http://event.on24.com/interface/registration/autoreg/index.html?eventid=xxxxx&sessionid=1&key=yyyyy&deletecookie=true&email=<span class='eloquaemail'>EmailAddress</span>" />

This redirect would give immediate access to the webinar and only pass over the email address. When the Post Data to Server pushes the additional registrant data, the existing record with the same email address would be updated with the additional data so you would still get the complete set of registrant information in ON24.

v1.0 Data Fields

Note: The below data table is if you are using the older URL https://event.on24.com/custom/client/eloqua/postreg.jsp

Fields are case sensitive (e.g. 'eventid' and 'key'). Use the exact 'ON24 Target Field' names.

Eloqua Standard Source Fields	ON24 Target Fields	Required (Y/N)
-	eventid	Y
-	key	Y
Email	email	Y
First Name	firstname	N
Last Name	lastname	N
Company	company	N
Title	job_title	N
Street Address 1	address_street1	N
Street Address 2	address_street2	N
City	city	N
State	state	N
Postal Code	zip	N
Country	country	N
Work Phone	work_phone	N
-	job_function	N
-	company_function	N
-	company_size	N
-	partnerref	N
-	std1	N
-	std2	N
-	std3	N
-	std4	N
-	std5	N
-	std6	N
-	std7	N
-	std8	N
-	std9	N
-	std10	N

Timing

Implementation Timing

The completion time to integrate data from the ON24 platform to Eloqua will vary according to your resources’ availability. 

Scheduled Timing

Scheduled timing is when the data passes from ON24 to your end system. During the setup process, you defined when your Eloqua integration would run. Under the Batch Job Interval field, the choices were every 15 minutes, 1 hour, 4 hours, 8 hours, 12 hours, or 24 hours. 

Note: Scheduled timing is different from Availability Timing.

Availability Timing

Availability Timing refers to when data is available in the data warehouse for the integration platforms to collect.

Timing may fluctuate on heavy traffic days.

• Registrant - 15 minutes
• Attended Live - 30 minutes to 2 hours after the event ended
• Attended On-demand - 4 to 12 hours

Data is processed and made available in a defined order based on business relevance. 

• Registrant data is prioritized and becomes available first. Attendee data follows once event activity has fully completed and reporting is finalized.
• Within attendee data, live event information is prioritized ahead of on-demand activity due to its immediate relevance. On-demand data is processed after live data and appears once all reporting is complete.

This prioritization ensures that the most relevant and time-sensitive information is available first, while maintaining consistent and reliable reporting across all data sets.

Note: Availability timing is different from Scheduled timing.

Backfills

After your Eloqua data integration is complete, you will automatically get a backfill for the last 15 days of data. 

Advanced Analytics customers – you can manually export the last 2 years of data from the ON24 platform and import it into Eloqua.

From the Analytics tab in your ON24 account, click on Power Leads to export the data.

FAQs

Does the Eloqua app support customers using the ON24 EU data center?

Yes

Why does my custom object not show in the cloud feeder?

There are two reasons why your Custom Object will not show up in the Cloud Feeder. The first and most common is that your custom object was not configured correctly. You will need to make sure that you have the below 2 required fields (Email address & Event User ID). Please also ensure that they are mapped exactly as the screenshot below:

 
Unique Code Field (108 Character Limit) =  Event User ID 
Email Address Field = Email Address 

Why can I not select my batch job interval to be 15 minutes?

You won't see the 15 minute interval sync if you are using the legacy version of the app (called Registrant Data Query Service).  We recommend installing the new app, called Registrant Data Query Service-API Version in order to have this option.   

Can I use On24 registration and pass over the data to my Eloqua instance?

Yes. In order to pass the registration data over, you will need to install the Registrant Data query service – API version app. When setting up the cloud feeder you will see that the registrant data can be passed to the custom object but we suggest that this data get pushed over to your contact. 

See the Set Up tab for more information.

Can I use an additional integration from Eloqua to Salesforce?

Yes, Eloqua can sync with Salesforce. As a result, a single setup for ON24-to-Eloqua data integration is recommended. 

• Use the Salesforce Integration App​​​​​​ to set up the bi-directional sync between Eloqua and Salesforce. This Integrating Eloqua with Salesforce article explains how it works. 
• Note: Salesforce data is prioritized as the system of record and takes first priority. It is recommended that your Salesforce Admin, Eloqua Admin, and Oracle implementation services work together to set up this sync.

Available Data

The tables below list the general data available with this integration.

When setting up the integration, use the API Field Names found in this spreadsheet.

Note: Eloqua Custom Objects have a limit of 100 fields in order to pass data over. If this limit is exceeded there is no error message, the data will not pass over.  

Watch the Video

Note: The ON24 interface and Knowledge Center look different in the video, but the functionality is the same.