Which columns does the platform read?
The platform looks for headers in the first row and accepts common English labels such as name, full name, email, e-mail, phone and mobile, as well as the usual Arabic labels for name, email and mobile. With no header row it treats the first column as the name and the second as the email. Saudi mobile numbers are normalised to one format automatically, so there is no need to clean them by hand.
What happens to duplicate or incomplete rows?
A row whose email is already registered for the same conference is skipped rather than duplicated, as is a row without a valid name. Rows with a name but no email are imported but cannot receive an emailed ticket; the registration team can print their badge from the platform instead. The result screen shows how many rows were skipped so you can check the source file.
When should you import rather than open public registration?
Import works when the list is known in advance: official invitees, chamber members, staff of an entity or delegations registered with the host. An open conference only needs the public registration link and its QR code. Many conferences combine both, with an imported list for VIP guests and delegations and open registration for everyone else; the source column tells them apart in exports.
How do you export the list after the event?
The platform exports attendees, check-ins, survey results and quote requests as CSV files encoded so Excel shows Arabic correctly. The attendee file includes name, email, phone, organisation, job title, registration source, join time, ticket code and attendance status and time, so the list returns to Excel richer than it left.
What should you keep in mind about data privacy?
An imported list is personal data: upload it only for people who agreed to share it, and remove columns you do not need first. The platform can export or erase one person's data on request and applies a retention period after the event, and public screens never show a name.
Which mistakes come up most in import files?
- First and family names in separate columns, so the platform reads only the first name; merge them into one column before uploading.
- Merged cells or several header rows at the top, so the second header is read as a name.
- Emails with spaces or a comma instead of a dot, so the row imports without an email and no ticket is sent.
- A CSV saved in an old encoding that garbles Arabic; save as UTF-8 or upload the Excel file directly.
A quick check of these points before uploading saves the registration team hours of manual fixes in the final days before the conference.





Scan to chat on WhatsApp