> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Field Event Members

> Add contacts to a field event, map your statuses to the meanings integrations write, and see how registrations, check-ins, and no-shows land.

Field event members work like any other [campaign member](/product-docs/campaigns/members): they appear on the contact record, in audiences, and in your reporting. This page covers what's specific to field events, namely your own statuses, the meanings behind them, and how a connected platform moves people through them.

## Member statuses

A field event's statuses come from its [field event type](/product-docs/campaigns/settings/types). The defaults are **Invited → Waitlisted → Registered → Attended → No Show**, with **Tradeshow** adding **Visited Booth** and **Engaged Post Show**. You can rename these, reorder them, add your own, or mark different ones as [success statuses](/product-docs/campaigns/members#success-statuses).

New members start at the type's first status.

## Status meanings

Because you can name statuses anything, Conversion needs to know which of them a platform should write to. Each status on a field event type can carry one **meaning**:

| Meaning              | A platform writes it when                                                                                 |
| -------------------- | --------------------------------------------------------------------------------------------------------- |
| **Registered**       | The person has a confirmed registration.                                                                  |
| **Waitlisted**       | The person is on the waitlist.                                                                            |
| **Attended**         | The person was checked in.                                                                                |
| **No Show**          | The person registered but was never checked in. Derived by Conversion after the event ends.               |
| **Pending Approval** | The registration is waiting on a host's approval. Optional. Only needed for events that require approval. |

A meaning belongs to one status at a time. The four required meanings must be mapped before an event of that type can be connected to a platform; connecting is refused otherwise, naming the missing ones.

Statuses without a meaning, such as **Invited**, **VIP**, or **Visited Booth**, are yours alone. A platform never moves anyone onto or off them.

<Tip>
  Renaming a status doesn't break the sync. Integrations write to the meaning, not the name, so **Attended** can become **Checked In** without changing anything else.
</Tip>

## How a platform moves members

Once the event is [connected to Cvent, Luma, or Splash](/product-docs/campaigns/field-events/platform-sync/overview), Conversion applies each platform update with a few rules so the platform and your team don't fight over a member:

* **Attendance wins.** A check-in moves a member to your attended status from any registration state, and nothing the platform later reports about their registration moves them back.
* **Registration states move freely among themselves.** Registered, Waitlisted, and Pending Approval replace one another as the platform reports them, so someone bumped from Registered back to the waitlist shows that.
* **Your unmapped statuses are never overwritten.** A member you moved to **VIP** stays there no matter what the platform reports. The starting status is the exception: someone still on **Invited** is promoted when they register.
* **Cancellations remove the member.** When the platform reports a registration as cancelled or declined, the member is removed from the event. Their contact record is untouched.

Each platform's guide lists exactly which of its statuses map to which meaning.

## No-shows

No platform reports a no-show, so Conversion derives it. Six hours after the event's **End Time**, members still on your registered status are moved to your no-show status. The sweep runs hourly, and a late check-in still wins: a member checked in after the sweep moves to attended.

## Add contacts

**Prerequisites:** The contacts already exist in Conversion.

1. Open the event's **Members** tab and click **Add members**.
2. Search or filter to find the people you want. Anyone already on this event is excluded from the list.
3. Optionally choose the status they should enter at. Otherwise they start at the type's first status.
4. Select the contacts and click **Add**.

Adding someone to a field event does not register them on your event platform. Registration flows in one direction, from the platform to Conversion. Send people to the platform's registration page to register.

Contacts who register on the platform are added for you. They are matched to an existing contact by email address, and a new contact is created when there is no match.

Updating and removing members otherwise works as it does on any campaign. See [Campaign Members](/product-docs/campaigns/members#updating-and-removing-members). Any move you make by hand stands, including moving someone backwards.

## Registration and attendance numbers

The **Members** section of the Overview tab summarizes the event:

|                     |                                                                            |
| ------------------- | -------------------------------------------------------------------------- |
| **Members**         | Everyone on the event.                                                     |
| **Registrations**   | Everyone who registered, including those who went on to attend or no-show. |
| **Attendees**       | Everyone who was checked in.                                               |
| **Attendance rate** | Attendees divided by registrations.                                        |

A breakdown underneath shows the count and share for each status.