Installation and API Credentials
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 at the bottom right 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:
- Client ID
- Token Key
- Token Secret
- Event ID (if left empty the app will pull data from all events from account)
- 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 (pictured above) can include any or all of these fields (pictured below). Eloqua requires "email" and that will mapped by default.
*The below fields would be for passing to the Contact Only (Not the Custom Object)
|
ON24 Field Name |
Description |
Data Type |
|
|
Email entered by the registrant. Required by Eloqua, mapped in App by Default |
Text |
|
Address street 1 |
Address1 entered by registrant |
Text |
|
Address street 2 |
Address2 entered by registrant |
Text |
|
Campaign code |
Any external identifier that should have a 1:1 relationship with the ON24 eventid. |
Text |
|
City |
City entered by registrant |
Text |
|
Company |
Company name of the registrant |
Text |
|
Company industry |
The company industry entered by the registrant. |
Text |
|
Company size |
The company size entered by the registrant. |
Text |
|
Country |
Country entered by registrant |
Text |
|
Custom field 1 (std1) |
This is reserved for custom fields in the registration page. Please note that the field designated as a specific custom field must remain uniform throughout the ON24 Platforms (i.e., webinars, templates, E-Hub, and Target, etc. |
Text |
|
Custom field 2 (std2) |
Custom Field #2 - See the definition for std1. |
Text |
|
Custom field 3 (std3) |
Custom Field #3 - See the definition for std1. |
Text |
|
Custom field 4 (std4) |
Custom Field #4 - See the definition for std1. |
Text |
|
Custom field 5 (std5) |
Custom Field #5 - See the definition for std1. |
Text |
|
Custom field 6 (std6) |
Custom Field #6 - See the definition for std1. |
Text |
|
Custom field 7 (std7) |
Custom Field #7 - See the definition for std1. |
Text |
|
Custom field 8 (std8) |
Custom Field #8 - See the definition for std1. |
Text |
|
Custom field 9 (std9) |
Custom Field #9 - See the definition for std1. |
Text |
|
Custom field 10 (std10) |
Custom Field #10 - See the definition for std1. |
Text |
|
Department |
Department entered by registrant |
Text |
|
Event start |
Start time of the Event |
Date |
|
Event user id |
Unique user identifier auto-generated by ON24 |
Text |
|
Firstname |
First name of the registrant |
Text |
|
Job function |
Job function entered by the registrant |
Text |
|
Job title |
Job title entered by the registrant |
Text |
|
Lastname |
Last name entered by the registrant |
Text |
|
Live end |
End Time of the Event |
Date |
|
Marketing email |
Boolean value (True/False) which will determine whether the registrant opts in to receive additional marketing emails. Default value is false. |
Text |
|
Partnerref |
To track the origin of the registrant/attendee. If you use multiple registration pages for the same webcast, you can include a Partner Referral code in the audience URL to track the individual sources. For example, you may promote an event through an email campaign or post it in Facebook. As a result, the registration URL may appear as below. However, the partnerref code value would be "email" or "facebook." ***NOTE: partnerref WILL work with links shortened into bit.ly links. The audience url with the partnerref can be shortened into bit.ly links. Do not append the partnerref to an existing bit.ly link. |
Text |
|
Source campaign code |
Campaign Code captured if registrant originated from eHub |
Text |
|
Source event id |
Unique identifier used to determine if the source was Webcast Elite, Engagement Hub, Go Live, or Target. Say a registrant went into Engagement Hub and clicked on videos and content. The sourceeventid would reflect eHub. If someone registered for an Elite event, then the value would reflect the eventid. |
Numeric |
|
State |
The state (i.e., California) entered by the registrant. |
Text |
|
Work phone |
The work phone number entered by the registrant. |
Text |
|
Zip |
The zip code entered by the registrant. |
Text |
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:
- 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.
- 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.
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.
The custom object can include any of the following fields related to attendee information.
Please 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.
| ON24 Field Name | Description | Data Type |
| Answered polls | The number of polls the user responded to. | Number |
|
Answered surveys |
The number of surveys the user responded to. |
Number |
|
Archive minutes |
The total number of minutes this user attended the archived portion of this event. Multiple console launches are aggregated into a single number. |
Number |
|
Asked questions |
The number of questions the user asked. |
Number |
|
Audience URL |
Audience URL. |
Large text |
|
Breakout id 1 |
Display the Id for first break out widget submitted |
Number |
|
Breakout name 1 |
Display the name for first break out widget submitted |
Text |
|
Breakout role 1 |
Display the role for first break out widget submitted |
Text |
|
Breakout cumulative live minutes 1 |
Display the cumulative live minutes for first break out widget submitted |
Number |
|
Breakout id 2 |
Display the Id for second break out widget submitted |
Number |
|
Breakout name 2 |
Display the name for second break out widget submitted |
Text |
|
Breakout role 2 |
Display the role for second break out widget submitted |
Text |
|
Breakout cumulative live minutes 2 |
Display the cumulative live minutes for second break out widget submitted |
Number |
|
Breakout id 3 |
Display the Id for third break out widget submitted |
Number |
|
Breakout name 3 |
Display the name for third break out widget submitted |
Text |
|
Breakout role 3 |
Display the role for third break out widget submitted |
Text |
|
Breakout cumulative live minutes 3 |
Display the cumulative live minutes for third break out widget submitted |
Number |
|
Breakout id 4 |
Display the Id for fourth break out widget submitted |
Number |
|
Breakout name 4 |
Display the name for fourth break out widget submitted |
Text |
|
Breakout role 4 |
Display the role for fourth break out widget submitted |
Text |
|
Breakout cumulative live minutes 4 |
Display the cumulative live minutes for fourth break out widget submitted |
Number |
|
Breakout id 5 |
Display the Id for fifth break out widget submitted |
Number |
|
Breakout name 5 |
Display the name for fifth break out widget submitted |
Text |
|
Breakout role 5 |
Display the role for fifth break out widget submitted |
Text |
|
Breakout cumulative live minutes 5 |
Display the cumulative live minutes for fifth break out widget submitted |
Number |
|
Call to actions clicks 1 |
# of clicks on the first Take Action widget (formerly Call To Action) |
Number |
|
Call to actions clicks 2 |
# of clicks on the second Take Action widget (formerly Call To Action) |
Number |
|
Call to actions clicks 3 |
# of clicks on the third Take Action widget (formerly Call To Action) |
Number |
|
Call to actions date 1 |
Date and time user clicked on the first Take Action widget (formerly Call To Action) |
DateTime |
|
Call to actions date 2 |
Date and time user clicked on the second Take Action widget (formerly Call To Action) |
DateTime |
|
Call to actions date 3 |
Date and time user clicked on the third Take Action widget (formerly Call To Action) |
DateTime |
|
Call to actions id 1 |
Display the unique identifier of the first CTA. |
Number |
|
Call to actions id 2 |
Display the unique identifier of the second CTA. |
Number |
|
Call to actions id 3 |
Display the unique identifier of the third CTA. |
Number |
|
Call to actions name 1 |
Display name of the first Take Action widget (formerly Call To Action) |
Text |
|
Call to actions name 2 |
Display name of the second Take Action widget (formerly Call To Action) |
Text |
|
Call to actions name 3 |
Display name of the third Take Action widget (formerly Call To Action) |
Text |
|
Campaign code |
Data stored in the Campaign Code field in Elite. |
Text |
|
Contact us widget action |
Contact us widget action. |
Text |
|
Contact us widget id |
Contact us widget auto-generated unique id. |
Number |
|
Contact us widget name |
Contact us widget name. |
Text |
|
Contact us widget submitted timestamp |
Contact us widget submitted timestamp. |
DateTime |
|
Contact us widget type |
Contact us widget type. |
Text |
|
Cumulative archive minutes |
Number of minutes the user attended the archived/on-demand portion of this event. Multiple console launches are aggregated into a single number. |
Number |
|
Cumulative live minutes |
Number of minutes the user attended the live portion of this event. Multiple console launches are aggregated into a single number. |
Number |
|
Cumulative visits duration 1 - 10 |
The cumulative visits duration for the <1 - 10> location widget submitted. |
Integer |
|
Custom tags |
This tag lists the custom tags related to the event. |
Large text |
|
Demo conversions widget action |
Demo conversions widget action. |
Text |
|
Demo conversions widget id |
Demo conversions widget id. |
Number |
|
Demo conversions widget name |
Demo conversions widget name. |
Text |
|
Demo conversions widget submitted timestamp |
Demo conversions widget submitted timestamp. |
DateTime |
|
Demo conversions widget type |
Demo conversions widget type. |
Text |
|
Drift widget action |
Provides the booked date for "scheduling:meetingBooked." | String |
|
Drift widget id |
Unique identifier for the drift widget |
String |
|
Drift widget name |
Name of activity ("startConversation", "conversation:playbookClicked", or "scheduling:meetingBooked") |
String |
|
Drift widget submitted timestamp |
The moment when the user interacting with the widget in the console. |
DateTime |
|
Drift widget type |
"drift" | String |
|
Engagement score |
This is a number between 0 and 10.0 measuring how engaged a user was based on activity during the webcast. |
Numeric |
|
Event id |
ON24 unique event identifier. |
Number |
|
Event title |
Title of the event. |
Text |
|
Event user id |
Unique user identifier auto-generated by ON24 | String |
|
First live activity |
The date/time this attendee first opened the event console during this live event. |
DateTime |
|
Free trial widget action |
Free trial widget action. |
Text |
|
Free trial widget id |
Free trial widget auto-generated unique id. |
Number |
|
Free trial widget name |
Free trial widget name. |
Text |
|
Free trial widget submitted timestamp |
Free trial widget submitted timestamp. |
DateTime |
|
Free trial widget type |
Free trial widget type. |
Text |
|
Get pricing widget action |
Get pricing widget action. |
Text |
|
Get pricing widget id |
Get pricing widget auto-generated unique id. |
Number |
|
Get pricing widget name |
Get pricing widget name. |
Text |
|
Get pricing widget submitted timestamp |
Get pricing widget submitted timestamp. |
DateTime |
|
Get pricing widget type |
Get pricing widget type. |
Text |
|
Last archive activity |
The date/time this attendee was last known to have an open event console during the archived event. |
DateTime |
|
Live end |
End time of event. |
DateTime |
|
Live minutes |
The total number of minutes this user attended the live event. Multiple console launches are aggregated into a single number. |
Number |
|
Location code 1 - 10 |
The code for the <1 - 10> location widget submitted. |
String |
|
Location id 1 - 10 |
The Id for the <1 - 10> location widget submitted. |
String |
|
Location name 1 - 10 |
Display the name for the <1 - 10> location widget submitted |
String |
|
Meeting conversions widget action |
Meeting conversions widget action. |
Text |
|
Meeting conversions widget id |
Meeting conversions widget auto-generated unique id. |
Number |
|
Meeting conversions widget name |
Meeting conversions widget name. |
Text |
|
Meeting conversions widget submitted timestamp |
Meeting conversions widget submitted timestamp. |
DateTime |
|
Meeting conversions widget type |
Meeting conversions widget type |
Text |
|
Poll answer 1 |
User-submitted answer to the poll. |
Text |
|
Poll answer 2 |
User-submitted answer to the poll. |
Text |
|
Poll answer 3 |
User-submitted answer to the poll. |
Text |
|
Poll answer 4 |
User-submitted answer to the poll. |
Text |
|
Poll answer 5 |
User-submitted answer to the poll. |
Text |
|
Poll question 1 |
Client-determined poll question asked to the audience. |
Text |
|
Poll question 2 |
Client-determined poll question asked to the audience. |
Text |
|
Poll question 3 |
Client-determined poll question asked to the audience. |
Text |
|
Poll question 4 |
Client-determined poll question asked to the audience. |
Text |
|
Poll question 5 |
Client-determined poll question asked to the audience. |
Text |
|
Prospect Engagement Profile |
Prospect Engagement Profile URL. |
Large text |
|
Questions and answers |
This tag lists the questions asked by the user and answers from presenters. |
Large text |
|
Resource viewed 1 |
Name of 1st resource viewed in the Resource Widget. |
Text |
|
Resource viewed 2 |
Name of 2nd resource viewed in the Resource Widget. |
Text |
|
Resource viewed 3 |
Name of 3rd resource viewed in the Resource Widget. |
Text |
|
Resource viewed 4 |
Name of 4th resource viewed in the Resource Widget. |
Text |
|
Resource viewed 5 |
Name of 5th resource viewed in the Resource Widget. |
Text |
|
Source campaign code |
Campaign Code from the originator event (e.g. EHub or Virtual Conference). |
Text |
|
Source event id |
Unique identifier used to determine if the source was Webcast Elite, Engagement Hub, Go Live, or Target. Say a registrant went into Engagement Hub and clicked on videos and content. The sourceeventid would reflect eHub. If someone registered for an Elite event, then the value would reflect the eventid. |
String |
|
Sponsor id 1 - 10 |
The sponsor id for the <1 - 10> location widget submitted. |
String |
|
Sponsor name 1 - 10 |
The sponsor name for the <1 - 10> location widget submitted. |
String |
|
Survey answer 1 |
User-submitted answer to the survey question. |
Text |
|
Survey answer 2 |
User-submitted answer to the survey question. |
Text |
|
Survey answer 3 |
User-submitted answer to the survey question. |
Text |
|
Survey answer 4 |
User-submitted answer to the survey question. |
Text |
|
Survey answer 5 |
User-submitted answer to the survey question. |
Text |
|
Survey question 1 |
Client-determined survey question asked to the audience. |
Text |
|
Survey question 2 |
Client-determined survey question asked to the audience. |
Text |
|
Survey question 3 |
Client-determined survey question asked to the audience. |
Text |
|
Survey question 4 |
Client-determined survey question asked to the audience. |
Text |
|
Survey question 5 |
Client-determined survey question asked to the audience. |
Text |
|
Total resources viewed |
Total number or resources viewed from the Resource Widget. |
Number |
|
Visits duration 1 - 10 |
The visits duration for the <1 - 10> location widget submitted. |
Integer |
|
Visits 1 - 10 |
The number of visits for the <1- 10> location widget submitted. |
Integer |
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'. In this case, for ON24-related use cases, Contact data will be referring to Registrant-related information, whereas Custom Object refers to 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:
Comments
0 comments
Please sign in to leave a comment.