Mobly fields reference
Every Mobly field that can be captured, enriched, or mapped to your CRM or MA integration — what it means and what to know when mapping it.
Every lead in Mobly has a set of fields — some captured from the badge or business card, some enriched automatically, and some generated by Mobly itself (like the source event or capture timestamp). This article is the canonical list.
Use it when you're configuring Field mapping and want to know what each Mobly field means before mapping it to a CRM or MA property, or when you're troubleshooting why a specific field isn't populating the way you expect.
How to read the tables
Each field entry lists:
Field — the label you'll see in the Mobly field-mapping picker
What it holds — plain-English description plus any notes on format, multi-value handling, or edge cases worth knowing
Fields you don't map are still captured on the lead — mapping only controls what syncs to your connected CRM or MA tool.
Person fields
The fields tied to the person you scanned or added.
First Name
The person's first name
Last Name
The person's last name
Primary email address. Deduplicated at the org level.
Personal Email
Non-work email addresses. Can hold multiple values, semicolon-delimited when synced.
Professional Email
Additional work email addresses. Can hold multiple values, semicolon-delimited when synced.
The person's LinkedIn profile URL
The person's Facebook profile URL
X (Twitter)
The person's X / Twitter profile URL
Profile Picture
URL to a headshot image. Populated by enrichment only — not from scans or manual entry.
Job Title
The person's job title
Description
A shared, per-lead description that any rep on your team can read and edit. One Description per lead. See Notes vs Description vs Recordings for how Description differs from per-rep Notes.
Personal Address
Home / postal address
Company fields
The fields tied to the person's company.
Company Name
The company the person works for
Company Industry
Industry classification
Company LinkedIn
Company's LinkedIn URL
Company Street Address
Street address
Company City
City
Company State
State
Company Zip Code
Postal code
Company Country
Country
Phone numbers
Phone numbers are structured, not a single text field. Each lead can have multiple phone numbers, and each has a type and an optional preferred flag.
Phone type values: MOBILE, LANDLINE, DIRECT, OFFICE, HQ, UNKNOWN
Preferred: exactly one phone number per lead can be flagged as preferred. That's the number Mobly treats as primary and what maps to your CRM's "Phone" field via the phoneNumber resolver (see Special CRM-mapping resolvers below).
In the Hub: rep-added phones and enriched phones show as two separate groups on the lead detail page ("Added by you" vs. "Added by Mobly").
Mobly-generated metadata
Fields Mobly creates automatically as part of the lead's lifecycle. Useful for CRM reporting, event attribution, and filtering.
Capture Method
How the lead was added — Scan (badge/card scan in the mobile app), Manual (typed in by hand), Upload (imported via CSV), or API (added via Mobly's REST API — only relevant if your org uses the API)
Enrichment Status
Whether the lead has completed enrichment. Values in the leads-table filter: Enriched, Queued for enrichment, Imported
Enrichment Mode
How enrichment treats customer-provided data on this lead. Values: Overwrite (default; enrichment replaces existing values), Fill Missing (enrichment only fills empty fields), Skip (no enrichment). See Enrichment and lead statuses.
Created
Timestamp the lead was first added to Mobly
Added To This Event
Timestamp the lead was attached to a specific event. Only populated in event-scoped views.
Added To This Activation
Timestamp the lead was attached to a specific activation. Only populated in activation-scoped views.
Created By
The user who first added the lead
Owner
The user assigned as the lead's owner
Number of Scans
How many times the lead has been scanned (aggregated across all reps and events)
Last Scanned By
The most recent rep to scan this lead
Special CRM-mapping resolvers
These aren't columns on the lead record — they're computed values Mobly exposes in the field-mapping picker specifically because customers commonly want to sync them. You'll see these in the "Mobly field" dropdown on the Mapping tab alongside the regular fields above.
moblyId
Mobly's internal ID for the lead. Useful for reverse lookups from your CRM back into Mobly.
phoneNumber
The lead's preferred phone number.
otherPhoneNumbers
All non-preferred phone numbers, joined by semicolons.
eventName
The event the lead was captured at, plus activation names if applicable. See your integration setup guide for event naming behavior.
numberOfScans
Total scan count for the lead.
firstScannedBy
Rep who first scanned the lead.
lastScannedBy
Rep who most recently scanned the lead.
lastScannedEvent
Most recent event the lead was scanned at.
allScannedEvents
All events the lead has been scanned at.
Qualifiers are separate
Qualifiers (custom tags your team applies to leads) are configured per-org, not part of the fixed field list above. See Configuring qualifiers for how to set them up and Qualifiers (CRM integration) for how they map into your CRM.
Related articles
Field mapping (CRM) — how to map these fields to your CRM
Field mapping (Marketing Automation) — same for MA tools
Write behavior (CRM) — control per-field whether Mobly overwrites the CRM value
Enrichment and lead statuses — the enrichment lifecycle
How does Mobly's OCR work? — what fields OCR extracts from scans
Last updated
Was this helpful?