Administration11% of the exam
Custom prospect fields and Salesforce field mapping
How an Account Engagement admin creates and edits custom prospect and account fields, maps them to Salesforce lead, contact and account fields, and chooses the sync behavior that decides which system's value wins.
Illustrate how to create, edit, and map fields.
~8 min read · 11 practice questions ·
What the exam expects
- Create a custom prospect or account field in the Lightning App (not in Salesforce Object Manager), leaving the generated Custom Field ID alone.
- Edit field settings (predefined values, type, global defaults) and know what an edit changes on existing forms and records.
- Map a custom field to a Salesforce lead, contact or account field, and troubleshoot a field that is missing from the mapping dropdown or does not sync.
- Choose a sync behavior (Account Engagement value, Salesforce value, most recently updated record or field) and predict which value wins.
- Key terms: custom prospect field (an admin-created field on the prospect record); Custom Field ID (the generated internal identifier); field mapping (linking an Account Engagement field to a Salesforce field so it can sync); sync behavior (the rule for which system's value is primary); predefined values (a fixed value list for checkboxes, radio buttons, dropdowns and multi-selects).
Key facts
Permission to create or map custom fields
- Detail
- Account Engagement Administrator role
Field Name and Custom Field ID
- Detail
- Neither is visible to prospects; don't edit the ID
Lead and contact to one prospect field
- Detail
- Salesforce API names must be identical
Field types that don't sync
- Detail
- Lookup and geolocation
Saving a prospect field mapping
- Detail
- Doesn't trigger a sync with the CRM
New prospect account field mapping
- Detail
- Values don't sync automatically; trigger a full sync
Changing sync behavior
- Detail
- Applies only to future data syncs
Changing global field settings
- Detail
- Doesn't update existing forms; load default data on the form
Opted Out default behavior
- Detail
- Account Engagement value wins by default; most recently updated field is recommended
Sources for this section (6)
- Create Custom Prospect Fieldshelp.salesforce.com (opens in a new tab)
- Map Custom Fieldshelp.salesforce.com (opens in a new tab)
- Create Custom Account Fieldshelp.salesforce.com (opens in a new tab)
- Change Field Sync Behaviorhelp.salesforce.com (opens in a new tab)
- Edit Global Field Settingshelp.salesforce.com (opens in a new tab)
- How Sync Behavior Workshelp.salesforce.com (opens in a new tab)
- Why can a field whose CRM value is primary still push data into the CRM?
- When does the most recently updated field behavior need Field History Tracking?
- Which prospect field type can't be placed on forms or form handlers?
- Which default prospect fields can never be pointed at another CRM field?
- When a predefined value is relabelled, what is stored on the record?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Marketing Cloud Account Engagement Specialist pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 24 lessons of the Marketing Cloud Account Engagement Specialist guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both