> 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/pardot/setup-guide.md). # Pardot setup guide Mobly's Pardot (Salesforce Marketing Cloud Account Engagement) integration syncs every captured-and-enriched lead into your Pardot Prospect database, with field mapping, qualifier mapping, and per-event campaign sync. Connection runs through Mobly's new integration platform via Salesforce SSO. ## What you can do * **Sync leads to Pardot Prospects** — every Mobly-captured lead becomes a Pardot Prospect, matched by Email (Pardot's unique identifier for prospects) * **Map any Mobly field to any Pardot Prospect field** — standard or custom * **Use Pardot dropdown fields** for qualifier mapping * **Sync to Pardot Campaigns** — link Mobly events to Pardot campaigns for member-level tracking * **Toggle Automatic vs Manual sync** — see [Sync modes](/help-center/integrations/marketing-automation/sync-modes.md) ## What's not supported (yet) * **Activity logging** — Mobly doesn't write per-activity records (calls, emails, meetings, notes) to Pardot. Outreach actions reps take in Mobly stay in Mobly's activity history; Pardot sees the resulting field updates (e.g., last touched timestamp) but no discrete activity events. For what activity logging looks like on the CRMs that support it (HubSpot, Salesforce, Zoho), see [Finding Mobly activities in your CRM](/help-center/integrations/crm/finding-activities-in-your-crm.md) * **Custom object sync** — Mobly only writes to the Prospect object today * **Engagement Studio enrollment** — Mobly doesn't directly add Prospects to Engagement Studio programs. Use a Pardot Automation Rule keyed off a Mobly field change to enroll prospects post-sync * **Account Engagement custom objects** — only Prospects are mapped from Mobly * **Multi-integration** — running Pardot 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** with: * The **Pardot Administrator** role (or another role with Prospect create/edit permissions) * The **Marketing User** permission on the Salesforce side * Access to the Pardot Business Unit you want Mobly to write to * A **Mobly admin account** to view and configure Integrations Pardot uses Salesforce SSO under the new integration platform, so the connecting user authenticates through Salesforce. Make sure the user has both the Salesforce-side permissions (Marketing User) and the Pardot-side role (Pardot Administrator). ## Connect the integration 1. Go to **Integrations → Pardot** in Mobly 2. Click **Connect** on the Connect tab 3. You'll be redirected to Salesforce SSO — sign in and approve permissions 4. If your org has multiple Pardot Business Units, pick the right one Detailed walkthrough: see [Connecting your CRM](/help-center/integrations/marketing-automation/connecting.md). ## Configure data flow Work through the tabs in order: 1. [**Mapping**](/help-center/integrations/marketing-automation/field-mapping.md) — match Mobly fields to Pardot Prospect fields. Persona section maps to Prospect. 2. [**Qualifiers**](/help-center/integrations/marketing-automation/qualifiers.md) — define qualifiers and map values to Pardot dropdown field options. 3. [**Campaigns**](/help-center/integrations/marketing-automation/campaign-mapping.md) — link Mobly events to Pardot campaigns. 4. [**Sync mode**](/help-center/integrations/marketing-automation/sync-modes.md) — Automatic by default; switch to Manual on the Connect tab if needed. ## Pardot-specific configuration tips **Pardot vs. Account Engagement naming.** Salesforce rebranded Pardot as "Marketing Cloud Account Engagement" but the underlying product and most documentation still reference "Pardot." Mobly uses "Pardot" for clarity — both terms refer to the same integration. **Prospect-only model.** Pardot doesn't have a separate Lead-vs-Contact distinction like Salesforce CRM does — everything is a Prospect. Mobly's Persona mapping section maps directly to Prospect fields. **Field types.** Match Mobly's TEXT/EMAIL/URL/PHONE badges to the matching Pardot field type. Misaligned types surface as `DATA_FORMAT_VALIDATION` errors in Reconciliation. **Long values.** Pardot text fields default to 255 characters. For longer Mobly fields (notes, descriptions), change the Pardot field type to **Textarea** under **Account Setup → Object and Field Configuration → Prospect Fields**. **Pardot CRM sync.** If your Pardot is connected to Salesforce CRM, Prospects synced from Mobly will eventually flow into Salesforce Leads/Contacts via your Pardot↔Salesforce connector. Don't double-connect Mobly to both Pardot and Salesforce — pick one as the entry point. **Account Engagement Sandbox.** If you're testing in a Pardot sandbox first, connect Mobly to the sandbox business unit. Switching to production requires reconnecting (the Connect flow will let you pick the production unit). ## Troubleshooting If a synced lead shows up in **Reconciliation → Failed**, see [Fixing Pardot sync errors](/help-center/integrations/marketing-automation/pardot/troubleshooting.md) — there's a section per error category with the fix. ## Related articles * [Connecting your CRM](/help-center/integrations/marketing-automation/connecting.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) * [Mapping campaign fields](/help-center/integrations/marketing-automation/campaign-mapping.md) * [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md) * [Fixing Pardot sync errors](/help-center/integrations/marketing-automation/pardot/troubleshooting.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/pardot/setup-guide.md?ask=&goal= ``` `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.