Reporting & data
One attendance record across the door, sessions and hall.
Check-in, session scanning and lead capture all write to the same record against the same person. Questions that span all three are one query, answerable the same day and safe to put in a board pack.
Why it is different here
Ask questions that cross the door, the sessions and the floor.
A scan at a door, a session and a booth are the same kind of event, recorded in one place from one credential. These four questions are a single report:
Which sessions did the people who visited your top-tier sponsors actually attend?
What share of badge-holders never reached the exhibit floor at all?
Did the attendees a booth captured match the audience that booth was sold?
Which track kept people in the building until the last afternoon?
All seven admission outcomes are recorded, not only the admits. Refusals show you the oversubscribed sessions, the doors that opened late and the badges that were passed around.
The everyday reports
Pacing, funnel, revenue and attendance, every morning.
Pacing against last year
Registrations to date against the same point last year, updated daily. Open it every morning.
Registration funnel
By type, date, source and campaign — including the ones who started and did not finish.
Revenue
By ticket type, add-on and promo code, against a catalogue where a booth and a t-shirt are the same kind of thing.
Attendance
Check-in rate and per-session attendance, from the shared record rather than from an export somebody merged.
Exhibitor and sponsor performance
Leads captured, booth traffic and the audience each exhibitor actually reached. Send it with the renewal.
Cancellation and attrition
Plus demographics and geography, and cross-event comparison across your own series.
Saved views and CSV export on every report, because somebody always needs it in a spreadsheet for the board pack.
Data & API
Get your data out through the same API we run on.
The interface is a client of the same API you get. No screen reaches data through a private path.
Export anything without asking us. Build an integration without a services engagement. Run the full attendee experience in a browser without publishing an app.
The consequence worth stating
You can leave with everything.
Your data sits in your own database and the API reaches all of it. Take the database whole, or pull it through the API, whenever you want.
We would rather be kept than be hard to leave.
Architecture and isolation →What question about last year’s event can you not currently answer?
Send it over and we will run it against a demo dataset and show you the result.
hello@fieravents.com