Seamless Registration enables you to send registrant information from your remote webcast registration page to your ON24 registration database, using a script.

Important: The Login Only Option toggle should be ON to use Seamless Registration.  You can find the toggle under Settings on the webinar's Registration setup page.

Toggling Enable Login Only to ON causes Registration to appear disabled, however, Registration is still active. In order to update the active Registration Fields the Login Only Option should be first switched OFF. Once any edits are made it should be switched back ON.

Things to Know

When using seamless registration, use the same registration fields in the same order, to ensure the data carries over correctly. 

See below for more information on which fields can be passed to ON24. 

And find more information on registration mapping here.

Partner Referral

If you use multiple registration pages for the same webcast, you can include a Partner Referral code to track the individual campaigns. 

For more information visit the Partner Referral page.

Best Practices

The simplest approach and the one we see most clients take is to redirect the user to ON24 once they've finished filling out the registration page on a third party site. The user sees an ON24-hosted "Thank you for registering, this event will start on...." Lobby page and they get an ON24 cookie that serves as the persistent storage to identify the user. With the cookie present, subsequent calls to the event send the user to the ON24 "Audience URL", which bypasses the registration page if a valid cookie is found. You also have the option of having ON24 automatically redirect to a generic third-party hosted "thank you for registering" page instead, by passing in a URL in the optional "lobby" parameter.

To see an example of a Seamless Registration page, click here.

Available Registrant Fields

Specific fields can be passed to the ON24 registration database. The parameter names are case-sensitive. Please note that you may have changed the Display Label of the field, but the underlying parameter name is retained.  See this link for seamless registration parameters.

Please associate the fields with the correct parameter name (i.e. pass the email address in the "email" field rather than in some other field). If the data you want to store is not in one of the named demographic fields, use std1-std10.

Any values sent which exceed the designated character limit will be truncated.

Records containing the email address of a registrant who is already in the database for this webcast will be updated with the latest values being sent.

Seamless Multi-Registration

Seamless Multi-Registration is available under Multi Registration in Webcast Elite. Seamless Multi-Registration supports the same registration field parameters as the Seamless Registration process for individual events.

The seamless registration for multi-registration pages is designed to be used with a single url without the use of separate event IDs. The seamless registration for Multi Registration works to register each individual for all events listed on the page. See an example of the html for a seamless POST method Multi Registration page below, with the shared MRP seamless URL in the form action.

<h3><u><div id="seamlessreg"></div>Seamless Registration Form</u></h3>
<form action="https://event.on24.com/wcc/mrs/5805XX/A7226F80BB5AFD05127EADEF150FFAXXX" method="POST">

<input type="hidden" name="deletecookie" value="true">
<table border="1">
<tr>
<td>First Name</td>
<td><input type="text" name="firstname" value="" required></td>
</tr>
<tr>
<td>Last Name</td>
<td><input type="text" name="lastname" value="" required></td>
</tr>
<tr>
<td>Email Address</td>
<td><input type="text" name="email" value="" required></td>
<tr>
<td>Company</td>
<td><input type="text" name="company" value="" required></td>
</tr>
</table>
<p><input type="submit" value="Submit"></p>
</form>

Sending Registrant Data

The script can be used with an HTTPS GET or HTTPS POST. For both methods, use HTTPS.

The webcast's unique event ID and key parameters must be included regardless of the method you use to send the Registrant data. Those values are contained within the Audience URL. You can access the Audience URL by clicking the Webcast URLs link on the Webcast Overview page; or by clicking the utility icon in the rightmost column on the My Webcasts page.

The EventID is the first numeric value that appears after the r/; the key is the second alphanumeric string which appears after the /. The Session ID will always be equal to 1.

Example: https://event.on24.com/wcc/r/1007892/39C070333A328199706BA21244AD8641

Using "HTTP GET" Method

The GET method relies on JavaScript redirection, which requires a web browser; this method will fail if used for server-to-server requests.
 

Rules to Remember:

If any of the parameters include the SPACE character, it must be defined using URL encoding i.e. "%20", (eg, &country=United%20States). Some special characters embedded within the field values, like "=", "&" etc., should also always be encoded.

When in a batch mode or registering multiple users, you must also send the additional "deletecookie" parameter set to "true" (ie. deletecookie=true).

Example: Sending first name, last name, email, and company.  Be sure to replace the XXXXs with your webinar event ID and Key.



If you are having trouble with the standard HTTPS GET URL, you can try https://event.on24.com/utilApp/r instead.

Using "HTTP POST" Method

You can also send registrant data to the ON24 Event Database by using a POST method.
 

Rules to Remember:

When in a batch mode or registering multiple users, you must also send the additional "deletecookie" parameter, setting it to "true", thus: delete a hidden element for POST method.

UTF input isn't necessary if sending UTF-8, which is the default. If you’re sending characters using a different encoding, change the hidden value to the proper character set.

For example, ISO-8859-1

Example: Sending first name, last name, email, and company.  Be sure to replace the XXXXs with your webinar event ID and Key.


 

<form name="myform" action="https://event.on24.com/utilApp/r" method="POST">

<input type="hidden" name="eventid" value="XXXXX">

<input type="hidden" name="sessionid" value="1">

<input type="hidden" name="key" value="XXXXX">

<input type="text" name="firstname" value="john">

<input type="text" name="lastname" value="smith">

<input type="text" name="email" value="john.smith@abc.com">

<input type="text" name="company" value="ABC, Inc.">

</form>