Ingest source data via an Ingestion API connector or a CRM connector; this automatically creates a DLO representing the raw incoming schema.
In Data Cloud Setup, go to Data Streams, open the stream, and click the Data Mapper tab to open the DLO-to-DMO mapping interface.
On the left panel, select the DLO and choose a target DMO category (Profile, Engagement, or Other); then select the specific standard or custom DMO to map into.
Map each DLO field to its corresponding DMO field by dragging or selecting from the right-hand dropdown; required fields on the DMO (such as ssot__DataSourceObjectId__c) must be mapped for the DMO to function.
Save and activate the mapping; Data Cloud will begin transforming and writing DLO records into the DMO on the next scheduled refresh or on demand.
Validate the mapping by querying the target DMO via the Data Cloud Query API and confirming that record counts and field values match expectations.
Known gotchas
A single DLO can be mapped to multiple DMOs, but each DMO field can only be sourced from one DLO field per mapping — define separate mappings if you need to merge multiple DLOs into one DMO.
Changing an active mapping resets DMO data for that stream and triggers a full re-ingestion; plan mapping changes during a maintenance window.
The primary key field on the DMO must be mapped to a DLO field whose values are stable and unique across source records, otherwise identity resolution will create duplicates.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp