For the complete documentation index, see llms.txt. This page is also available as Markdown.

Marketo setup guide

Mobly's Marketo integration syncs every captured-and-enriched lead into your Marketo Lead Database, with field mapping, qualifier mapping, and per-event Program (campaign) sync. Connection runs through Mobly's new integration platform — no LaunchPoint service, API user, or custom REST role to set up on your side.

What you can do

  • Sync leads to the Marketo Lead Database — every Mobly-captured lead becomes a Marketo Lead, matched by Lead ID first, then Email

  • Map any Mobly field to any Marketo field — including custom fields (under Admin → Field Management)

  • Use Marketo picklist fields for qualifier mapping — both single-select and multi-select fields

  • Sync to Marketo Programs — see Connecting Marketo Programs to Mobly Events for per-event program sync

  • Toggle Automatic vs Manual sync — see Sync modes

What's not supported (yet)

  • Activity logging — Mobly doesn't write any per-activity records (calls, emails, meetings, notes) to Marketo. Outreach actions reps take in Mobly stay in Mobly's activity history; Marketo only sees the resulting Lead field updates. For what activity logging looks like on the CRMs that support it (HubSpot, Salesforce, Zoho), see Finding Mobly activities in your CRM

  • Smart List membership — Mobly doesn't directly add leads to Smart Lists. Use Marketo Smart Campaigns triggered by Mobly's field updates if you need this

  • Multi-integration — running Marketo alongside another CRM in the same Mobly org isn't supported today (one CRM per org)

Before you connect

You'll need:

  • A Marketo user with admin access (or at minimum, an API-enabled role with Lead Database read/write and Program management)

  • A Mobly admin account to view and configure Integrations

  • About 20 minutes for setup if your Marketo schema is already aligned with what Mobly captures

Use a dedicated API user if possible — Marketo best practice is to have integration credentials owned by IT rather than an individual.

Connect the integration

  1. Go to Integrations → Marketo in Mobly

  2. Click Connect on the Connect tab

  3. Sign in to your Marketo instance and approve the permissions Mobly requests

Detailed walkthrough: see Connecting your CRM.

The legacy LaunchPoint Service + Custom REST Role + Client ID/Secret setup is no longer required. The new integration platform uses standard Marketo OAuth — no LaunchPoint configuration on your side.

Configure data flow

Work through the tabs in order:

  1. Mapping — match Mobly fields to Marketo fields. Persona section maps to Lead.

  2. Qualifiers — define qualifiers and map values to Marketo picklist options.

  3. Campaigns — link Mobly events to Marketo Programs.

  4. Sync mode — Automatic by default; switch to Manual on the Connect tab if needed.

Marketo-specific configuration tips

Field types matter. Marketo enforces field types more strictly than some CRMs — sending a string to a date field, or an unrecognized value to a picklist, surfaces as DATA_FORMAT_VALIDATION or DATA_VALUE_VALIDATION in Reconciliation. Match Mobly's TEXT/EMAIL/URL/PHONE badges to the matching Marketo field type.

String length defaults. Marketo string fields default to 255 characters. For longer Mobly fields (notes, descriptions), increase the field size in Admin → Field Management → [field] → Field Properties or remap to a Textarea.

Custom fields naming. Marketo doesn't have separate "namespaces" for custom fields the way some CRMs do — naming hygiene matters. A Mobly prefix (Mobly_Capture_Date, Mobly_Event_Name) keeps integration fields distinguishable from rest of the schema.

Picklist visibility. Marketo picklists may be restricted by Field Visibility rules per workspace. The connecting user needs visibility into every field in the mapping. If certain fields aren't appearing in the Mapping dropdown, check workspace permissions.

Programs vs. Smart Campaigns. Mobly's per-event campaign sync writes to Marketo Programs. If your team uses Smart Campaigns to trigger downstream automation, build them to listen for the Mobly-set field changes (e.g., Mobly Last Capture Date is changed) rather than expecting Mobly to fire Smart Campaign-style triggers directly.

Troubleshooting

If a synced lead shows up in Reconciliation → Failed, see Fixing Marketo sync errors — there's a section per error category with the fix.

Last updated

Was this helpful?