The Events dashboard provides a detailed overview and analysis of all events created within your organization, as well as insights into how users interact with these events. This article explains every section, metric, and feature available in the dashboard, including the use of filters, the interpretation of key performance indicators (KPIs), and the structure of both the Metrics and Raw data tabs.
Who can use this feature?
Available for users with role Owner.
Learn more about roles and permissions here.Available on All Plans
Available on Desktop
Note: Dashboard data refreshes nightly. A badge next to the dashboard title shows when the data was last updated.
Accessing the journeys dashboard
In the main navigation on the left, click on Analytics. Then, click on Events to open the Events dashboard.
The Events dashboard is divided into two main tabs:
Metrics: Provides visualized KPIs, charts, and detailed event tables.
Raw data: Displays a comprehensive list of all users and their event-related data in a tabular format.
Dashboard filters
Six filters are available at the top of the dashboard. These filters apply to all data and visualizations in the current view:
Date filter: Select the time period for which you want to view data.
Team filter: Filter data by specific teams within your organization.
Title: Filter by the event title.
Status: Filter by the event status (e.g., Completed, In Progress).
Type: Filter by event type (e.g., Online, Offline, Hybrid).
Language: Filter by the language in which the event is conducted.
All active filters are considered in the data displayed and in any exports or downloads.
Metrics tab
The Metrics tab is organized into several sections, each providing different insights:
Overview
Cost
Details
Overview section
The Overview section displays six key performance indicators (KPIs) and several visualizations. Only events that do not have the status Draft or Canceled are included in these metrics.
KPI | Description |
Events | Number of events (excluding drafts and canceled events). |
Registrations | Number of users who have registered for events. Note that a user can be registered for multiple events. |
Attendances | Number of users whose attendance was confirmed after registration. |
Cancelled registrations | Number of registrations that were withdrawn or cancelled by users. |
Declined requests | Number of registration requests that were declined by team managers. |
Learning time | Total hours spent by users in events. For example, if there are five events with three attendees each, and each event lasts two hours, the learning time would be 30 hours (5 x 3 x 2). |
Below the KPIs, a bar chart visualizes the number of events, registrations, and attendances over time based on the event start date. Use the aggregation selector (e.g., Day, Week, Month, Quarter) in the top‑right to change the time grouping; the default is Week.
Three further charts break down the number of events by:
Status: Shows the distribution of events by their current status (e.g., Completed).
Type: Displays the number of events by type (Online, Offline, Hybrid).
Language: Illustrates the proportion of events conducted in each language.
Cost section
The Cost section provides insights into the financial impact of events. Only events that are not in Draft or Canceled status are included in the cost calculations.
Budget: Sum of the Annual budget defined for the teams in scope (based on the Team filter). Visible only if at least one team budget exists.
Remaining budget forecast: Budget minus all cost categories within the current filters (can be negative). Visible only if at least one team budget exists.
Incurred costs (attended): Cost for users whose attendance was confirmed.
Incurred costs (no attendance): Cost for active registrations that did not attend (no‑shows).
Approved costs: Cost of approved but not‑yet completed training.
Requested costs: Cost of requested but not‑yet approved training.
Costs by category and remaining budget forecast: Shows the four cost categories along with the remaining budget forecast for the filtered scope. Remaining budget forecast appears only when at least one team has an Annual budget.
Costs by category and date: A stacked chart shows the four cost categories over time, aggregated by the event start date. Use the aggregation selector (e.g., Week, Month, Quarter) to change the time grouping; the control works the same as in other charts.
Details section
The Details section contains a table listing all events that are not in Draft or Canceled status. Each row represents a single event and includes the following attributes:
Attribute | Description |
Title | Name of the event. |
Start | Start date and time of the event. |
End | End date and time of the event. |
Status | Current status of the event (e.g., Completed, In Progress). |
Type | Type of event (Online, Offline, Hybrid). |
Language | Language in which the event is conducted. |
Trainer | Trainer of the event. |
Registrations | Number of users registered for the event. |
Attendances | Number of registered users who attended the event (as marked in the sign-up list). |
Cancelled registrations | Number of registrations that were cancelled or withdrawn by users. |
Declined requests | Number of registration requests declined by team managers. |
Learning time in hours | Total time spent by users in the event. |
Price per registration | Price per registration for the event. |
Incurred costs (attended) | Cost for users whose attendance was confirmed. |
Incurred costs (no attendance) | Cost for active registrations that did not attend (no‑shows). |
Approved costs | Cost of approved but not‑yet completed training. |
Requested costs | Cost of requested but not‑yet approved training. |
Link | Direct link to the event detail page for further information. |
Raw data tab
The Raw data tab provides a detailed table listing all users and their associated events. Each row represents a unique user–event relationship and includes the following columns:
Column | Description |
USER_NAME | Full name of the user (first and last name). |
Email address of the user. | |
TEAMS | Comma-separated list of all team names the user belongs to. |
TITLE | Title of the event. |
STARTS_AT | Start date and time of the event. |
ENDS_AT | End date and time of the event. |
DURATION_IN_HOURS | Event duration in hours (decimal values possible). |
DURATION_IN_MINUTES | Event duration in minutes. |
STATUS | Current status of the event (e.g., Completed, In Progress). |
TYPE | Type of event (Online, Offline, Hybrid). |
LANGUAGE | Language of the event. |
PRICE_AMOUNT | Price per registration for the event. |
PRICE_CURRENCY_CODE | Currency code for the event price (e.g., EUR). |
USER_EVENT_STATUS | Status of the user with respect to the event. Possible values include: Attending, Withdrawn, AttendanceConfirmed, RequestDeclined. |
INCURRED_COSTS_ATTENDED | Cost incurred for a user whose attendance was confirmed. |
INCURRED_COSTS_NO_ATTENDANCE | Cost incurred for a user who did not attend (no‑show). |
APPROVED_COSTS | Cost of approved but not‑yet completed training. |
REQUESTED_COSTS | Cost of requested but not‑yet approved training. |
EVENT_ID | Unique identifier for the event. |
USER_ID | Unique identifier for the user. |
Important considerations
All metrics, costs, and details exclude events with the status Draft or Canceled.
Only event costs are considered; learning paths and journeys are excluded because they do not have a price attribute.
Incurred costs reflect completed attendance vs. no‑show costs. Approved and Requested represent pipeline stages before completion. Cancelled registrations and declined requests are not included in incurred costs.
Budget and Remaining budget forecast appear only when at least one team budget is set. They aggregate according to the current Team filter and date scope, and the remaining budget forecast can be negative.
Attendance numbers reflect only those users who have been marked as attended in the sign-up list.