> 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/the-hub/managing-events/tracking-activations.md). # Managing activations within an event {% embed url="" %} An **activation** is a sub-experience attached to an event — a session, breakout, booth, sponsored dinner, panel, or anything else inside a larger event that has its own date, its own roster, and its own outcomes worth tracking separately. Activations let you measure capture results, register attendees, and route leads at the session level, not just at the event level. \* This article is only relevant to Mobly Admins (with access to the Hub) \* ## When to create an activation Use activations when something inside your event needs to be tracked or run distinctly from the broader event registration: * **Sessions** — a keynote, breakout, workshop, or panel where you care which attendees showed up * **Booths and demos** — a sponsored experience inside a conference, with its own capacity and its own lead capture * **Dinners, happy hours, VIP gatherings** — separately ticketed or invitation-only sub-events * **Roundtables** — capacity-limited deep-dive discussions * **Time-windowed quick-capture** — the mobile app surfaces activations during their start/end window so reps can capture into the right sub-event in one tap If a sub-experience doesn't need its own roster, its own time window, or its own CRM routing, you can probably skip activations and use the parent event's roster. ## Creating an activation 1. In the Hub, open the event you want to add the activation to. 2. Click into the **Activations** tab on the event detail page. 3. Click **Add Activation**. 4. Configure: * **Name** — what appears in the mobile app and reports * **Type** — what kind of activation this is (Booth, Session, Networking Mixer, Meal, Onsite Office Visit, Giveaway, or Other). Reporting rolls up by type, and some types unlock type-specific tabs on the activation detail page. * **Date and time** — the start/end window for the activation. **Important:** the mobile app's quick-capture feature is only active during this window, so set generously if you think the activation might start early or run long. * **Location** — optional override; inherits from the parent event if blank * **Capacity** — optional cap on registrations * **Assigned users** — the reps running the activation * **Campaign** — optional; attach a Mobly campaign to route activation-captured leads to a specific flow in your CRM Save. The activation now appears in the parent event's Activations tab. ## The activation detail page Click into any activation from the Activations tab to land on its detail page. Tabs across the top: ### Summary The default landing tab. Capture funnel for the activation at a glance: * **Leads Captured** — leads scanned during the activation window * **Total Leads** — every lead associated with the activation, including pre-registrations * **Check-ins** — leads marked as checked in * **No Show** — registered leads who didn't check in Use Summary as your morning-after recap: did the session land? ### Leads The full table of leads in this activation, with the usual search / filter / sort. From here: * **Add a lead** — open the New Lead drawer to create and attach in one step * **Bulk import** — upload a CSV of attendees (see [Bulk-importing attendees](#bulk-importing-attendees) below) * **Export** — download the current list as CSV * **Per-row:** open the lead, remove from activation (keeps the lead on the parent event), or remove from event entirely (confirms first) ### Users The reps running this activation. Add or remove assignees here. If the parent event already has users assigned, you can pull them into the activation without re-adding them from scratch. ### Registration (if your org uses Host or registration) The activation's own registration flow — separate from the parent event's. Use when an activation needs its own landing page, RSVPs, capacity, or confirmations. If your org doesn't use registration features, this tab won't appear. ### Content (if your org uses the Content library) Two collections of content pieces attached to this activation: * **Always Included** — items that are part of every activation's content kit by default for your org * **Activation-specific** — pieces you've attached to just this one activation Attach or detach content here. If your org doesn't use Content, this tab won't appear. ### Campaign (if your org uses Campaigns) Two lists: * **Global** — campaigns associated with the parent event or other lists in your org * **Activation-specific** — campaigns scoped to just this activation's roster Click **Add Campaign** to create a new campaign already scoped to this activation. If your org doesn't use Campaigns, this tab won't appear. ## Editing an activation Click the **pencil** icon at the top of the activation detail page. The edit drawer covers the activation's identity: * Name, dates, location, capacity * Assigned users * Linked campaigns Save / Discard buttons commit or revert. > The edit drawer is for activation identity only. **Adding or removing attendees happens in the Leads tab** — via the New Lead drawer, bulk import, or per-row remove actions. ## Deleting an activation Click the **trash** icon at the top of the activation detail page. A confirmation dialog appears. If the activation has linked campaigns, the dialog lists which campaigns will be archived alongside it — so you don't accidentally orphan a campaign you wanted to keep. ## Bulk-importing attendees In the Leads tab, click **Add Lead → Bulk import**. The drawer steps through: 1. **Pick a CSV** or paste rows. Required columns: first name, last name, email at minimum (your org's lead-import policy may require more). 2. **Validate** — rows that fail land in a separate errors table so you can fix and retry. 3. **Map fields** — if your CSV column headers don't match Mobly's field names, map them here. 4. **Import** — creates new leads (or matches existing ones by email) and adds them to the activation's roster. The drawer reports created / matched / failed counts when the import completes. ## How activations show up elsewhere * **In the mobile app:** during the activation's date/time window, reps see a quick-capture option that automatically tags scans to this activation. No manual switching required. * **On the parent event:** the parent event's Activations tab lists every activation with its status (Future / Active / Past) and capture counts at a glance. * **In reporting:** activations show up in event ROI and dashboard breakdowns as their own roll-up under the parent event. ## Related articles * [How to add an event](/help-center/the-hub/managing-events/how-to-add-an-event.md) — the parent event your activation lives under * [How to assign users to an event](/help-center/the-hub/managing-events/how-to-assign-users-to-an-event.md) * [How to use Mobly campaigns](/help-center/campaigns/how-to-use-mobly-campaigns.md) — for the campaign routing piece * [How to check in leads](/help-center/the-hub/managing-events/how-to-check-in-leads.md) --- # 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/the-hub/managing-events/tracking-activations.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.