What is session attendance?

Session attendance is how many people were in the room. As a raw number it means little; against the room’s capacity it becomes the most useful programme evidence a conference collects.

In practice at an event

Attendance is behaviour, and behaviour is more honest than a survey answer. An attendee who says the security track was valuable and spent the day in the product track has told you two things, and the second is truer.

The pattern to look for is a track that runs at forty percent of capacity all day. That is a track to shrink, reposition or re-title, and it is invisible in aggregate satisfaction scores.

The practical difficulty is measurement. Counting people at a door needs staff at every door, which most conferences do not fund. The usable proxy is the personal agenda: the number of attendees who saved a session, available a week out, predicts the room better than registration does and arrives early enough to swap rooms.

What to look for

Ask what a product actually measures. Saved-agenda counts, check-in scans and self-reported attendance are three different things and should not be presented as one.

Read attendance next to session ratings. A full room with a low rating and an empty room with a high one are both useful and mean opposite things.

How event67 handles it

The console reports top sessions and engagement funnels live during the event, and personal agenda counts are visible before it, which is what makes a room swap possible while there is still time. There is no per-session badge scanning, so attendance figures are derived from app behaviour rather than from door counts, and that distinction is worth stating in any report you build from them.