Happenee lets you download data from an event in eight different exports, each one built for a different job — accounting, GDPR audit, scanning analysis, catering rosters, CRM onboarding. Most exports are Excel; some are also CSV. You will find them in the Statistics section and in the detail pages of individual modules (Orders, Registration form, Attendee app). Articles about each module describe what their export contains; this article serves as a switchboard: which export to download when.
Decide what you need the data for:
Accounting and invoicing — Orders, Ticket statistics. You are most likely working with someone used to Excel.
Hotel, catering, organizing team — attendees export (filtered by group, accommodation). One export usually does the job.
GDPR audit or a request about a specific person — the export of consents beyond legitimate interest.
Check-in evaluation — the scanning export.
Form responses for analysis — the Registration form export (Excel or CSV for scripted processing).
App evaluation — the user activity export and the list of users who have the app.
A single file with every contact assigned to the event. It contains contact fields, attendee status, groups, preferred language, and the ticket (if the event is paid).
Typical uses:
Source data for catering, the hotel, or the organizing team.
Building badges if you do not print directly from Happenee.
A quick check of who is in which group.
For preparing data for the hotel, Happenee offers a limited export — see Preparing data for accommodation providers.
A separate export for the consents the organizer added on top of the baseline GDPR (marketing consent, photo consent, consent to share data with a partner, and so on).
Typical uses:
Audit — proving who agreed to what and when.
Source data when an attendee requests deletion or a data overview.
One row per QR code scan in the Service app or in Check-in.
Typical uses:
Evaluating arrival timing (how many people came at which hour).
Checking whether anyone passed through more than once (duplicate scans).
Linking a check-in to a specific scanning action (Check-in, One-time check for a voucher, and so on).
For an explanation of place types, see How check-in and QR-code scanning work.
A complete list of every order on a paid event — who, how much, what payment method, whether it is paid.
Typical uses:
Source data for accounting (an alternative to individual invoices).
Checking which orders are still waiting for payment.
The detail of a single order is described in Managing Orders and invoices. The export is the bulk view.
Aggregate numbers — sold, paid, unpaid, free, cancelled, broken down by month and by ticket type.
Typical uses:
Financial reporting for the event (how much was collected, how much is still pending).
Evaluating sales waves (when each ticket type sold).
The detailed explanation of ticket statistics is in Setting up Tickets.
One row per registered attendee, with every answer from the form. It includes contact details and additional questions.
Two variants:
Excel — for people who will work with the data by hand (filtering, pivot tables).
CSV — for import into another system (CRM, analytics, data pipeline).
In addition, you can edit responses directly in the attendee detail in the UI (for example, when someone made a typo in their address).
An export of each attendee's activity in the app — which sections of the app they opened and when they were last active.
Typical uses:
Evaluating engagement (an internal corporate event and a client conference have different benchmarks).
Source data for deciding whether to push more content into the app, or to turn the app off entirely for the next event.
Only who downloaded the app and signed in for this specific event. A smaller subset, but an important one.
Typical uses:
Before the event — who to send a push notification to versus who to send an e-mail.
After the event — who actually used the app (combined with the activity export).
An automated export for the hotel — missing. You assemble the data by hand from the All attendees export and the form responses. A dedicated automated export for accommodation providers is not yet a Happenee feature; today this is a manual workaround. See Preparing data for accommodation providers.
E-mail campaign send-out reporting — lives in the detail of the campaign, not in a central export. A dedicated reporting view for e-mail campaign performance beyond raw counts (opens, clicks per segment, time-series of engagement) is not available today. See Creating and sending an E-mail campaign.
An interpretive layer — Happenee exports are raw data. When a registration curve is healthy, when too little is happening — the organizer evaluates that themselves or with help from customer success. More graphs and statistics inside the admin are planned, but for deeper interpretation today you work with the raw export.
Exports are a snapshot taken at the moment of download. If you are looking at the current state, download again. Put the date in the file name (attendees_2026-04-19.xlsx) — otherwise after two downloads you will not know which one is the latest.
Use a saved view in the Registration section instead (filter, save the view, share). Your colleague works with live data and you do not need to export again.
A single Orders (Excel) export covers all of them. Pull individual PDF invoices only as attachments.
The scanning export has one row per scan, not one row per attendee. Anyone who passed through more than once (for example, Check-in plus One-time check) appears in the export multiple times. For a simple list of who arrived, use the attendees export filtered by the Checked-in status.
