By defining property names you can easily map any attendee interaction into a field of your CRM's contact or lead object.
There are two main ways an attendee interacts with your eWebinar. Initially, when registering, there's a set of registration form questions they fill out. After they've joined the webinar you can program any number of interaction cards in sync with your video to ask attendee's a question or solicit an action. Polls are a great way to ask a question based on a limited set of answers, Questions allow for attendee's to answer in their own language, and Offers give attendee's a call to action button they can click on.
What you will typically want to do is have these answers or actions (in the case of "Clicking" the CTA) integrated in some way into your CRM. To do this there are 2 steps you need to take:
1. Define properties by creating property names for the interaction cards and registration fields you want to integrate.
In registration form fields
When you're in the registration form editor you'll notice you can create new fields, enter a question for them and specify the type of field you want. What you may not have noticed is that you can also specify a "property_name" for these fields. The default fields of first name, last name and email already have them: firstName, lastName and email respectively. You can define a property name for any field you've added by typing it into the input box just under the question for the field.
Property names have a few rules:
Property names may not contain spaces or most special characters and are case insensitive - so lastName is treated as the same property as lastname. You'll see later that this will make it easier to interact with these fields from other services.
You may not have the same property name twice in the same eWebinar. If you could it wouldn't be obvious which answer to map to which CRM field.
You may have the same property name across eWebinars. This means, for example, that you could ask the same question across different eWebinars and have all of those answers map to the same CRM field. That way, if you're asking "Which country are you from?" you can always map the answer to the field in your CRM named country. This does mean if your attendee's answer the question multiple times, once per eWebinar, you'll only see that last response in your CRM.
Here's an example of a registration form which has one of its properties, a Hidden property (will discuss Hidden properties at the bottom of this article) set to propietaryId. You can also see above it that first name last name and email have preset property names of firstName, lastName, and email correspondingly. These property names can not be changed.
In interaction cards
eWebinar has a multitude of ways people can interact with your video. With property names you can now also capture those interactions into your CRM in much the same way. First, configure your CRM integration in the Integrations tab so that you have an integration connected with basic configuration. Once that is set up, you'll notice when you create or edit an interaction that there's a new tab in the interaction card called Integrations. Here is where you can define the property name for this interaction card. The same rules for property names as above applies 😉
This is an example of a filled in Poll interaction card with the property name set to plannedUse
2. Map these properties to fields in your CRM typically within your Contact or Lead objects.
Now that you have property names defined across the registration form fields and interaction cards you want to capture, the only thing left to do is tell the system where you want the values for these properties to land in your CRM object. Typically this object will be either a Lead, Contact or List object but most CRMs allow you to define custom fields where you want to keep track of extra information such as this.
First, go into your CRM and make sure you have any custom fields you want defined. Typically they should be of set to type Text. eWebinar will only send text strings from answers and interactions.
Now that you have property names defined in eWebinar and custom fields set up in your CRM go to the eWebinar Integrations panel. Click on the Integration you want to set up where you'll find a property to field mapper. On the left you'll see a chooser that lets you pick one of the property names you defined within your eWebinars. Pick a property. On the right you'll see a chooser that lists all the fields available to map to within your CRM object. Pick a field.
You'll want to define the custom properties in your CRM before you go into the Integration card to define these mappings.
Here you have an integration card for Mailchimp where we're in the middle of defining what property name should map to the Code field on Mailchimp:
That's it! The next time an attendee registers or finishes a webinar you should see these fields get populated in your CRM if they answered the question or interacted with the card.
If you're using Zapier for your integration you'll see the property names you defined when you test your trigger. You can then do mappings of those properties to CRM objects much like we did above but in the Zapier Zap creation experience.
Using property names in your registration forms
Above you've seen how property names can be useful in getting information out of eWebinar. However, there are times you want to be able to easily populate information into eWebinar on behalf of an attendee who's registering for a session. To find out more about this see How do I populate and track fields for attendees during registration.