Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Sales Performance Management
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Data Cloud Data Sources in Sales Planning

          Data Cloud Data Sources in Sales Planning

          Build sales plans on Data Cloud Data Model Objects (DMOs) and Data Lake Objects (DLOs) in addition to CRM Analytics Data Pipeline datasets. Data Cloud is the foundational data platform across Salesforce, so you reuse data that your org already manages and scale beyond the license limits of Data Pipeline.

          Required Editions

          Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
          Available for an additional cost in: Enterprise, Performance, Unlimited, and Developer Editions with Sales Planning in English only, and only if you have Web Services API enabled

          Why Build Sales Plans on Data Cloud Data

          Data Pipeline includes only 50 licenses per org, regardless of how many Sales Planning licenses you buy. Data Cloud isn't capped this way, so more of your managers collaborate on planning without extra license purchases. Data Cloud data also works across the same Sales Planning capabilities as CRM Analytics data, including segmentation, territory alignment, and stamping.

          CRM Analytics Data Pipeline data sources continue to work, and you use both source types in the same org.

          Note
          Note Data Cloud uses a usage-based model. Records that Sales Planning processes, queries, or analyzes for your sales plans consume Data Cloud service credits. Data Cloud measures and bills this usage separately from your Sales Planning data allowance.

          Segmentation with Data Cloud Data

          After you connect a Data Cloud source, the planning experience works the same as it does with CRM Analytics data. In the Segment Builder, you split segments by specific fields, create segments with AI assistance, and assign records through the record explorer.

          Territory Planning with Data Cloud Data

          Design territories with either live data or copied data.

          • Live data—Design on the latest record data without copying it. Live data supports Report, Query, and Segment data sources, up to 100,000 records and 20 columns at a time. Latitude and longitude fields are optional, but they're required to show individual locations on a map. Territory model queries and aggregation aren't supported with live data.
          • Copied data—Store a static copy of records and their locations in a dataset. Source changes aren't reflected automatically, so define all required fields and geographic boundaries when you create the copy. Copied data counts against your data allocations and supports aggregation and a variety of boundary types.

          To keep underlying data changes from affecting territory carving, stamp the segment before you create the territory plan.

          Segment Stamping

          Stamping creates a frozen dataset that contains only the data from the stamped segment. Stamp a segment to carve territories without ongoing data changes affecting the plan.

          • Stamped datasets are added to the Sales Planning Data app that Data Pipelines configuration creates.
          • When that app doesn't exist, datasets are created in the OAuth user's personal folder, where other users can't access them. Sales Planning tries to move these datasets to the shared app each time you open the plan.
          • Set Up a Data Cloud Data Source
            Use a Data Cloud Data Model Object (DMO) or Data Lake Object (DLO) as the data source for a sales plan. Select the Data Cloud source, choose the columns that you want, and share the data source with the users who need it.
          • Update a Data Cloud Data Source
            When the underlying dataset changes, for example when a field is added in Data Cloud, the new field isn't included automatically. Edit the data source to add the column to your sales plan.
          • Bulk API Behavior for Data Cloud Sources in Territory Planning
            Territory Planning uses a combination of Apex, REST, and Bulk API calls based on your Data Management settings. Use this reference to understand when Bulk API applies to Data Cloud sources and how to estimate the storage that your plans consume.
           
          Loading
          Salesforce Help | Article