Eloqua Registration Integration Guide

Introduction

The following document provides step-by-step directions for setting up an Eloqua registration integration with your webcasts. This integration will allow you to seamlessly register audience members for Webcast events using an Eloqua form. The process does not require the audience member to load any pages from the Webcast within their browser to register.

This is an Open API, allowing for setup and testing at your convenience. To confirm the "pass" parameter and/or link that should be used in the setup, please contact Support for assistance.

Registration Integration Setup

1. After the form setup is complete in Eloqua, click "Processing" in the top right.
2. Click "+" and double-click on the "Post Data to Server" option in the menu.
3. Select "Constant Value" in the dropdown and enter the Server Side Registration URL configured for the event you want to receive the submitted data.

Below is an exmaple of the Server Side Registration URL. The bold values in this example need to be updated to include the 7-digit Event ID for your presentation as the "ei" parameter and your company's Client ID as the "pass" parameter. Contact Support to confirm the "pass" value you should use.

Sample Server Side Registration URL
https://event.webcasts.com/viewer/regserver.jsp?ei=1234567&pass=abcd001&tp_regconfemail=1
Parameter Description Values Character Limit

ei* Event ID
(Ex. 1234567) Numbers 7

pass* Client ID
(Ex. abcd001) Alphanumeric, utf-8 7

tp_regconfemail Enable a Registration Confirmation Email from the Webcast 1 1

Notes:

A "*" next to a parameter name in the table above indicates the field is required.

The "pass" parameter is case-sensitive. Contact Support to confirm your company's "pass" value.

If the "tp_regconfemail=1" paramater is included in the Server Side Registration URL and Registration Confirmation Email is enabled in the Webcast event, a participant will receive a confirmation email after being registered. If registration confirmation emails are not enabled or any value other than "1" is sent in the parameter, the confirmation email will not be sent.

If the "tp_regconfemail=1" parameter is not included in the Server Side Registration URL, the system submitting the registration request is responsible for delivering the Webcast URL to audience members.

Parameter	Description	Values	Character Limit
ei*	Event ID (Ex. 1234567)	Numbers	7
pass*	Client ID (Ex. abcd001)	Alphanumeric, utf-8	7
tp_regconfemail	Enable a Registration Confirmation Email from the Webcast	1	1

Field Mapping

The field mapping between the form Source Fields and the Target Fields on the server to which you are reposting are set up automatically based on the HTML names of the Source Fields. These fields need to match the parameters below to properly map to the server to which you are reposting.

Below is a list of fields available for mapping:

Parameter	Description	Values	Character Limit
fname	First Name	Alphanumeric, utf-8	256
lname	Last Name	Alphanumeric, utf-8	256
company	Company Name	Alphanumeric, utf-8	256
title	Business Title	Alphanumeric, utf-8	256
address1	Street Address	Alphanumeric, utf-8	256
address2	Street Address - Extra	Alphanumeric, utf-8	256
city	City	Alphanumeric, utf-8	256
state	State	Alphanumeric, utf-8	256
country	Country	Alphanumeric, utf-8	256
postalcode	Postal/Zip Code	Alphanumeric, utf-8	256
phone	Primary Phone Number	Alphanumeric, utf-8	256
cell	Cell/Mobile Number	Alphanumeric, utf-8	256
fax	Fax Number	Alphanumeric, utf-8	256
email*	Email Address	Ascii email	128
custom_question1	Custom Registration Question Answer	Alphanumeric, utf-8	256

Notes:

A "*" next to a parameter name in the table above indicates the field is required.
The system will only accept registration parameters that are configured on the Webcast's Registration Form. Submitted fields that are not configured on the Registration Form will be discarded.
Parameter values should be properly URL encoded (Ex. Blank spaces should be replaced with %20).
All parameters should be validated before submission or they may be rejected by the server. For example:

Registration requests with invalid email addresses will not be accepted.
Fields containing html or other script tags will be blocked by the system's security filter.

For Custom Registration Questions, the parameter name should match the "Report Column Title" entered when creating the question in the Webcast Administration Portal. This field is case-sensitive and requires a unique label.
For Custom Registration Questions with multiple answers, repeat the parameter name for each answer submitted. The answers will appear grouped together in the reports.
If the "tp_regconfemail=1" paramater is included in the server-side registration link and registration confirmation emails are enabled for the event, a participant will receive a confirmation email after being registered. If registration confirmation emails are not enabled or any value other than "1" is sent in the parameter, the confirmation email will not be sent.
If the "tp_regconfemail=1" parameter is not included in the server-side registration link, the system submitting the registration request is responsible for delivering the Webcast URL to audience members.
Security options enabled for the webcast will not stop registrations. These settings are only tested when the audience member attempts to enter the actual presentation.
To ensure quality, always test this implementation before opening access to your audience to ensure registration fields and corresponding answers are passed correctly. The best way to test this is to submit a test registration on the Eloqua form and check the Webcast's reports to verify all data has been collected.

Test the Setup

Once the setup is complete, any submissions of the Eloqua form should immediately appear in the Webcast reports. To test the setup, submit a sample registration through the Eloqua form.

1. In the Webcast platform, select the Webcast where data should be passing and choose the "Reports" button below.
2. In the Reports interface, choose the "Audience Details" report (default) and click "Run My Report". The report that displays will include any registration fields passed in the setup, but will have blank fields for any data that was not passed or is related to audience participation.
3. If all the data appears correct in the reports, no further action is needed. If some or all of the data is not received, review the Server Side Registration URL used in setup and confirm all fields have been correctly mapped.

Return Messages

When a registration is submitted, you will receive a Return Message to confirm receipt. Refer to the list below for more information on the Return Message: