> ## 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 Platform Sync

> Connect your event platform so event details, registrations, and check-ins flow into Conversion automatically.

Connecting your event platform is what turns a field event into a running program. The platform owns the event's details, registrations arrive as members, check-ins move them to attended, and no-shows are worked out after the event ends.

## Supported platforms

| Platform   | How you connect it                                                                            | Guide                                                               |
| ---------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Cvent**  | Authorized in your browser by a Cvent planner with the administrator role.                    | [Cvent](/product-docs/campaigns/field-events/platform-sync/cvent)   |
| **Luma**   | An API key from your Luma calendar or organization.                                           | [Luma](/product-docs/campaigns/field-events/platform-sync/luma)     |
| **Splash** | A Client ID and Client Secret from your Splash Customer Success Manager, plus a Splash login. | [Splash](/product-docs/campaigns/field-events/platform-sync/splash) |

All three bring in event details, registrations, waitlists, check-ins, and cancellations. How quickly they arrive differs by platform and is covered in each guide.

## Connect a field event to an event

**Prerequisites:**

* The platform is connected to your workspace from **Settings > Integrations**.
* The event exists on the platform and isn't already connected to another Conversion field event.
* The field event's type maps the **Registered**, **Waitlisted**, **Attended**, and **No Show** meanings. The default types do. See [Status meanings](/product-docs/campaigns/field-events/members#status-meanings).

**Steps:**

1. Open the field event and go to the **Overview** tab.
2. In the **Integrations** section, click **Connect** on the event platform card.
3. Find the event. Events are listed newest first; search by title or narrow by date to find older ones.
4. Select it and click **Confirm and sync**.

Conversion pulls in the event's title, start and end times, format, venue, organizer, capacity, and registration details, and keeps them up to date from then on. Because the platform owns these details, they are locked in Conversion; change the event on the platform and click **Re-sync** to pull the change in immediately.

<Warning>
  A platform connection can't be changed or removed. Each platform event can be connected to one Conversion field event and vice versa. To start over, archive or delete the field event and create a new one.
</Warning>

## Registration

Registration flows one way, from the platform into Conversion. Each person who registers is matched to a contact by email address and moved to your registered status. If no matching contact exists, Conversion creates one with their name and email. Waitlisted registrations land on your waitlisted status, and registrations awaiting a host's approval land on your pending-approval status if the type maps one.

When the platform reports a registration as cancelled, declined, or removed, the member is removed from the event.

Moving a member to **Registered** in Conversion changes their status here and nothing else. Conversion does not register people onto Cvent, Luma, or Splash. Point your invitation email at the platform's registration page instead; the link is on the Overview tab as **Registration URL**.

<Info>
  Whether registrations arrive in real time or on an hourly sync depends on the platform. See its guide.
</Info>

## Attendance

Attendance is a check-in. When the platform records a member as checked in, they move to your attended status, and nothing the platform later reports about their registration moves them back.

After the event, Conversion derives the no-shows itself: 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, so allow up to seven hours after the end time for the last no-shows to appear. A late check-in still wins.

<Info>
  Connect the event **before it ends**. Attendance isn't backfilled for an event connected afterwards, and the no-show sweep only runs on connected events.
</Info>

## Event changes

Rescheduling, a new venue, or a change of title on the platform is picked up by the next sync or by **Re-sync**. On Luma these arrive in real time. If the platform reports the event as cancelled, Conversion archives the field event so it stops syncing; its members are kept.

## Troubleshooting

These apply to any platform. For platform-specific issues, see the troubleshooting section of your platform's guide.

| Problem                                                               | Likely cause                                                                                                                                                                                              |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No events to choose from                                              | No event platform is connected. Connect one from **Settings > Integrations**.                                                                                                                             |
| A specific event is missing                                           | It's already connected to another Conversion field event, it belongs to a different account than the one connected to your workspace, or it's further down the list than the first page. Search by title. |
| **Connect** is refused with a message about meanings                  | The field event's type doesn't map every required meaning. Fix the type in [Campaign Types](/product-docs/campaigns/settings/types) and try again.                                                        |
| Details look out of date                                              | Click **Re-sync** on the platform card.                                                                                                                                                                   |
| Someone registered on the platform but isn't in Conversion            | They registered without an email address, so there was nothing to match on, or the platform's sync hasn't run yet.                                                                                        |
| A member you moved to **Registered** isn't registered on the platform | Expected. Conversion doesn't write registrations to event platforms.                                                                                                                                      |