When you access the Field Mappings tab, Acoustic Campaign makes a dynamic call to SFDC and obtains all your standard and custom fields from SFDC and groups them by section. You can collapse and expand the sections as needed. You need to provide mappings for Leads, Contacts, and Accounts. You can see the SFDC fields that are associated with each tab and match them with existing Acoustic Campaign fields and the fields you create.
Acoustic Campaign fields may be mapped twice, using a supported combination. For instance, if the Acoustic Campaign field is already mapped to the Lead and Contact it will not appear as an option to map for Accounts.
Below is the field mapping combination that Acoustic Campaign currently supports:
- Acoustic Campaignfield mapped to a Lead and a Contact
- Acoustic Campaignfield mapped to a Lead and an Account
The combination that is not supported is an Acoustic Campaign field being mapped to a Contact and an Account. This is not possible because account fields accompany the Contact when syncing, so if you have ready mapped the Acoustic Campaign field on the Contact you cannot map an Account field to the same Acoustic Campaign field.
If you need to have this data from the third object in which the field is not currently mapped, it is recommended to create a new field to map to this object.