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

# Field mapping

Field mapping decides where each Mobly field lands in your MA tool. You configure it on the **Mapping** tab inside any connected Marketing Automation integration (**Integrations → \[your MA tool] → Mapping**).

For a full list of every Mobly field, what it holds, and where the data comes from, see the [Mobly fields reference](/help-center/integrations/mobly-fields-reference.md).

## What's on the Mapping tab

Per-object sections — typically **Lead** (Marketo) or **Prospect** (Pardot), with the lead-side object as the primary mapping target. MA tools don't have a separate Account/Company object like CRMs do; company info goes onto the Lead/Prospect record as fields.

Each section is a table of rows:

* **Mobly Field** on the left — the field as Mobly knows it (e.g., First Name, Email, Phone Number, Job Title), with a type badge: **TEXT**, **EMAIL**, **URL**, etc.
* **MA Field** on the right — a dropdown to pick the field where this Mobly value should land. Leave blank to skip a field. Click the **×** to clear an existing mapping.

Two actions in the top right of each section:

* **Set Defaults** — auto-populates Mobly's recommended mappings. Good starting point. You can tweak individual rows after.
* **Clear object mappings** — removes every mapping for the object. Useful if you're starting over.

## How saving works

There's no Save button. Each field change saves immediately when you pick a value (or clear one). If you switch tabs or close the window mid-edit, your last selection on each row is already saved.

This is intentional — earlier versions of the Mobly integration could lose mappings when you switched tabs without saving. Auto-save fixes that.

## Setting up mappings for a new integration

Quickest path to a working setup:

1. Go to **Integrations → \[your MA tool] → Mapping**
2. Click **Set Defaults** on the Lead/Prospect section
3. Review the auto-populated rows, change anything that doesn't fit your MA tool's schema
4. Move on to the [Qualifiers](/help-center/integrations/marketing-automation/qualifiers.md) and [Campaigns](/help-center/integrations/marketing-automation/campaign-mapping.md) tabs

If your MA tool has unusual field naming conventions or required custom fields, defaults won't cover them — you'll need to fill those in manually.

## Field types — what to expect

The type badge on each Mobly field tells you what kind of MA field it expects to land in:

* **TEXT** — single-line text. Most short fields.
* **EMAIL** — email-formatted string. Map to an Email-type field, not a generic text field, so the MA tool validates correctly.
* **URL** — a full URL (with `https://`). Map to a URL-type field.
* **PHONE** — phone-formatted. Map to a Phone-type field.

Marketing Automation tools enforce field types more strictly than some CRMs. Misaligned types surface as `DATA_FORMAT_VALIDATION` errors in [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md) once leads start syncing.

## Common gotchas

* **Marketo strict typing.** Marketo will reject string values sent to date fields or unrecognized picklist values. Get types right up front to avoid Reconciliation noise.
* **Pardot field length defaults.** Most Pardot text fields default to 255 characters. For longer Mobly fields (notes, descriptions), change the Pardot field type to Textarea or remap to a Mobly field that fits.
* **Skipping the Lead/Prospect section entirely** — Mobly will have nothing to sync. Always map at least Email + name fields.
* **Changing field types after mapping** — if you change a field type in Marketo or Pardot after mapping, revisit the Mobly mapping to confirm the type expectations still match.

## Vendor-specific notes

Each MA tool has its own field schema and quirks. See your vendor's setup guide for vendor-specific field naming and configuration:

* [Marketo](/help-center/integrations/marketing-automation/marketo/setup-guide.md)
* [Pardot](/help-center/integrations/marketing-automation/pardot/setup-guide.md)

## Choosing what Mobly overwrites

Once fields are mapped, you can decide for each one whether Mobly should overwrite what's already in your MA tool or leave existing values alone. Set the gear icon on any mapped field row to configure it — see [Write behavior](/help-center/integrations/marketing-automation/write-behavior.md) for the details.

## Related articles

* [Write behavior](/help-center/integrations/marketing-automation/write-behavior.md) — decide per-field whether Mobly overwrites or preserves the value in your MA tool
* [Qualifiers](/help-center/integrations/marketing-automation/qualifiers.md) — for qualifier mapping (separate from field mapping)
* [Mapping campaign fields](/help-center/integrations/marketing-automation/campaign-mapping.md) — for per-event Program sync (Marketo only)
* [How data flows from Mobly to your MA tool](/help-center/integrations/marketing-automation/how-data-flows.md)
* [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md) — see field-level errors