Event registration analytics
The event registration analytics page shows a high level overview of registration performance for your live event. To access the registration analytics page, head into “Event Analytics” and click into the “Registration” tab.
Here, you can see the number of impressions, registrations, and the registration rate. You can also filter registration analytics by day or by week.
The impressions data point shows the number of times a visitor viewed the registration page.
Registrations is the number of visitors who submitted the registration form.
The registration rate is based on the number of visitors who ended up registering, out of the number of visitors. For example, if there were 100 visitors and 80 of those visitors registered, the event would have an 80% registration rate.
Organizations
The organizations section of event registration analytics shows which organizations have registered for the event. These shows in order of most to least.
For more information about the registrants from a specific company, click the logo tile. This brings up the table on the registrants page, which is filtered to show registrants from that organization. For more information about data on the registrants page, head on over here.
Note
Referral Analytics and UTMs
The Referral widget displays the previous webpage viewers were on before accessing the website with the registration form.
For each referrer, the widget showcases Referral URL, Impressions, Registrations, and Attendees. You can sort the columns as desired.
UTM Parameter Analytics
UTM analytics are accessible if you append UTM parameters to your registration URL. UTM codes are text snippets affixed to a URL’s end for tracking campaign metrics.
If you input UTM parameters for Campaign, Source, and Medium, we will display Impressions, Registrations, and Attendee analytics in each of the corresponding widgets.
UTM Campaign
A UTM campaign is typically a name to identify which campaign the media is associated with, such as “Thanksgiving Sale.” For example:
www.example.com/videoABC?utm_campaign=thanksgiving+sale
UTM Source
In this context, “Source” refers to a traffic origin. By using UTM parameters for traffic sources, you can monitor traffic origins. The parameter to add to the URL is utm_source.
Examples of traffic sources include Facebook, Google, Bing, or email list names. The UTM Source should represent the primary traffic source, such as Facebook, rather than granular details like a specific Facebook post. For example:
www.example.com/VideoABC?utm_source=facebook
UTM Medium
Adding UTM Medium parameters allows you to track how viewers discover the page with your embedded media. This covers various channels like social media, affiliates, organic search, paid ads, newsletters, and email. For example:
www.example.com/VideoABC?utm_medium=email
Event registration analytics FAQs
Why isn't a logo showing up for an organization?
We match logos using domain data from registrant email addresses. If we can't fetch the data, and fallback methods don't retrieve it, we display initials based on the first two letters of the company’s domain name.
Will organization logos show retroactively for all of my live events?
Organization logos will display for events created on or after January 23rd, 2025.
Can I download event registration analytics?
Event registration analytics do not have a download option at this time.
Does this work for on-demand attendees too?
No, registration analytics are available from the event publish date until event completion.
What happens if I don't like the logo shown for my company?
We use a third-party service called Brandfetch to display logos. If a logo is incorrect or outdated, you can submit a logo update request directly through Brandfetch via their official logo updating process, or by submitting a support ticket. Once the update is approved on their end, it will automatically reflect in our product.
Why don't I see an attendee column for referral analytics and UTMs?
The attendee column is available for events that started on March 7th, 2024 or later.