> 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 [Checking in Host registrants](/help-center/the-hub/managing-events/checking-in-host-registrants.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. ## 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) * [Preparing the event page](/help-center/host/preparing-the-event-page.md) — the form registrants fill out * [Checking in Host registrants](/help-center/the-hub/managing-events/checking-in-host-registrants.md) — what happens at the event when registrants arrive --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/host/how-registrants-flow-into-mobly.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.