Salesforce setup guide
Mobly's Salesforce integration syncs every captured-and-enriched lead into your Salesforce Lead, Contact, and (optionally) Account objects. Connection runs through Mobly's new integration platform, so there's no Connected App, OAuth Consumer Key, or Password Auth panel to manage on your side.
What you can do
Sync leads to Salesforce Leads, Contacts, or Accounts — three sync strategies, see Choose a sync mode below
Sync to Custom Objects — Mobly can map captured lead fields to custom objects in your Salesforce org if they're configured in the new Mapping tab
Map any Mobly field to any Salesforce field — standard or custom
Use Salesforce picklists for qualifier mapping — both restricted and unrestricted picklists
Log lead activities to Salesforce as Tasks — outreach actions in Mobly (Pulse sequence emails, calls, meetings, LinkedIn touches, SMS, manual notes) become Tasks on the matching Lead or Contact, with the activity type in the Subject and notes in the body. See Finding Mobly activities in your CRM for the per-action breakdown
Sync to Salesforce Campaigns — see Connecting Salesforce Campaigns to Mobly Events for per-event Campaign sync
Toggle Automatic vs Manual sync — see Sync modes
What's not supported (yet)
Opportunity sync — Mobly doesn't create or update Opportunities. Use Salesforce Flow or Process Builder to convert Mobly-created Leads into Opportunities downstream
Multi-integration — running Salesforce alongside another CRM in the same Mobly org isn't supported today (one CRM per org)
Before you connect
You'll need:
A Salesforce user account with:
API Enabled permission (under the user's Profile or assigned Permission Set)
Create + Edit access to Lead, Contact, Account, plus any custom objects you've mapped
Read + Edit access to relevant fields on those objects
A Mobly admin account to view and configure Integrations
About 30 minutes for setup, longer if your Salesforce org has heavy validation rules or restricted profiles
Use a dedicated integration user if possible — create a Salesforce user with Mobly's required permissions whose credentials are owned by your IT team rather than tied to an individual employee. This survives team changes without breaking the integration.
Connect the integration
Go to Integrations → Salesforce in Mobly
Click Connect on the Connect tab
Sign in to Salesforce in the OAuth window that opens
Approve the requested permissions
Detailed walkthrough of the Connect flow: see Connecting your CRM.
The legacy "OAuth 2.0 Connected App" setup with Consumer Key/Secret is no longer required. The new integration platform uses standard Salesforce OAuth — no Connected App configuration on your side.
Choose a sync mode
Salesforce has three matching strategies, set on the Salesforce integration's Connect tab. Pick one based on how your team wants Mobly leads to land in Salesforce.
Leads and Contacts (recommended)
Contact ID → Contact Email → Lead ID → Lead Email
Creates a new Lead
Leads only
Lead ID → Lead Email
Creates a new Lead
Accounts and Contacts
Contact ID → Contact Email → Account by website domain or company name
Creates a new Contact in matched Account, or both if no match
Leads and Contacts is the most common choice for orgs that use both Lead and Contact objects.
Leads only is for orgs that route everything through Lead first (typical for inbound-heavy or SDR-driven workflows where the Convert step happens later).
Accounts and Contacts is for orgs that work primarily with named Accounts and don't use Salesforce Leads.
You can change the strategy later, but in-flight leads sync against whatever was set when they were captured. Switching strategies mid-event can fragment a campaign across object types — pick before your first event if you can.
Configure data flow
Work through the tabs in order:
Mapping — match Mobly fields to Salesforce fields. Persona section maps to Lead and/or Contact (depending on your sync mode); Company section maps to Account.
Qualifiers — define qualifiers and map values to Salesforce picklist options.
Registration — set the Salesforce Campaign Member Status a lead gets at each Mobly registration state (see below).
Labels — group leads inside Mobly by qualifier value, event, activation, or scan count. Mobly-side only.
Sync mode — Automatic by default; switch to Manual on the Connect tab if needed.
Registration mappings
The Registration tab is where you set the org-wide default Salesforce Campaign Member Status for each of Mobly's three lead-registration states.
Mobly tracks a lead through three registration states as they move through your event:
Registered
Lead signed up before the event
Checked-in
Lead checked in at the door
Live Capture
Lead scanned on the floor
For each state, pick the Salesforce Campaign Member Status you want that state to map to (e.g., "Sent," "Responded," "Attended"). When a lead hits that state in Mobly, the linked Salesforce Campaign's Campaign Member Status for that lead updates to the mapped value.
How the mappings are used. These are org-level defaults — every Event or Activation you link to a Salesforce Campaign picks up these three mappings automatically. You can override any state on an individual Event or Activation if that particular booth or dinner uses different Campaign Member Statuses.
When to use it. If you want your reps' Salesforce filters (or reports, or downstream automation) to distinguish "who pre-registered vs walked in vs got scanned on the floor," set these once here and every event uses them by default.
Salesforce-specific configuration tips
Restricted picklists. If a Salesforce field has "Restrict to Picklist Values" turned on, Mobly can only send values that exist as options. Either pre-add every Mobly qualifier value to the Salesforce picklist, or turn restriction off, or map Mobly to an open-text field instead.
Validation Rules. Salesforce Validation Rules can reject Mobly's writes silently. If a custom Validation Rule requires fields Mobly isn't sending, leads land in Reconciliation → Failed under DATA_VALUE_VALIDATION. Either adjust the rule to allow Mobly's connecting user (using a IF($User.Username == 'mobly@yourcompany.com', false, ...)-style guard) or ensure Mobly is mapped to send the required fields.
Field-level security. Mobly's connecting user needs field-level read/write permission to every field in the Mobly mapping. Profiles or Permission Sets that lock down certain fields will cause Mobly to silently skip them. Check Setup → Object Manager → [Object] → Fields & Relationships → [field] → Set Field-Level Security.
Long Text Areas. Salesforce text fields default to 255 characters. For longer Mobly fields (notes, descriptions), use Long Text Area or Rich Text Area on the Salesforce side, or remap to a longer-tolerating field.
Connected user lifecycle. If the user that authorized Mobly is later deactivated or has API Enabled removed, syncing stops. Use a service account or rotate the connection to a current user proactively.
Send Leads With No Emails. On the Mapping tab, expand the Email field's row and you'll find a per-integration toggle: Send Leads With No Emails. Off by default — Mobly skips creating a Salesforce Lead when the captured record has no email. Turn it on and Mobly will still create the Lead in Salesforce, with the email field blank. Salesforce-only, and only shows when your sync mode is Leads-based (Leads only, or Leads and Contacts). Handy when your Salesforce workflow doesn't require Email at Lead creation and you'd rather have a record to route than a silent drop.
Troubleshooting
If a synced lead shows up in Reconciliation → Failed, see Fixing Salesforce sync errors — there's a section per error category with the fix.
For broader integration questions (auth, permissions, what data lands where), revisit Connecting your CRM and How data flows from Mobly to your CRM.
Related articles
Last updated
Was this helpful?