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

# Comparing the Marketing Automation integrations

Mobly integrates with two Marketing Automation tools — Marketo and Pardot (Salesforce Marketing Cloud Account Engagement). This article is a side-by-side reference for what each integration supports.

Use this when:

* You're picking which MA tool to connect first
* You're evaluating whether a feature you need is available
* A CSM needs a fast answer to "does Mobly do X for \[vendor]?"

For setup-specific instructions, jump to the per-vendor [setup guides](/help-center/integrations/marketing-automation.md#per-vendor-docs).

> Looking for a CRM? Mobly also integrates with HubSpot, Salesforce, Pipedrive, and Zoho — see the [CRM comparison](/help-center/integrations/crm/comparison.md).

## At-a-glance

|                                  | Marketo    | Pardot                   |
| -------------------------------- | ---------- | ------------------------ |
| **Setup time**                   | \~20 min   | \~20 min                 |
| **Difficulty**                   | Moderate   | Easy–Moderate            |
| **Auth**                         | OAuth      | OAuth via Salesforce SSO |
| **Lead/Prospect sync**           | ✓          | ✓                        |
| **Company/Account sync**         | —          | —                        |
| **Activity logging**             | —          | —                        |
| **Campaign / Program sync**      | ✓ Programs | —                        |
| **Configurable sync strategies** | —          | —                        |
| **Custom object support**        | —          | —                        |

## By feature

### Authentication

Both Marketing Automation integrations use OAuth through Mobly's new integration platform. **Pardot** is the only one with a quirk: it authenticates via Salesforce SSO since Pardot is a Salesforce-owned product, so the connecting user signs in through Salesforce rather than directly via Pardot.

### Lead / Prospect sync

The MA-side object differs by vendor:

| Vendor  | Primary object | How Mobly matches existing records              |
| ------- | -------------- | ----------------------------------------------- |
| Marketo | Lead           | Lead ID → Email (upsert)                        |
| Pardot  | Prospect       | Email (Prospects are unique by email in Pardot) |

Both write the lead-side record only — company information lives on the Lead/Prospect record as fields, not as a separate Account/Company object.

### Activity logging

**Neither MA tool supports activity logging from Mobly today.** When reps take an outreach action in Mobly (Pulse email, manual note, etc.), the activity stays in Mobly's history. The MA tool sees the resulting field updates (e.g., last touch timestamp) but no per-activity record.

For activity logging, you'd need to be on HubSpot, Salesforce, or Zoho — see the [CRM comparison](/help-center/integrations/crm/comparison.md).

### Campaign / Program sync

Per-event sync to a campaign-equivalent object on the MA side:

| Vendor      | Object  | Notes                                                                                    |
| ----------- | ------- | ---------------------------------------------------------------------------------------- |
| **Marketo** | Program | Program Status drivable from Mobly qualifier values. Exact match required on status text |
| **Pardot**  | —       | No campaign object sync. Use Pardot Automation Rules keyed off Mobly field changes       |

### Field type enforcement

Both MA tools are strict about field types — sending an unrecognized picklist value or a wrong-typed field surfaces as a `DATA_FORMAT_VALIDATION` or `DATA_VALUE_VALIDATION` error in [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md). Plan for cleaner upfront mapping than you might with a CRM.

| Vendor      | Strictness | What this means                                                             |
| ----------- | ---------- | --------------------------------------------------------------------------- |
| **Marketo** | Strict     | Field types and picklists strongly enforced                                 |
| **Pardot**  | Moderate   | Standard prospect fields are strict; custom prospect fields more permissive |

## When to use what

**Marketo and Pardot serve different ecosystems.** Pick the one your team's already on:

* **Marketo** if your marketing stack is Adobe-centric or Marketo is your existing engagement platform
* **Pardot** if you're a Salesforce shop and use Account Engagement (Pardot) for lead nurturing

Both have the same core capability set in Mobly: lead sync + qualifier mapping. Marketo adds Program sync for per-event attribution.

## Per-vendor details

* [Marketo](/help-center/integrations/marketing-automation/marketo.md)
* [Pardot](/help-center/integrations/marketing-automation/pardot.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/comparison.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.