> 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/connecting.md).

# Connecting a Marketing Automation tool

Mobly uses a single setup flow for both supported Marketing Automation tools — Marketo and Pardot. This article covers the universal connect steps. For vendor-specific notes (Marketo workspaces, Pardot Business Units, etc.) see the [per-vendor setup guide](/help-center/integrations/marketing-automation.md#per-vendor-docs) for the integration you're connecting.

## Before you start

You'll need:

* **Admin access to your MA tool** (or a user with the right permissions — see your vendor's setup guide for specifics)
* **Admin access in Mobly** (to view and configure Integrations)
* A few minutes — typical end-to-end setup is 15–20 minutes once permissions are in order

> Mobly supports one active Marketing Automation integration per organization today. You can also connect one CRM alongside the MA tool. Multiple integrations within the same category isn't supported yet.

## Connect the integration

1. In Mobly, go to **Integrations** in the left nav
2. Find your MA tool under the **Marketing Automation** category and click its card
3. You'll land on the integration's page with five tabs: **Connect**, **Mapping**, **Qualifiers**, **Campaigns**, **Reconciliation**
4. On the **Connect** tab, click **Connect**
5. A new window opens — sign in to your MA tool and approve the permissions Mobly requests
6. The window closes and you're back in Mobly. The integration card now shows **Connected** with a globe icon

That's the connection itself. Mobly can now reach your MA tool, but no data is flowing yet — you still need to configure mappings.

> Pardot uses Salesforce SSO for authentication, since Pardot is a Salesforce-owned product. The "sign in" step will redirect you through Salesforce.

## Configure data flow

After connecting, work through these tabs in order:

1. [**Field mapping**](/help-center/integrations/marketing-automation/field-mapping.md) — match Mobly fields to MA fields (Lead, Prospect, etc.). Use **Set Defaults** to auto-populate Mobly's recommended mappings as a starting point.
2. [**Qualifiers**](/help-center/integrations/marketing-automation/qualifiers.md) — map Mobly qualifier values to MA picklist or property options.
3. [**Campaigns**](/help-center/integrations/marketing-automation/campaign-mapping.md) — optionally enable per-event Program sync (Marketo only — Pardot doesn't have a campaign-object equivalent).
4. [**Sync mode**](/help-center/integrations/marketing-automation/sync-modes.md) — choose Automatic (real-time) or Manual.

You can come back to any of these tabs later — none of them lock you in.

## Verify the connection works

After you've set up at least one Mapping and chosen a Sync mode:

1. Capture a test lead at a test event in Mobly
2. Wait a minute or two for enrichment
3. Check **Reconciliation → Cleared** — your test lead should show up there
4. Open your MA tool and confirm the Lead/Prospect was created with the fields you mapped

If the test lead lands in **Reconciliation → Failed** instead, see [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md) for how to read the error and fix it.

## Status indicators

On the Connections list (the main **/integrations** page):

| Indicator                  | Meaning                                                                             |
| -------------------------- | ----------------------------------------------------------------------------------- |
| **Connected** + globe icon | Mobly can reach your MA tool and sync is enabled                                    |
| Greyed-out card            | Never connected, or has been disconnected                                           |
| **Disabled** badge         | Connected but sync is paused — connection and mappings are kept, no data is flowing |

## Pause, disconnect, or reconnect

The Connect tab has two buttons next to the integration's status:

* **Disable** — pauses syncing but keeps the connection and all mappings. Use this when you want to stop syncing temporarily (e.g., during an MA tool migration on your side) without losing your configuration.
* **Disconnect** — fully removes the connection. Mappings and qualifier configurations are kept in case you reconnect with the same vendor later.

To re-authenticate after a connection breaks (auth expired, password changed, etc.), click **Connect** again on the same integration's Connect tab. There's no need to disconnect first for a re-auth.

## Related articles

* [Comparing the Marketing Automation integrations](/help-center/integrations/marketing-automation/comparison.md)
* [Sync modes](/help-center/integrations/marketing-automation/sync-modes.md)
* [Field mapping](/help-center/integrations/marketing-automation/field-mapping.md)
* [Qualifiers](/help-center/integrations/marketing-automation/qualifiers.md)
* [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md)


---

# 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/connecting.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.