Best practices for mapping Salesforce fields to Marketing Cloud Attributes

Best practices

• You only need to map the new Attributes that you create in your account if you want to use them for personalization in your email.
• When mapping Attributes to fields in Salesforce, map to fields of the same Data Type. For example: a Date field in Salesforce should be mapped to a Date field in the Marketing Cloud.
• You can map an Attribute to a Salesforce Account field, however, we don't have rights to edit 'Account' fields in Salesforce. Account fields are not specific to a Subscriber and will not allow this field to be included on the Profile Center. This does not apply to the 'Leads'-related Attributes because a Lead cannot be tied to an 'Account' field, only to a 'Lead' field. 'Lead' and 'Contact'-related fields will show on the Profile center, but 'Account' fields will not.
• If the Salesforce field you are looking for does not appear in the list to select, then that field is not supported by the Integration OR Field Level Security is not set to visible. In either case, you will not be able to map your Attribute to it and you will need to change your field to a supported field type for the Contact, Lead or Account objects.
• If you are attempting to map to a custom field, review the field's security setting and make sure that the System Administrator and any other Marketing Cloud User profiles have visibility set to "Yes."
• Salesforce Sends do not add attribute info within Marketing Cloud Profile Attributes at send time, consider using Imports to populate Profile Attributes for send time personalisation
• The length of the Profile Attribute and Salesforce object's field should match.