What is event analytics?

Event analytics is the measurement side of running an event. It is usually over-supplied and under-used: dashboards are full, and very little on them changes what anybody does.

In practice at an event

The distinction that matters is between behavioural numbers and volumetric ones. Behavioural numbers describe what attendees chose: which sessions filled, which questions got upvoted, how many people saved a personal agenda, who connected with whom. Volumetric numbers describe how much of something happened: app opens, notifications sent, sessions listed. The first kind changes a decision. The second rises when you do more of something.

Live analytics are a different instrument again. A number watched during the event — arrivals against the guest list, activation through the first morning — is actionable while somebody can still act. The same number in a post-event report is a lesson for next year.

What to look for

Ask which numbers are available during the event and which only afterwards. Ask what the denominator is for every percentage, and write it down, because a rate whose denominator changes between years has no trend.

And ask what the vendor does with the aggregate. Many products publish benchmark statistics derived from customer events, which may be entirely fine with you and is worth knowing rather than discovering.

How event67 handles it

Engagement analytics run live in the console during the event: active attendees, funnels and top sessions, plus a live arrivals count against the guest list for the check-in desk. Afterwards, an end-of-event report archives every Q&A, poll and photo. Deleted sessions and photos are excluded from what the analytics screens display, so a report never shows an organizer something they removed.