> 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/integrations/crm/qualifiers.md). # Qualifiers Qualifiers are how Mobly captures structured data about leads at events. Once mapped to your CRM, qualifier values flow into your CRM records as fields (or, for Note Activity qualifiers, as activity log entries) — where they drive segmentation, routing, and automation. This article covers the **CRM mapping side** of qualifiers. For creating and configuring qualifiers themselves, see [Configuring qualifiers](/help-center/the-hub/working-with-leads/configuring-qualifiers.md). ## Where the CRM mapping lives Every qualifier's CRM mapping is controlled on the **Integration** tab of the qualifier's edit modal. Open the modal from **Lead Settings → General → Qualifiers** by clicking any qualifier row, then switch to the **Integration** tab. ## Auto Create from CRM The fastest way to align a qualifier with your CRM is to start from the CRM field itself. When creating a new qualifier, pick **Auto Create** on the type-picker screen. Mobly asks which CRM object and field you want to mirror, then reads that field's shape from your CRM and pre-fills the qualifier: * **Picklist fields** → Mobly creates a Picklist qualifier with the CRM's picklist options pre-loaded and mapped 1:1. * **Number / currency / percent fields** → Numeric qualifier, with the numeric bounds pulled if the CRM specifies them. * **Boolean fields** → Boolean qualifier, with the True/False labels auto-adjusted to whatever the CRM uses (Yes/No, True/False, 1/0). * **Text fields** → Open Text qualifier — with the option to convert to Picklist or Boolean before saving if you'd rather store fixed options. **Which CRMs support Auto Create**: Salesforce, HubSpot, Zoho, Marketo. Other integrations still work for mapping, but you'll pick the type manually and enter the values yourself. This is a **one-time fast-path**, not a background sync. If the CRM field's options change later, you'll need to update the qualifier's values in Mobly manually — or use **Change field** in the modal footer to remap to a different CRM field. ## How each qualifier type maps to CRM Behavior on the Integration tab depends on the qualifier's type. ### Picklist Each Mobly qualifier value maps to a CRM picklist option. The Integration tab shows a dropdown next to each value where you pick the matching CRM option. For **Multiple**-selection picklists, choose a **separator** — comma or semicolon (default). Mobly joins the selected values with your separator and sends the string to your CRM's multi-select or text field. If a CRM picklist doesn't have an option for one of your Mobly qualifier values, you have two choices: 1. **Add the missing option in your CRM** — best when the value is a real concept your team uses outside Mobly too. 2. **Map the Mobly qualifier value to an existing close-enough option** — fastest when you don't want to expand the CRM picklist. ### Boolean Maps to a CRM Yes/No, True/False, or checkbox field. If the CRM field uses Yes/No labels, the qualifier's True/False labels auto-adjust to match — so what your reps see on the mobile app lines up with what shows up in the CRM. ### Numeric Sent as a number to the CRM field. The unit label (`$`, `%`, `mi`, etc.) is display-only in Mobly — the CRM stores the numeric value. ### Open Text Sent as a string to a CRM text or long-text field. Open Text has one special mode: the **Send as activity** toggle. When enabled, instead of writing the value to a CRM field, Mobly writes it as an **activity or Note on the CRM record** (subject to your CRM's activity API). This is how the Note Activity type is achieved end-to-end — pick Open Text, flip Send as activity on. ### Note Activity Note Activity qualifiers write to the CRM as activity/Note entries by design — no field mapping needed. The activity carries the qualifier name, the note text, the event or activation context, and a timestamp. Where the CRM supports activity logging (HubSpot, Salesforce, Zoho), the activity appears on the lead's or contact's activity feed there too. ## Reconciliation and unmapped values Unmapped picklist values trigger `NO_TAG_MAPPING` errors in [Reconciliation](/help-center/integrations/crm/reconciliation.md). Open a reconciliation error row and Mobly takes you straight to the mapping editor pre-loaded with the affected qualifier — quick fix when a new value goes unmapped. Numeric, Open Text, Boolean, and Note Activity qualifiers don't produce mapping errors the same way (they don't have discrete values needing lookup), so most reconciliation traffic is picklist mapping gaps. ## Best practices * **Auto Create from CRM when you can.** It guarantees 1:1 alignment on picklist options and saves the most manual mapping work. Only limited to Salesforce, HubSpot, Zoho, Marketo today. * **Match CRM picklists 1:1.** Easier mapping, fewer reconciliation gaps. * **Use Open Text with Send as activity** when you want unstructured commentary logged as a CRM activity — captures the "what did the rep observe" without cluttering fields. * **Pick your multi-select separator to match your CRM's expectations.** Marketo and HubSpot pipe-list handling can be finicky; check what your workflows expect before shipping. * **Archive obsolete qualifiers.** Historical values stay queryable in Mobly. ## Related articles * [Configuring qualifiers](/help-center/the-hub/working-with-leads/configuring-qualifiers.md) — the primary qualifier setup guide * [How to use qualifiers to manage leads](/help-center/the-hub/working-with-leads/how-to-use-qualifiers-to-manage-leads.md) — downstream automation examples * [Field mapping](/help-center/integrations/crm/field-mapping.md) — for non-qualifier fields (name, email, etc.) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) — where unmapped qualifier values surface * [Mapping campaign fields](/help-center/integrations/crm/campaign-mapping.md)