A Data Cloud Consultant is mapping ingested CRM Contact data to the Individual Data Model Object (DMO). During the mapping process, they need to map a custom text field containing customer loyalty status. Where should this custom field be mapped if no standard DMO field exists for it?
Trap 1: It must be left unmapped because custom fields are not supported on…
Custom fields are fully supported on standard DMOs.
Trap 2: It must be stored inside a Calculated Insight.
Calculated Insights are for metrics, not raw attribute mapping.
- A
It must be mapped to a custom field created on the Individual DMO.
Custom attributes that lack standard equivalents should be mapped to custom fields created on the standard DMO.
- B
It must be left unmapped because custom fields are not supported on standard DMOs.
Why wrong: Custom fields are fully supported on standard DMOs.
- C
It must be mapped directly to the Data Lake Object schema.
Data streams map from DLO to DMO, not back to the DLO.
- D
It must be stored inside a Calculated Insight.
Why wrong: Calculated Insights are for metrics, not raw attribute mapping.