Event analytics and reporting.RSVPs, no-shows and attendance, live.
Event analytics in AirLST comes from your guest list, not from a head count afterwards: RSVPs, declines, email delivery, attendance and no-show rate by guest group, live on the dashboard during the event and as a report after it. Measuring an event becomes a matter of looking, not recounting.
Reporting nobody has to stitch together.
Invitation, registration, check-in and survey write to the same guest; the analytics read from it.
RSVPs before the event, attendance on the day, no-shows the moment they happen.
Attendee statistics by guest group, entrance, workshop and time period.
Export to Excel or CSV, data through the API, contacts on to the event CRM.
Who said yes? And who actually got the invitation?
Attendee analytics starts with the send: delivery rate, opens and clicks per template tell you whether the invitation lands. RSVPs, declines and open replies flow into the dashboard live; anyone who has not replied by the deadline is a filter for a reminder, not a mass email.
- Delivery rate per templateDelivered, opened, clicked, bounced; for each guest, whether their invitation arrived.
- Live RSVP trackingConfirmed, pending, declined and waitlist, with a trend line since the send.
- CapacityUtilization per guest group and workshop round, waitlist as a number.
Attendance and no-show rate while doors are open.
Every scan in the check-in app is a data point. The dashboard shows expected, checked-in and missing guests by guest group and station, with a trend over time. Catering knows how many people are in the room; the project lead sees whether the north entrance is backing up.
| Guest group | Confirmed | Checked in |
|---|---|---|
| Attendees | 318 | 309 |
| VIP | 64 | 61 |
| Workshop A | 40 | 36 |
| Press | 6 | 6 |
The statistics tab of the check-in app shows the same numbers to the team at the door.
Guests who do not show up free capacity for the waitlist, walk-ins and the seating chart.
Time and station per guest, for compliance, hospitality records and certificates of attendance.
| Name | RSVP | Survey |
|---|---|---|
| JWJames Walker | Sep 3 | – |
| LHLaura Hayes | Sep 5 | – |
| EBEthan Brown | Sep 9 | – |
Event reporting: every number is a list you can act on.
The no-show rate is not a figure in a report, it is 16 guests in the list you can email. Attendance per workshop tells you which room was too small. The survey tells you how the people who came liked it. And the export takes everything to finance, your CRM and your agency.
- Filters, not reportsEvery metric is a selection in the guest list: follow-up, thank-you, a reminder for next time.
- Feedback per guestAnalyze answers from the post-event survey by group, attendance and program choice; question catalog in the event feedback form template.
- Export and APIExcel or CSV per selection; external systems pull the data through the API.
- Across eventsContacts and their history in the event CRM; compare several events side by side in one view.
Four numbers every event should answer.
Events have long been considered hard to measure. With a guest list that knows invitation, registration, check-in and feedback, four metrics are there without extra work: who was reached, who said yes, who came and how it went. They turn into planning decisions on format, channel, room size and budget.
The numbers come from what happens anyway: send, RSVP, scan, answer.
VIP, attendees, press, Workshop A: the same four numbers for every segment.
What a good no-show rate looks like and how to lower it is the topic of an upcoming guide in our resources.
Analytics on individual guests needs rules. They are already in place.
Event analytics shows numbers per group; looking at an individual guest requires permission. Roles and permissions of the guest list apply to reporting as well; opens and clicks are only tracked with consent; exports are logged.
- Hosted in GermanyGuest and analytics data on servers in Germany.
- GDPR compliantConsent per guest, data processing agreement and deletion policy in the Trust Center.
- TISAX-assessedTISAX is the information security assessment standard of the automotive industry; AirLST has been assessed against it.
Example roles. You assign permissions per user.
The analytics are your guest list, counted.
Send, RSVP, scan and answer are all stored on the guest. Reporting reads them without anyone exporting, merging or recounting.
Event CRMContacts across all events
Guest List ManagementOne source of truth for the whole team
Event Website BuilderLanding pages without code
Invitation EmailsDigital invitations in your brand design
Event RegistrationForms, RSVPs, plus-ones
Event TicketingTamper-proof QR tickets
Seating ChartsTables and seats from the guest list
Workflow AutomationAutomate workflows
Event AppAgenda and ticket on the phone
Event Check-inScan instead of search at the door
Access ManagementCheck-in, badges, gates: the whole entrance
Name BadgesPrinted on arrival
Lead RetrievalScan leads at the booth
Event SurveysPost-event feedback- You are here
Reporting & AnalyticsAttendance, no-shows, reporting 
API & IntegrationsConnect CRM and IT
AI integration (MCP)Connect Claude, ChatGPT or Copilot
For attendance per room and certificates of attendance, see the training management software; for attendance per day and session, conference management; for consistent metrics across many events, the event management software.
What is event analytics?
Event analytics is the set of metrics that describes an event through its attendees: how many people were invited and how many received the invitation, how many RSVPed yes, declined or never replied, how many showed up and how many did not, the no-show rate, and how attendees rated the event. Event reporting turns those numbers into decisions: which channel drives RSVPs, which format works, how big the room has to be, where the budget should go.
In AirLST, event analytics comes from the guest list, because invitations, RSVPs, check-in and surveys write to the same record. The dashboard shows total, confirmed, pending and declined guests, the email delivery rate and the no-show rate from confirmed and checked-in guests, live during the event; attendee statistics by guest group, station and time period come from filters on the list, and the export comes from the same selection. That makes events as measurable as any other marketing channel.
Analytics is not a report someone writes. It is the guest list, counted.
How does reporting work in AirLST?
- Send. Delivery rate, opens, clicks and bounced addresses per template; for each guest, whether the invitation arrived.
- Replies. RSVPs, declines, open replies and waitlist on the dashboard, with a trend since the send; reminders to the people still missing.
- Event day. Every scan counts: checked in, expected, no-shows, walk-ins, by station and group, on the dashboard and in the check-in app.
- After. Attendance and no-show rate by guest group and workshop; no-shows as a selection for follow-up; survey feedback per guest.
- Share. Export to Excel or CSV, data through the API into CRM and BI, contacts with their history in the event CRM.
How is event analytics different from a spreadsheet?
A spreadsheet report is built after the event: the send list, the replies, the door list and the survey export get merged, names matched, check marks counted. It takes time, it is error-prone, and it arrives too late to change anything during the event. It also says little about the individual guest, because each list spells them differently.
In AirLST there is nothing to merge, because everything sits on the same guest.
That is why the no-show rate is live, why no-shows are a selection you can email, and why feedback can be combined with group and attendance. The difference is not the dashboard, it is the data source: a guest list that knows invitation, registration, check-in and survey is the analytics. Everything else is how you display it.
What does event reporting work with?
With invitation emails for delivery rate and opens, event registration for RSVPs and capacity, the check-in app for attendance and no-shows, the post-event survey for feedback, the event CRM for history across events and the API for CRM and BI.
- Training management software: attendance rate per date and round, certificates
- Conference management: attendance per day and session
- Event management software: consistent metrics across many events