DMO reference
Personalization reads and writes several kinds of data underneath the pages in this section. This page maps each kind of data to where you work with it, so you know which page to check for a given question — without restating exact object or field names that need confirming in your own org.
Data this section works with
| Data category | What it holds | Where to work with it |
|---|---|---|
| Profile/identity data | Unified profiles built by Data 360 from your connected sources (web, mobile, CRM, and more), merged into one record per individual. | Identity resolution |
| Engagement/behavioural data | Signals such as views, clicks, add-to-cart and purchase events that recommenders and decisions learn from. | Engagement signals and metrics |
| Decision/log data | A record of each personalization decision run — what fired, what content served, and stage timing. | Personalization logs |
| Attribution data | Which views and points led to outcomes, split by first-touch and last-touch, content and point. | Attribution |
| Experimentation data | Experiment metadata, cohort allocation, per-request logs and summary results. | Experimentation |
To see how incoming data becomes a DMO Personalization can read, see Map DLOs to standard DMOs. For each category above in more depth, see Identity resolution, Engagement signals and metrics, Logs, Attribution and Experimentation.
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).