People and identity
Duplicates are the most expensive mistake in event data: two records for one person means two badges, a split meeting history and a directory that lists them twice. Moostoo is built so that a person is recognised by their email address wherever they appear. Knowing how that works tells you why an import matched someone, why changing an address needs care, and why a team member also shows up on the attendee list.
Three records, one person
| Record | Scope | What it holds | Who edits it |
|---|---|---|---|
| User | The whole platform | The person's sign-in: their email addresses, password or sign-in provider, and which organizations they belong to. | The person themselves. |
| Contact | Your organization | Your organization's own record of them: name, email, phone, company and title. Listed in the Contact Directory. | You and your team. |
| Attendee | One event | Their participation: attendee type, ticket, registration and profile answers, agenda, meetings, badge code and check-in. | You, and the attendee through their profile. |
When you add somebody to an event — by hand, by import, through registration or a ticketing platform — Moostoo looks the email address up. An address it knows is linked to the existing person and contact; an unknown one creates them. A user record can exist for somebody who has never signed in: it is simply the anchor that lets the next event recognise them.
The email address is the key
- Addresses are case-insensitive.
Jamie.Chen@…andjamie.chen@…are the same person, everywhere — imports, sign-in and search alike. - An address with a space inside is refused, because it cannot be anybody's address.
- Imports never rewrite an attendee's email. Once somebody has signed up, their address is how they sign in; an import identifies people by it (or by ticket id first, for ticketing imports) and does not overwrite it.
- One person may have several addresses. A person's account can hold more than one verified address, which is how a work and a personal address resolve to one attendee.
Once someone has signed up, their address is their login
You can still edit a signed-up attendee's details, but changing their email changes the address they sign in with — so the edit dialog asks you to confirm it first. Imports and ticketing syncs never change it for you.
Team members are participants too
Everyone on an event's team is also a participant of that event: they appear on the attendee list, can be messaged and met, get a badge and have an agenda. You do not add your staff twice — adding someone to the event team seats them on the roster automatically, and removing them from your organization takes them off every event's roster.
Registered, invited and signed up
Invited You (or an import) added the person; they have not registered themselves yet. An automated invitation email can go out when they are added.
Registered The person is in: they registered, were approved from an application, bought a ticket, or entered the event in the app.
Checked in A separate yes/no, set at the door or kiosk. Checking in never changes whether someone is registered.
Signed up The person has an account and has signed in at least once.
Contacts are yours, profiles are theirs
A contact is your organization's record and is not changed behind your back: a ticketing re-import refreshes the attendee's ticket data, never your contact. What an attendee writes in their event profile — job title, company, bio, offers and seeks — belongs to that event's attendee record, so the same person can describe themselves differently at a trade show and at a conference.
Read next