How does the Campaign Monitor preference center work with the Salesforce integration?

Campaign Monitor has a preference center feature. It will allow a subscriber to update custom field values stored in Campaign Monitor.

Mapping Preference Center Fields to Salesforce

If you need these changes to flow back to Salesforce, field mappings in the direction of Campaign Monitor to Salesforce will update the contacts related to subscribers when the primary sync runs (by default hourly).  

For these fields, Campaign Monitor really becomes the source of truth. Preference center fields are updated by the subscriber in Campaign Monitor and synced back to Salesforce via field mappings. Field mappings can only map a specific field in one direction.

Salesforce to Campaign Monitor

If you have the less common need to also update the same fields in Salesforce and push those to Campaign Monitor, you can use our import wizard. The wizard has its own independent built-in field mappings feature and can be scheduled up to hourly.

Note: There is no logic to compare field values when importing, so plan the interaction of field mappings (CM>SF) and the wizard timing well. When setting up the source for the import wizard, we suggest including a filter to ensure that it only contains recently modified records, as well. Another option is to map the preference center fields to scratch fields in Salesforce, and add your own custom automation to map the data with any logic needed.

Email Changes

The email field is a bit different than the custom fields you can add to Campaign Monitor to collect other information. If you allow members to update their email on the preference center, you will want to consider the following:

• Email changes made in Campaign Monitor won't automatically change the Email on a related contact and will create two subscriber records in Salesforce (original and new email- More info).
• Using our optional Salesforce ID match override doesn't handle the above. It will connect the new subscriber record to the right contact, but the contact will still have two subscribers in Salesforce.
• To clean up the old subscriber record, consider using the advanced options on the import wizard to delete the old email on the next import (since the old email will fall off the source). Again. plan and test this carefully!
• A more robust option would be to create a custom text field in Campaign Monitor for the preference center email change and to map this to a Salesforce scratch field, instead of the standard Email field. Custom automation can then add whatever logic you need to move the updated preference center value to the standard Email field (which will trigger our field mapping on Email)

Note that we can't support custom configuration like this, but we are happy to recommend a consulting partner.