Numbers you can act on before the event ends
Event analytics in event67 show active attendees, engagement funnels and the sessions people actually opened, live rather than in a post-event export. The design constraint is stated up front: the platform records that an action happened and never the text inside it.
What this looks like in the product
The numbers an organizer is asked for at lunchtime on day one, in one place.
- Live engagement
- Active attendees and activity while the event is running, not a week later.
- Funnels
- Invited, activated and engaged, so the drop-off is visible at the step it happens.
- Top sessions
- View counts per session, which is also what makes sponsor reporting possible.
- Arrivals
- Door check-ins against the invited list, on the console and as a widget.
- End-of-event report
- An archive of every Q&A question, poll result and photo when the event closes.
The engagement page
- Active attendees right now
- Invited, activated, engaged
- Top sessions by views
- Arrivals against the guest list
- Feedback and Q&A volume
Analytics after an event are history; during it, they are a decision
Most event reporting arrives too late to change anything. The deck lands ten days afterwards, everyone agrees the breakout track underperformed, and nobody can do anything about it until next year.
Measuring live changes what the numbers are for. If activation is flat by the afternoon of day one, the fix is a reminder email that evening, and it works. If a breakout is drawing four times the views of its neighbours, the repeat session goes in the bigger room. If arrivals are running two hundred behind the invited list at nine o'clock, the keynote holds for ten minutes.
So the funnel is the shape that matters more than any single number: invited, then activated, then engaged. Each step is a different problem with a different fix, and knowing which one you are losing people at is worth considerably more than an overall percentage.
What is actually measured
- Activation
- An attendee who claimed their invite and opened the app. This is also the billing meter, which means the number you are charged on is a number you can watch, not one you receive in an invoice.
- Engagement
- Screens viewed, features used, sessions opened, QR scans, connections made, photos added, scroll depth. All of it action metadata.
- Top sessions
- View counts per session, which drive both programme decisions and the number a sponsor gets reported.
- Arrivals
- Door check-ins against the invited list, for the desk and as a console widget.
- The archive
- When the event ends, the Reports page holds every Q&A question, poll result and photo.
The line the telemetry does not cross
This is worth reading before a procurement or works-council conversation, because it is unusually specific for a category that is usually vague about it.
event67's own telemetry records the fact and type of an action, never the text inside it. It knows a question was asked; it does not put the question into analytics. It knows a search happened; it does not record the search terms. It knows a message was sent in the admin chat; the content of that message is not analytics data. Nothing is sold, nothing is shared for advertising, and there is no cross-app tracking.
The honest counterpart: this is telemetry linked to an account, not anonymous. Organizers see aggregate engagement for their event; the individual record exists and is described plainly in the privacy policy rather than hidden behind the word anonymised.
- Recorded: which screens, which features, which sessions, how far someone scrolled.
- Not recorded: the content of messages, questions, chat or search terms.
- Not done: selling data, sharing for advertising, or tracking across unaffiliated apps and sites.
The three numbers to watch, in order
An engagement page shows more than anybody can act on at eleven o'clock on the morning of day one. In practice three numbers matter, and they matter in a fixed order because each one is meaningless until the one before it is healthy.
Activation, from the day invites go out
The share of your invited list who claimed and opened. If this is low a week before the event, the cause is almost always the invite email rather than the app, and the fix is a resend with a clearer subject line. Watching it late is watching it too late.
Arrivals, on the morning
Door check-ins against the invited list. This is the number the person running the room needs at 08:55 to decide whether the keynote starts on time, and it is the only one on this list that is worth interrupting somebody for.
Session views, from the first break onwards
Which sessions people are actually opening. A breakout drawing four times its neighbours is a repeat in a bigger room, and it is also the number a sponsor attached to that session should be given afterwards.
Everything else on the page is worth reading in the wash-up rather than during the event. The discipline is not about what is measured; it is about deciding in advance which two or three numbers will change a decision, and ignoring the rest until the event is over.
What the analytics will not do
- No custom dashboards, no query builder and no metric you define yourself.
- No data warehouse export, no BI connector and no analytics API.
- No cross-event benchmarking against other organizations.
- No attribution or ROI modelling, because there is no ticket revenue in the system to attribute to.
- No individual attendee behaviour report handed to sponsors.
Who reads these numbers
The organizer running the day, who needs arrivals and activation. The programme committee, who need session views to decide next year. The internal sponsor of the budget, who asks one question — did people use it — and deserves a specific answer.
And, quietly, finance: because activation is the billing meter, the console shows what the event will cost as it accrues, rather than presenting it as a surprise afterwards.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
When can we see the numbers?
During the event. Active attendees, funnels, top sessions and arrivals update live, which is the point: a number that arrives ten days later is history, and a number that arrives at lunchtime on day one is a decision about the afternoon.
Does event67 record what attendees type?
No. The telemetry records the fact and type of an action and never the text inside it. Questions, chat messages and search terms are not analytics data. The full detail is in the privacy policy, which is deliberately specific about this rather than relying on the word anonymised.
Can we export the data into our own BI tool?
No. There is no analytics API, no warehouse export and no BI connector. What you get is the console during the event and the end-of-event archive of Q&A, polls and photos afterwards.
Can sponsors see analytics?
Not directly. Engagement analytics belong to the organizer. What you can report to a sponsor is the view count on the sessions they supported, which is a real number and usually the one they actually wanted.
Is the billing number the same as the analytics number?
Yes, and that is deliberate. Activated attendees drive both, so the meter you are charged on is visible in the console from the day the event is published. Billing runs 48 hours after the event ends and the amount is emailed before any card is charged.
Keep reading
What is being measured
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.