Skip to main content

Events dashboard

Analyze events, participation, costs, and learner interest in event proposals using dashboard metrics and raw data.

The Events dashboard provides a detailed overview and analysis of events and event proposals within your organization, as well as insights into how users interact with them. 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 the Metrics, Raw data: Events, and Raw data: Event proposals tabs. You can analyze event proposals as an aggregated overview or as user-level raw data.

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 events 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 three main tabs:

  • Metrics: Provides visualized KPIs, charts, a detailed event table, and an aggregated overview of event proposals.

  • Raw data: Events: Displays a comprehensive list of all users and their event-related data in a tabular format.

  • Raw data: Event proposals: Displays user-level records for event proposals, including interest-related statuses.

Dashboard filters

Filters vary by tab and apply to all data in the current view.

  • Metrics tab filters: Date, Team, Event title, Event status, Event type, Event language.

  • Raw data: Events tab filters: Date, Team, Title, Status, Format, Language, Category, User name, User event (proposal) status.

  • Raw data: Event proposals tab filters: Team, Title, Status, Format, Language, Category, User name, User event (proposal) status. No Date filter is displayed on this tab.

The User event (proposal) status filter corresponds to USER_EVENT_STATUS on Raw data: Events and USER_EVENT_PROPOSAL_STATUS on Raw data: Event proposals.

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

  • Events

  • Event proposals

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.

Breakdown charts by status, type and 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).

  • Booked future costs: Cost of booked 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 KPIs with Budget, Remaining budget forecast, and stacked bar for Costs by category and remaining budget forecast

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.

Costs by category and date chart aggregated by event start date (Week)

Note: For a cross‑activity view of budgets and costs across events and journeys, open Analytics → Budget and costs.

Events

The Events 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).

Format

Event format (Online, In-person, Hybrid).

Language

Language in which the event is conducted.

Link exists

Whether a link is present; distinct from the Link column, which opens the event detail page.

Location

Physical venue recorded for the event.

Category

Category information assigned to the event.

Trainer

Trainer of the event.

Min. participants

Configured minimum number of participants.

Max. participants

Configured maximum number of participants.

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).

Booked future costs (€)

Cost of booked but not‑yet completed training.

Requested costs (€)

Cost of requested but not‑yet approved training.

Link

The Details link opens the event detail page for further information.

Event proposals

The Event proposals section provides an aggregated overview, with each row representing one event proposal. Proposals with status Draft are excluded; proposals with status Archived can appear in this table.

Attribute

Description

Title

Title of the event proposal.

Status

Status of the event proposal.

Language

Language of the event proposal.

Format

Proposal format (Online, In-person, Hybrid).

Location

Location information, where available.

Category

Category information for the event proposal.

Trainer

Trainer information for the event proposal.

Interested

Number of interested learners.

Price (€)

Recorded price per participant.

Raw data: Events

The Raw data: Events 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:

Note: On the Raw data: Events tab, you can filter by User name and User event (proposal) status. User event (proposal) status corresponds to the USER_EVENT_STATUS column (for example, Attending, Withdrawn, AttendanceConfirmed, AbsenceConfirmed, RequestDeclined).

Column

Description

USER_NAME

Full name of the user (first and last name).

EMAIL

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).

FORMAT

Event format (Online, In-person, Hybrid).

LANGUAGE

Language of the event.

LOCATION

Physical venue recorded for the event.

CATEGORY

Category information assigned to the event.

TRAINER

Trainer of the event.

MINIMUM_PARTICIPANTS

Configured minimum number of participants.

MAXIMUM_PARTICIPANTS

Configured maximum number of participants.

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, AbsenceConfirmed (marked as not attended), RequestDeclined. Unlike Withdrawn, AbsenceConfirmed records non-attendance rather than a canceled registration. This status can also be set automatically following a late calendar decline.

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).

BOOKED_FUTURE_COSTS

Cost of booked 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.

Raw data table showing USER_NAME, EMAIL, TEAMS, TITLE, STARTS_AT, ENDS_AT, and duration columns.

Raw data: Event proposals

The Raw data: Event proposals tab contains the List of all users and their event proposals table. Each row is a user-level record for an event proposal rather than an aggregated proposal overview.

Note: STATUS describes the proposal itself, while USER_EVENT_PROPOSAL_STATUS describes the user's relationship to it, for example Interested or Removed. The table also includes Removed records, so it does not list only currently interested users. Use User event (proposal) status to filter by USER_EVENT_PROPOSAL_STATUS.

Column

Description

USER_NAME

Name of the user.

EMAIL

Email address of the user.

TEAMS

Team memberships of the user.

TITLE

Title of the event proposal.

STATUS

Status of the event proposal itself.

LANGUAGE

Language of the event proposal.

FORMAT

Proposal format (Online, In-person, Hybrid).

LOCATION

Location information, where available.

CATEGORY

Category information for the event proposal.

TRAINER

Trainer information for the event proposal.

PRICE_AMOUNT

Price amount for the event proposal.

PRICE_CURRENCY_CODE

Currency code for the price.

USER_EVENT_PROPOSAL_STATUS

Status of the user's relationship to the proposal, for example Interested or Removed.

INTEREST_SHOWN_AT

Date and time when interest was expressed.

CANCELED_AT

Date and time when interest was withdrawn, where recorded.

INTEREST_SHOWN_COMMENT

Comment associated with the expression of interest.

USER_ID

Unique identifier for the user.

EVENT_PROPOSAL_ID

Unique identifier for the event proposal.

Important considerations

  • Event metrics, costs, and event details exclude events with the status Draft or Canceled.

  • The Event proposals table on the Metrics tab excludes proposals with status Draft; proposals with status Archived can appear.

  • 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. Booked future 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.

Did this answer your question?