Data mapping

Every connector lands raw data in data lake objects (DLOs) — tables shaped however the source system sends them. Personalization doesn’t read DLOs directly; it reads data model objects (DMOs), Data 360’s standardized schema. Data mapping is the step that connects the two: you tell Data 360 which DLO field fills which DMO field, so identity resolution, segmentation, and personalization all see consistent, predictable data no matter which connector the data came from.

In this section

Discussion

Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).

Support SF Guide

SF Guide is a free, independent guide to Salesforce Personalization, built and maintained in the open. If it saved you time on an implementation, a small contribution helps keep it current and ad-light.