What event analytics tell a program committee

The Analytics tab answers the questions a program committee actually asks — how the call went, whether the files arrived, what delegates did — and hands the whole story over as a typeset report when the meeting is done.

Event managerBoard member

Analytics is readable by anyone with view access to the event — it exists precisely so a board member or committee chair can see the numbers without being handed an editing role. The tab is organized as sections, and a section only appears when the modules behind it have run: an event that never ran a call for abstracts simply has no Abstracts section, rather than a page of zeros.

What the sections show

Overview

The headline tiles — submissions, decisions, uploads, engagement — with the decision split and submissions-per-day charted. The place to look first, and often the only place a busy chair looks.

Abstracts

The full funnel: invitations sent and opened, submissions by status and type, review coverage, staged decisions, notifications, confirmations and program conversions, with time-to-decision and per-track scoring tables. Track scores are shown per track only — cross-track score comparisons are deliberately absent because they are not comparable.

Program & Uploads

Upload compliance against the effective deadline — on time, late, still missing — plus poster and paper file coverage.

Engagement

Attendee sign-ins, bookmarks, the most-bookmarked sessions, Open Mic activity by room and day, and gallery readership — poster views and, since papers gained view tracking, paper views, each with a most-viewed list.

Delivery, opens and clicks across your campaigns, invitations, decisions and automated mail — see the note below on what this needs.

Every panel exports its rows as CSV, and charts follow the venue's timezone and your light-or-dark theme.

Email engagement needs the delivery webhook

Rostrum always records what it sent. Whether a message was delivered, opened or clicked comes from the email provider's event webhook, and the panel says honestly when that is not configured — counts appear from the moment it is switched on, not retroactively. Chapter 18 covers the sending side.

The post-event report

Download report produces a typeset PDF of the whole story — the funnel, the program shape by day and track, uploads, engagement and email — built from the same numbers the panels show, so the report can never disagree with the screen. Sections appear only where the module ran, and a report generated before the event is marked Completed carries a caveat on its cover saying so. It is the artifact to put in front of a program committee.