Event Analytics

Overview

The Event Analytics page summarizes project information regarding attendee registrations for your event, event session capacity and responses to multiple-choice questions presented to attendees. It is a great place to quickly get a real-time snapshot of the performance of your event in terms of attendees. 


Date range filter

The Date Range filter: 
- specifies a date range for the data presented and, by default, applies the date that the first attendee record was created to the current date. 
- limits the data presented to only those attendee records CREATED within that range. 
- by default, it applies the date that the first attendee record was created to the current date

This filter and specified date range will apply to all data presented on this page. 


Registration Conversions

Registration Conversions: 

- displays the number of registrations created for all event sessions within the applicable date range, and the number of those registrations that have resulted in attendance.
- marks Registrants as attended when they are checked in through the Limelight Check-in app or when an attended date to is added to their record(s) from the Limelight portal.
- for lead generations, the number of registrations will correspond to the number of leads collected. In this case, the attendee count will be zero, since once a lead is collected, there are no attendance activities expected. 


Analytics Glossary

Unique
- For registrations and attendees: describes how many INDIVIDUALS registered and attended.
- For lead collection projects: the number of unique leads collected.
- These counts are evaluated based on whether multiple registration records have the same:
     - first name
     - last name
     - email

Repeats occur when
- the same individual registers for a single session multiple times or
- when an individual registers for multiple sessions within the event.
- may also occur when registrations do not contain complete personal information (any field from first name, last name or email are missing so the database recognizes it as a repeat based on one or more of the mentioned factors).
For lead collection projects, the repeat count is the number of duplicate leads collected in terms of first name, last name and email.
*It is recommended to make these fields mandatory in all projects tracking individuals. 



Registration Status Chart

The ‘Registrations status chart describes the state of the registrants that have been created within the date range selected. The slices of the pie represent the following possible states of registrations. 






Attended
- reflects the number of registered attendees that have attended their sessions. 
   i.e. their registration record has an associated attended time stamp, regardless of if they were marked attended through the  Limelight Check-in app or through the Limelight portal. 
In some cases, a record may be edited to be cancelled/waitlisted by a portal user after the registrant has attended, in this case, the registrant will still be counted as an attended registrant.

Waitlist
- reflects the registrants that have a status of ‘waitlisted’ in the database.
   i.e. they do not have an attended time stamp. This includes registrants who either:
   - signed up on the web for full sessions or
   - those registrants whose records were manually changed to "waitlisted" in the Limelight portal.
If auto-waitlist is turned on, these numbers will adjust as registrants cancel and slots open up.

Cancelled
- reflects registrants who have a status of "cancelled" in the database and do not have an associated attended time stamp.
In some cases their status has been manually changed to cancelled whereas in some cases, these are customers who initially signed up but decided to cancel afterwards.

No show
- reflects registrants who have registered for the event but do not have an attended time stamp and the session end date/time has passed. This number will only be calculated if sessions in the project are set with end dates/times.

Drill down
Each of the slices in the chart can be drilled down to reveal the registrant source. 

Registration History Chart
The Registration History chart shows an accumulative and non-accumulative graphical representation of the registration conversions, with special considerations that are applied due to the date filter applied. The chart shows the number of registrants events (registrations and attendance, and totals and uniques for both metrics)  that occurred, by day. Registrants displayed on this chart are only those created within the date range applied, if a registrant registers before the date range and attends within the date range, they will not be included in this chart. Additionally, for this chart, if the registrants that were created within the date range actually attended after the date range, they will not be counted. 

To gain more clarity increase the date range to to include the attendance dates

Note: For unique regstrations/attendees, If the same person registers/attends on day 1 and day 4 within the range, they will be shown as a unique registrant/attendee on day 1 and ignored on day 4.

Registration Source

This chart is a breakdown of registrant status from each source type. The three possible sources are:
- Web: These registrations were created from Limelight published micro-sites.
- Manual: These registrations were created through a manual upload (csv) on the Limelight portal.
- Walk-in: These registrations were created through the Limelight app


Other information:

Leads Generated
This chart shows the number of registrations created or leads captured on the Limelight app, grouped by the app user logged in at the time.

Photos Taken
This value displays the total number of photos taken within this project on the Limelight app, and which app form fields contributed to this total.

Waivers
This value displays the total number of waivers signed on the Limelight app, and which waiver form fields contributed to this total.

Guests
This value displays the total number of guests that registrants said they would be bringing to an event.
Note: This will not always be equal to the total number of expected guests. This is because the number is de-duped (non-uniques are ignored) on the person and the guest count. For example, if the same person creates 4 registrations declaring 2 guests, we assume they are bringing the same 2 guests to all 4 registrations. Resulting in a total of 2. However if a person has two separate registrations, one with 1 guest and one with 4, we assume 5 total guests are coming to the event. The number of guests per person is calculated by the total number of guests (de-duped) divided by the number of unique people registered for the event, and rounded to the nearest number.

Sessions AnalyticsSession analytics is available through the Sessions toggle.
It lists the sessions in the project, ordered based on session start date, with the default (project) session first. The data communicates how many total registrants are expected to arrive at a session, and how overbooked that session in terms of capacity. Additionally, the data also communicates the break down of the registrants; ‘2 out of the 11’ expected arrivals are guests.

The registered guests count is calculated based on the number of guests the registrants declared they are bringing at the time of registration. The guests count is calculated based on the ( +  - ) toggles of attended guests available on the Limelight check-in app.

Responses AnalyticsResponses analytics is available through the Responses toggle. This page list all fields that collect registrant or lead responses and what the total number was for each response option within the field. Currently, this page only  supports fields that are configured with enumerated options such as:

  • Dropdown
  • Radio button
  • Multiple checkbox
  • Slider
  • Toggle

If a field is not mandatory and an engagement decides not to answer it, the (blank) option will increment, meaning the user has no response for it. The (blank) will also be incremented if a csv of registrants are uploaded and their answer is not changed to any of the options available. Finally, if the engagement is updated either via the database or the Limelight app, and the field is changed to have no value, the engagement’s response will be counted as (blank). If their record is edited to any of the options, that option will increment, and (blank) will detract by one.

Still need help? How can we help? How can we help?