> 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/marketing-automation/marketo.md).

# Marketo

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

|                |                                                                   |
| -------------- | ----------------------------------------------------------------- |
| **Setup time** | \~20 minutes                                                      |
| **Difficulty** | Moderate (field types, workspace permissions)                     |
| **Required**   | Marketo admin (or API-enabled role with Lead Database read/write) |
| **Status**     | Generally available                                               |

## What you can do

* Sync leads to the Marketo Lead Database (matched by Lead ID, then Email)
* Map Mobly fields to standard or custom Marketo fields
* Use Marketo picklist fields (single- or multi-select) for qualifier mapping
* Sync per-event to Marketo Programs with Program Status driven by Mobly qualifier values

## What's not supported (yet)

* **Activity logging** — Mobly doesn't write per-activity records (calls, emails, meetings, notes) to Marketo. Outreach actions stay in Mobly's activity history; Marketo sees the resulting field updates but no discrete activity events. See [Finding Mobly activities in your CRM](/help-center/integrations/crm/finding-activities-in-your-crm.md) for what activity logging looks like on HubSpot/Salesforce/Zoho
* Smart List membership (use Smart Campaigns triggered by Mobly field updates instead)
* Running Marketo alongside another CRM in the same Mobly org

## Articles in this section

* [**Marketo setup guide**](/help-center/integrations/marketing-automation/marketo/setup-guide.md) — full walkthrough with Marketo-specific tips
* [**Connecting Marketo Programs to Mobly Events**](/help-center/integrations/marketing-automation/marketo/connecting-programs.md) — per-event Program sync
* [**Fixing Marketo sync errors**](/help-center/integrations/marketing-automation/marketo/troubleshooting.md) — Reconciliation error reference


---

# 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/integrations/marketing-automation/marketo.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.