With property names, registration form fields can be pre-populated for convenience or to track data from registration to integration.
By now you probably know about property names in eWebinar. If not, you should first read this article: How to capture attendee interactions and registration form fields in my integrations.
Property names in that article were useful in getting data out of eWebinar and into your integrations. 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 through to your integrations. For example, to keep track of a proprietary ID you know of for that attendee.
Property names make this easy; you can populate any of the registration form fields for a registrant directly on the URL.
First, get your registration URL. It should look something like:is:
The URL to your registration form is just that with register/form added on the end, like this:
To populate fields automatically you would pass into either URL the property names and values to either of those URLs as query parameters. These are parameters that show up after the ? of a URL and where each parameter takes the form propertyName=value. To put more than one on the URL you separate them with the & character.
So, let's say we wanted to pre-populate the registration form with a first name, last name email and a property name called proprietaryName that contains an ID we know about. The URL would look something like this:
In the example above proprietaryId is a field you probably don't want your attendee seeing as it would confuse them. You're only using the field to track an ID during the lifecycle of an attendee in eWebinar. That's why we support Hidden fields in our registration form. To set a field as Hidden just select that as the type of the field in the Registration form editor.
Built-in propertyName fields
There are a few propertyName fields that are built in but which you can fill in via the mechanism above. They are:
Used to specify the session time to register for. The value must be either:
This specifies the time of the session in ISO 8601 format. It's a standard format between services. You can specify any valid session time based on the schedule you set for this webinar.
This states the attendee wants to register for a replay session.
|firstName||First name of attendee|
|lastName||Last name of attendee|
|Email of attendee|
|source||Any text of your choosing used to track where this registration came from typically|