Loading
Prepare for Email to Become the Default Login ExperienceRead More
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
Sales Innovations for Prospect Management
Create Actionable Lists with Data 360 Data Model Objects

You are here:

  1. Salesforce Help
  2. Docs
  3. Sales Innovations for Industries Clouds

Create Actionable Lists with Data 360 Data Model Objects

Filter and curate lists by using fields from a Data 360 data model object (DMO), which can combine your CRM data with enriched external data. You see additional fields from external systems on each record without writing that data to CRM.

Actionable List with Data 360 data model objects extends Actionable Segmentation to include fields from Data 360 Data Model Objects (DMOs). Build lists directly from a Data 360 DMO, which can combine your CRM data with enriched external data, such as usage metrics, engagement scores, and account health indicators.

Instead of selecting a pre-built segment, you filter directly on DMO fields, so your admin doesn't need to pre-build a segment for every use case. Because lists build directly from DMO data, they aren't bound by the lower list-volume limit that applies to segment-based lists.

DMO field values serve only as criteria for filtering and list membership. They're never written back to CRM records. For example, you curate a list of records whose external metric exceeds a threshold, without that value ever being stored on the Account record.

Why Use Data 360 Data Model Objects

Often, the data you need to act on lives outside CRM, such as account balances, usage metrics, or transaction history in an external system. This data is volatile and sensitive. Copying it onto CRM records increases database bloat and compliance risk, so most organizations model it externally instead.

With Data 360, you ingest and model that external data as a data model object, and a data transform combines it with your CRM data. Filtering happens directly on the DMO to build the list. The external values appear in the list builder for review, but only standard CRM references are stored as actionable list members. This keeps your CRM data clean while you act on external field values alongside it.

How Actionable Lists with Data 360 DMOs Work

Each list draws on a Data 360 DMO. The DMO can hold data from a single source, or it can combine data from several sources into one DMO with a data transform. To build or prepare a DMO, see Prepare Data 360 Data Model Objects for Actionable Lists.

Your Salesforce admin creates an Actionable List Definition that connects a Data 360 DMO to a CRM source object and sets the fields and member statuses that you can use.

From a saved definition, you create an actionable list, apply filters to refine which records to include, and save the list.

For example, a team wants to reach out to accounts whose product usage is declining. The usage data lives in an external system, so an admin combines it with Account records in a DMO and creates a definition on the Account object. A user then builds a list and filters it to accounts with a low usage score. The list includes those accounts for outreach, but the usage score is never written to the Account record.

Each actionable list contains actionable list members, one for each record in the list. To learn how access to a list and its members is determined, see How Actionable List Sharing Works.

 
Loading
Salesforce Help | Article