> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/host/how-registrants-flow-into-mobly.md).

# How registrants flow from Host into Mobly

When someone fills out your Host registration form, they automatically appear as a **lead in Mobly** — no upload, no manual sync, no extra step. This is the core integration: your registration page and your lead database stay in lockstep without you doing anything.

## What triggers the sync

The moment a guest submits the registration form on your Host event page, Mobly:

1. Creates a lead in your Mobly org (or updates an existing one — see [Deduplication](#deduplication) below)
2. Adds that lead to the matching Mobly event with **Registered** status
3. Logs a registration activity on the lead's timeline

The handoff happens in seconds. By the time the guest sees the "Thanks for registering!" confirmation page, the lead is already in Mobly.

## What fields come across

From the standard Host registration form:

* **First name**
* **Last name**
* **Email**
* **Company name** (if your form collects it)

Custom fields you add to the form (job title, dietary restrictions, etc.) are captured in Host but not currently mapped onto the Mobly lead. Most teams handle this by viewing custom-field data in Host's registration export, then enriching the Mobly lead manually for VIPs.

## Where the lead lands

Open the corresponding event in the Hub and go to the **Leads** tab:

* The new registrant appears in the lead table
* Status column shows **Registered**
* Source on the lead's activity timeline shows the registration event

If you're using the Mobly mobile app at the event, the same registrant appears under that event in the app — ready for check-in (see [How to check in leads](/help-center/host/how-to-check-in-leads.md)).

## Deduplication

If a registrant's email matches an existing lead in your org, Mobly **updates** the existing lead rather than creating a duplicate:

* The lead's persona (first name, last name, email) is refreshed from the registration form
* The lead is associated with this event if it wasn't already
* The activity log gets a new registration entry, but the lead history is preserved

This matters for repeat attendees and for the common pattern of pre-registered VIPs who later fill out the public form. No duplicates, no manual merging.

## The "no email" edge case

If a registrant submits the form **without an email address** (rare, but possible if your form makes email optional), Mobly silently skips creating the lead. There's no error shown in the Hub. The registration is recorded on the Host side, but won't appear in Mobly until an email is added.

Two takeaways:

* **Keep email as required** on your Host registration form unless you have a specific reason not to. Optional email = registrants that vanish from Mobly's view.
* If you're missing registrants and don't know why, check the Host registration list for entries without an email — that's usually the cause.

## Enrichment mode for registrants

When you turn on **Mobly Registration** as the registration method for an event, Mobly asks how it should treat the data your registrants submit. Three choices, matching the modal you see when uploading a CSV of leads:

| Mode                                    | What it does                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Skip enrichment** (default)           | Import registrants as-is. Mobly never runs enrichment against them. They still sync to your CRM. |
| **Enrich, fill in missing fields only** | Enrichment only fills empty fields — the values a registrant provided are never overwritten.     |
| **Enrich, overwrite OK**                | Enrichment may replace values a registrant provided with enriched data.                          |

**Default is Skip.** The safe assumption is that when someone types their own information into a form, that's the authoritative version — Mobly doesn't touch it. Change to a Fill or Overwrite mode when you want Mobly's enrichment layer to expand or refresh the registrant's profile (e.g., pulling in job title, LinkedIn URL, company size from the enrichment waterfall).

### Where to set it

* **On setup:** the enrichment mode modal opens automatically when you choose **Mobly Registration** as the event's registration method.
* **Later:** in the Registration tab menu, click **Switch enrichment method** (next to **Switch registration method**) to reopen the modal and change the mode.

### What Skip looks like

Registrants imported under Skip mode show up as **"Imported"** on the leads table and are excluded from every re-enrichment sweep. That state is durable — a lead stays Imported until someone changes the mode.

### Changing the mode later — retroactive re-enrichment

If you **loosen** the mode later (Skip → Fill in missing, or Skip → Overwrite OK), Mobly kicks off a background sweep that re-evaluates the event's existing registrants and enqueues enrichment for the eligible ones — you don't have to touch each Imported lead by hand. Leads still on Skip because of another event they're linked to stay skipped (the most-protective mode wins across events); already-enriched leads and leads currently being enriched are left alone.

Tightening the mode (Overwrite OK → Fill in missing, or either → Skip) doesn't retroactively undo prior enrichment — it only changes what happens on the next registration or resync.

## What doesn't sync (yet)

A few things stay on the Host side and don't currently flow into Mobly:

* **Custom form fields** beyond name, email, and company (see above)
* **Email-template engagement data** — opens, clicks, bounces from invitations Host sent. Visible in Host's analytics, not in the Mobly lead.
* **Plus-ones** as separate Mobly leads — currently the primary registrant's record is what syncs; plus-ones live in the Host guest record. Capture them in the mobile app on-site if you want them as Mobly leads.

These may extend over time. Talk to your CSM if any of them are blockers for your workflow.

## Troubleshooting

**"Registrants aren't showing up in Mobly."**

Most common causes, in rough order of likelihood:

1. **Registrant submitted without an email.** Check the Host registration list for entries with blank email fields.
2. **Host event isn't connected to a Mobly event.** Verify the connection by opening the event in the Hub — the Registration tab should show "Host" as the active method.
3. **Feature not enabled for your org.** If your team is on a plan that doesn't include Host registration, the sync doesn't run. Contact your CSM to confirm.
4. **Brief delay during high registration volume.** Most syncs complete in seconds; spikes can push it to a minute or two. If leads are still missing after \~5 minutes, contact support.

## Related articles

* [Getting started with Host](/help-center/host/getting-started-with-host.md)
* [Connecting to Host](/help-center/host/connecting-to-host.md)
* [How to upload a CSV of leads](/help-center/the-hub/working-with-leads/how-to-upload-csv-for-enrichment.md) — CSV upload uses the same three enrichment modes on its confirm step
* [Preparing the event page](/help-center/host/preparing-the-event-page.md) — the form registrants fill out
* [How to check in leads](/help-center/host/how-to-check-in-leads.md) — what happens at the event when registrants arrive