Pardot

Pardot Registration Integration Guide

Introduction

The Pardot Server Side Registration API allows you to seamlessly register audience members for Webcast events using a Landing Page and Form created within Pardot. This process does not require the audience member to load any pages from the Webcast within their browser to register.

A Pardot Form Layout and Form need to be setup in advance. Once setup, you will update the Form within the Layout Template as well as to both the Thank You Content and Thank You Code of the Form to facilitate the data pass.

Pardot Form Layout Template Updates

1. After the Form Layout Template is created, click "Edit layout template" in the template setup and navigate to the "Form" tab.

Pardot


2. On the "Form" tab, confirm the "Thank You" code is located above the "form" tag. Depending on certain settings, no updating may be required. The "form" tag is highlighted below for illustrative purposes.

Pardot


The "Thank You" code that needs to be moved located above the "form" tag appears as follows:

%%form-if-thank-you%%
    %%form-javascript-focus%%
    %%form-thank-you-content%%
    %%form-thank-you-code%%
%%form-end-if-thank-you%%


Pardot Form Updates

1. After the Form is created, click "Edit form" in the form setup and navigate to the "Complete Actions" step.

Pardot


2. Select the "Thank You Code" tab and paste in the code below in the box provided:

<script type="text/javascript">// <![CDATA[
document.hidden_form.submit();
// ]]>
</script>

Below is an example of how the updated "Thank You Code" should appear. Please be sure that the "Always display form after submission" option is checked and save the setup.

Pardot


3. Next, select the "Thank You Content" tab and click on the HTML button.

Pardot


4. In the WYSIWYG editor, you will need to enter the code used to submit the registration to your Webcast event. Below is sample code, which passes First Name, Last Name, Company and Email Address fields (default Webcast registration fields).

The bold values in the this example need to be updated. Enter 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.

The underlined portion of the code above is the code containing the registration fields that will pass to your Webcast event. You can customize this code to add/remove any additonal registration fields you want to pass into the Webcast. For detailed instructions on how to customize which fields are passed to your webcast, skip to step 6.

<blockquote>
<form action="https://event.webcasts.com/viewer/regserver.jsp?ei=1234567&pass=abcd001" id="0" method="POST" name="hidden_form" target="sendreg">
<input name="company" type="hidden" value="%%company{html}%%" /> <input name="lname" type="hidden" value="%%last_name{html}%%" /> <input name="fname" type="hidden" value="%%first_name{html}%%" /> <input name="email" type="hidden" value="%%email{html}%%" />
<iframe height="1" name="sendreg" src="demo_iframe.htm" style="display: none" width="1"></iframe>
<p>&nbsp;</p>
</form>
</blockquote>

5. Enable the "Always display form after submission" checkbox. Save this page to complete the setup.

Pardot


6. This step provides more details on how to customized what registration fields pass into your Webcast's reports. This is an optional step.

Below is an example of the formatting used to pass a registration field from Pardot to your Webcast:

<input name="webcast_parameter_name" type="hidden" value="pardot_parameter_name"/>

Below is a list of Webcast Registration Fields, including the Webcast Paramter names. These fields can be added in step 4 using the code provided above to customize which fields are passed to your Webcast. Please refer to Pardot for a list of corresponding Pardot Parameter names.

Parameter Description Values Character Limit
ei*
Event ID
(Ex. 1234567)
Number
7
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
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.
  • 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 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.
  • 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 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.

Pardot


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.

Pardot


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:

Message Description
"Success."
The registration has been successfully submitted to the event.
"Event not found."
Invalid Event ID
"Unauthorized."
The client pass ID does not have access to the Event ID.
"Registration for this event is prohibited."
The event is configured for anonymous registration.
"Email not found."
A valid email address is required for registration. This message indicates an email was not passed.
"Email format not valid."
Invalid email formatting
"User already registered."
An audience member is already registered for the event ID based on email address.
"No reg data sent."
General error - Contact Support for help.