When you create a webinar, BigMarker adds some hidden registration fields by default
When you create a webinar, series or event, you will notice that it comes with a few hidden registration fields already created. These fields are added by default by BigMarker for use in registration, or to track certain activities. Depending on your needs, you may or may not need these fields, but it is a good idea to leave them in place.
UTM Codes
For everything on BigMarker, you will see a few UTM codes added to the hidden fields: utm_medium, utm_source, and utm_bmcr_source. These codes are either commonly used accross many platforms, or used in the share link settings when adding a source to your link:
Registration_user_agent
With the Registration_User_Agent field, BigMarker collects device and OS information for users that registered. This information is great for tracking the most commonly used devices that your audience will be using when attending your event. You are able to view this under their profile in the Manage Webinar Registration section on your event backend, or in any downloaded reports.
Note that this field will not be populated if you manually add registrants to your session, or if registrants are added via an integration import or webhook. Only users who register on BigMarker landing pages will have their information logged in this field.
Other activity fields
BigMarker will automatically add a few fields that will track a user's activity with the session or series. These fields will be updated by BigMarker during registration or the live event, and should not be deleted:
- Responded to survey - The field will display either "Yes" or "No" depending on if the registrant submitted the webinar survey
- Ticket Pass Name - This field will display any and all tickets that were purchased. This field will only display for events with ticket passes.
- On-site check in status - The field will display either "Yes" or "No" depending on if the registrant is marked as checked in for the event.
If you are hoping to have other activities available as registration fields such as the price that was paid for a registration or how many chat messages were sent, look into using calculated fields.