Configure mappings
- Karl Tompson
Mapping metadata
Mappings are stored in Salesforce and determine how Leads or Contacts are identified, and how data should be copied back and forth between Salesforce and Sitecore CDP & Personalize.
Mappings are created as CDP4SMapping__c custom objects. CDP4S provides a convenient GUI to manage mappings.
Description of fields:
Guest Field: references the property in the Sitecore JSON Guest object. Note this allows complex nesting. Literal values can also be used by enclosing in curly braces ‘{}’; the enclosed text will be parsed as JSON so numbers and boolean values are correctly typed.
Salesforce Field: the API name of the field on the Guest or master object in Salesforce.
Mapping Type: determines the function of the mapping as below.
Mapping types
Identity is a special type that indicates the value should be used to locate an existing object. An error will occur if this property has no value.
Type | Sitecore > Salesforce | Salesforce > Sitecore |
|---|---|---|
Identity | Used for new object only | Not updated |
Personalize only | Not updated | Always updated |
Default value | Only if existing value is empty | Not updated |
Default value and Personalize | Only if existing value is empty | Always updated |
Always update | Always updated | Not updated |
Always update and Personalize | Always updated | Always updated |
You may create multiple mappings for the same field if required to achieve the desired results.
Object types
The mappings always apply to the object type inferred by the Master Lookup Field setting, which may be a Lead, Contact, any other standard or custom object, or Sitecore_CDP_Guest__c if none specified. If the master object is a Lead and conversion handling is enabled, CDP4S will attempt to map to the resulting Contact.
Fields that do not exist on the target object will be ignored, except in the case of Identity mappings.