Segment references too many data lake objects (DLOs)
Use a Calculated Insight (CI) to reduce the number of DLOs referenced by your segment.
Split a segment into multiple smaller segments.
Segment is too complex.
Use a CI instead of many attributes and nested operators.
Use a CI instead of an attribute (data model object) with many relationships.
Combine text values into one Is In text operator.
Segment returns skewed data.
Remove placeholder values like 0 or Unknown from source data before ingesting data into Data 360.
Segment is inactive.
Copy the inactive segment to create a segment with the same population.
Too many segments are trying to publish at the same time.
Wait for some segments to finish publishing and try again.
Change the publish schedule for some of your segments.
Segment population recount in progress.
Wait for the recount to finish and try publishing the segment again.
Segment wasn’t processed.
Contact Salesforce Customer Support for help.
Multiple population counts are in progress.
Wait for the counts to complete and try again.
Improve the segment by making it simpler, using nested segments, or merging the containers, if possible.
Segment population count failed.
Identify containers with the same join paths and merge them using nested operators, if possible.
Avoid long paths and use the shortest join path to reach the needed attribute.
Avoid cyclic paths in segments. Cyclic paths are relationships that use cyclic behavior (a→b→a). While segment counts can fail, segment jobs can run successfully.
Segment can’t be published.
Simplify your segment by merging containers when possible. Use nested operators to merge the containers.
Ensure the DMO types are correct, especially for Engagement Type data. Incorrect DMO types can cause timeouts and failures.
Unable to edit segment, or segment editor UI times out.
Remove unnecessary relationships defined at Segment On at the DMO level. If the issue persists, contact Salesforce Customer Support for help.
Segment count/population mismatch.
Segmentation applies a filter on the engagement date (24 months for standard segments and 7 days for rapid segments). In Data Explorer, make sure to apply the filter on the engagement event date.
Ensure date operators match with tenant timezones.
Check if the source data has drastically changed (significant additions, updates, or deletions).
If you use Calculated Insights in your segments and notice an unexpected increase or decrease in segment count or segment population, check if any Identity Resolution rules were processed between the CI and segment run.
Segmentation in Data 360 generates a list of unique profile IDs as output. But Marketing Cloud uses the Subscriber Key attribute for segmentation; hence, the population counts in Data 360 and Marketing Cloud can differ.
