How do I pre-populate my registration forms and track attendees through registration?

With property names, registration form fields can be pre-populated for convenience or used to track attendee data from registration to integration.

By now, you probably know about properties and property names in eWebinar.  If not, you should first read this article, which talks about how to get data out of eWebinar and into your CRM or marketing automation software.  

In this article, we'll show you how to use property names to put data into eWebinar via the attendee registration form.

In one scenario, you might want to pre-populate some of the registration form fields based on your knowledge of a registrant.  In another popular scenario, you might want to track some piece of data from registration all the way through to your integrated CRM, for example, to keep track of a proprietary ID you have for that attendee. 

Property names make this easy; you can populate any of the registration form fields for any registrant using parameters added to your registration form's URL: Here is the process:

First, get your registration URL.  It should look something like this:

https://ilove.ewebinar.com/webinar/interactive-demo-getting-started-with-ewebinar-1187

Then add register/form to the end of it. This is the URL to your registration form and should look like this

https://ilove.ewebinar.com/webinar/interactive-demo-getting-started-with-ewebinar-1187/register/form

To populate fields automatically, you would add the property names and values to the either the registration or registration form URL as query parameters.  The parameters are what show up after the ? of a URL and take this form: propertyName=value. 

To put more than one parameter in the URL, separate them with the & character.  

So, let's say you wanted to pre-populate your registration form with the Name, Email, and Proprietary ID — a property named proprietaryID that contains a Proprietary ID from your system —  the URL would look something like this:

https://ilove.ewebinar.com/webinar/interactive-demo-getting-started-with-ewebinar-1187/register/form?Name=Robin%20Hood&email=robinhood@nottingham.com&proprietaryId=12345

In the example above, the registrant's name is Robin Hood, their email is robinhood@nottingham.com, and their Proprietary ID is 123245.

NOTE: We used "%20" above to represent the space between "Robin" and "Hood". Alternatively, if the form had both a First Name and Last name field, we could have added two parameters to the URL instead of one: firstName and lastName.

About hidden fields

In our example, Proprietary ID is a field you probably don't want your attendee to be able to see or change, as it would just confuse them. The only reason you added it was to track the ID of an attendee through their lifecycle in eWebinar.

This is why we support Hidden fields in our registration form. If you set a field as Hidden, you can still pass through data via the URL, but the attendee will never see it.

Properties built-in to the registration form

There are a few properties that are built in, but which you can use to pre-populate your registration form in via the mechanism above.  They are: