Loading…
Record who attended each session — by badge scan or by name, on the web or in the app — and see the names, times and re-entries in one report.
In WebMobi, a check-in counts where the person checking people in says it counts: Whole event (the entrance) or a specific session, and either way the person counts once as Attended. Choose the session on the web Event Check-In page or with Scanning into in the app, then scan badges or check people in by name. The event's Check-in Analytics page then lists, for each session, how many people attended and who — with in and out times in the event's time zone — and exports it as a CSV file.
For choosing a session check-in approach for your event, see Session check-in and attendance.
| Rule | What it means for you |
|---|---|
| The target is always visible | The screen shows where the next scan counts — a session name or Whole event. What you see is what is recorded. |
| The target is chosen, never carried over | Opening the scanner starts at Whole event. The morning keynote is not silently carried into the afternoon. |
| A session check-in is attendance | Attended counts each person once, whether they were scanned at the entrance or into a session. |
| One visit at a time | A second check-in while someone is already inside the same session is recorded as a repeat and not counted. |
| Re-entry is a new visit | Out and back in again adds a visit to Check-ins, while the session and Attended still count one person. |
| Every scan is kept | Repeats and no-change scans are kept as evidence in History, even though they change no count. |
| A badge belongs to one event | A badge from another event is refused and records nothing. |
Works in any browser with a camera, or with a USB badge scanner. Needs a connection.
Works online and offline — the phone saves the session list along with the attendee list.
Open the event and choose Analytics (also in the Event Check-In page menu). The page is Check-in Analytics; under the title it says Times shown in … with the event's time zone. It shows live data and refreshes every minute; Refresh reloads now.
| Part of the page | What it shows |
|---|---|
| Registered | Confirmed registrations. |
| Attended | People with at least one check-in, at the entrance or into a session, each counted once. |
| Attendance rate | Attended as a share of Registered. |
| Check-ins | Every check-in, including re-entries and each session visit. |
| Check-in Trend (Last 24 Hours) | Check-ins per hour over the last day, at the entrance and in sessions. |
| Attended by ticket type | People who attended, per ticket type. |
| Session Attendance | Each session with N attendees — the number of people, not scans. Select a session to list every attendee with In and Out times. A person who re-entered appears once per visit. |
| Recent Check-ins | The latest 10 check-ins at the entrance. |
A session with nobody yet reads No attendees recorded for this session yet. Press Refresh if you just scanned. With no session check-ins at all, the card reads No session attendance data yet. and On the Check-In page, choose a session before scanning badges.
Export CSV downloads the report as one CSV file, fetched fresh at that moment. If the per-person list cannot be fetched, the export stops and says so rather than giving you a file with a section missing.
| Section of the file | Columns |
|---|---|
| Header | Event, exported time, Times shown in, Registered, Attended, Check-ins and Attendance rate. |
| Ticket Breakdown | Ticket Type, Total Registrations, Attended and Attendance rate, with “No ticket” for a registration without one. |
| Session Attendance | Session, Attendees, Check-ins (incl. re-entry). |
| Session Check-ins (who attended each session) | Session, Attendee Name, Checked In At, Checked Out At — one row per visit. |
| Recent Event Check-ins (latest 10) | Attendee Name, Ticket Type, Checked In At. |
Times in the file are written as YYYY-MM-DD HH:MM:SS with the time zone, 24-hour, so a spreadsheet cannot read a date two ways. More on every export: Exporting attendance, attendee lists and the agenda.
| What goes wrong | Prevention |
|---|---|
| A whole queue scanned into the wrong session, or into Whole event | Read the session name on the screen before the first scan and after every break. The app starts at Whole event each time the scanner opens. |
| A session door leaves people “checked out” | Use In only at doors unless you want leaving times. |
| Scanning into the wrong event | Read the event name and dates above the scanner, because the page warns when today is more than a day outside them. |
| Rehearsal check-ins in the real report | Practise on a separate event: a check-in cannot be removed. |
Yes: Attended counts each person once, whether they were scanned at the entrance or into a session.
Only if you want a record of who came through the door, because a session check-in counts as attended but is not an entrance check-in.
No: they count once in Attended and in the session, while each visit counts in Check-ins and in the export’s “Check-ins (incl. re-entry)” column.
Not as a single view. The report lists who attended each session. To follow one person, open History → Check-ins, which shows each of their check-ins with the session.
The event’s own time zone, named under the page title (“Times shown in …”) and in the exported file. If the event has no time zone, the page says “Times shown in your local time”.
The scans were probably made with “Whole event” selected. Only check-ins made with the session selected count toward it. A check-in cannot be moved to another session afterwards.
People with the View analytics permission on the event, plus the event creator and your organization’s owners and admins.
Yes. Scan in “In / Out” mode (a badge already inside is scanned out) or “Out only”. The report then shows an Out time next to the In time for that visit. Checking in by name is always an in.
Yes, in the mobile app. The phone saves the session list with the attendee list; offline check-ins keep their session and the time they were made, and count toward that session when the phone syncs.