> 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/how-to-configure-qualifiers-by-event.md).

# How to configure qualifiers by event

{% embed url="<https://getmobly.wistia.com/s/t8ko8qsjsst673m>" %}

\* This article is only relevant to Mobly Admins (with access to the Hub) \*

Some qualifiers make sense at every event (Lead Type, Follow-up Decision). Others are event-specific — booth-specific raffle entries, conference-specific session interest, one-off campaigns. Mobly lets you mix and match: org-wide qualifiers run everywhere by default, and event-specific qualifiers turn on only for the events that need them.

For example:

* At a **large enterprise event**, you might prioritize qualifiers like company size, timeline, and pain points.
* At a **startup-focused event**, you might surface authority, demo readiness, and budget instead.
* At a **booth-specific giveaway**, you might add a one-off "Entered raffle?" qualifier for just that event.

Reps in the mobile app only see the qualifiers that apply to the event they're working — less clutter at the booth, cleaner data downstream.

## Step 1 — Set the qualifier's default scope

For each qualifier you want to be event-specific, set its default scope to **off** so it doesn't show up everywhere by default.

1. In the Hub, go to **Lead Settings**.
2. Click the **edit icon** on the qualifier you want to scope.
3. Toggle the "visible at all events" setting to **No**. This makes the qualifier opt-in per event rather than always on.
4. Save.

A qualifier set to "**Yes**" (visible at all events) is your **Always Included** baseline — every event gets it automatically. A qualifier set to "**No**" is event-specific — it shows up only when you explicitly add it to an event.

## Step 2 — Add event-specific qualifiers to an event

1. In the Hub, open the event you want to configure.
2. Click into the **Qualifiers** field on the event detail page.
3. You'll see your **Always Included** qualifiers checked by default — those run at every event.
4. Pick any **event-specific qualifiers** you want to add to this event from the available list.
5. Save.

The selected qualifiers now appear in the Mobly mobile app for any rep scanning leads at this event.

## When to use which scope

* **Always Included (visible at all events):** lead-classification questions every rep needs to answer at every event. Lead Type, Follow-up Decision, Approval Status.
* **Event-specific:** topical or campaign-driven questions that only matter for one event (or a small set). "Visited the demo booth?" at a single conference. "Entered the raffle?" at a specific giveaway. Session-interest picks at a multi-session summit.

> When the event ends, the event-specific qualifier values you collected stay on the lead records. You don't lose the data — the qualifier just stops appearing in the mobile app for new scans at unrelated events.

## Related articles

* [Configuring qualifiers in Lead Settings](/help-center/the-hub/working-with-leads/configuring-qualifiers.md) — the main qualifier setup (org-wide)
* [How to use qualifiers to manage leads](/help-center/the-hub/working-with-leads/how-to-use-qualifiers-to-manage-leads.md) — the rep-side application
* [How to add an event](/help-center/the-hub/managing-events/how-to-add-an-event.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/how-to-configure-qualifiers-by-event.md?ask=<question>&goal=<endgoal>
```

`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.