Why does my Selection returns zero results?

A DESelect selection returning 0 results is usually not a system error — it’s a signal that the SQL logic generated by your segmentation criteria didn’t match any records. Whether due to filters, joins, primary key deduplication, or data visibility, taking a step-by-step approach to validating your selection logic and data will lead you to the root cause.

Please see the steps below how you can validate the Selection.

1. Selection Isn’t Constructed Correctly
DESelect builds an underlying SQL query based on the filters, relationships, and joins you define. If your logic has issues — such as combining filters incorrectly (e.g., conflicting AND/OR conditions) or referencing fields without a proper relationship — the result can be an empty result set.
Unlike a failed query that shows an error, this type of issue still runs successfully in SFMC — but simply returns no data because nothing matches your criteria.

What to check:
- Are all the Data Extensions you referenced included in the Selected Data Extensions?
- Do all filters reference fields from included tables?
- Are your joins logical (e.g., correct fields and match types)?

2. Primary Keys & Deduplication Logic Removing Results
DESelect Segment respects primary keys defined on data extensions by default. When duplicate records are removed by deduplication logic, you may see fewer results than expected — and in edge cases (e.g., if the only matching records are removed by your key logic), 0 results.

3. Data Is Filtered Out by Your Criteria
It might seem obvious, but often a Selection returns nothing because no records actually meet the filters you applied — especially when multiple conditions are combined with AND logic. For example, if you filter for customers who both purchased Product A and Product B, but no records satisfy both, you’ll get 0 rows.
This is especially common when working with complex filters or subquery filters like “In Results / Not In Results.” Carefully double-checking values, date ranges, and logical groupings can often reveal that the data simply doesn’t exist for the selected criteria. 

4. Join Logic Excludes All Matches
When multiple Data Extensions are linked, the join types you choose (inner, left, etc.) directly impact results. An inner join requires matching rows in both tables — if there’s no match, you’ll get 0 records.
For example, if you join DE A and DE B on a key that doesn’t match any values, the result is empty. Reviewing your join fields and ensuring the selected tables actually share real matching values is critical.

5. Advanced Filtering Edge Cases
There are specific filter behaviors (e.g., “Not Contains,” certain OR + AND combinations, relative date logic) that can introduce additional unexpected filtering. In some cases, DESelect adds extra conditions to the underlying SQL (like OR field IS NULL when using certain filters) that can unintentionally exclude records from the final result. Carefully reviewing how your filters behave helps catch these edge cases.
If the issue persists, contact Support with screenshots of your selection setup and Target Data Extension structure for faster investigation.

If the issue persists, contact Support with screenshots of your selection setup and Target Data Extension structure for faster investigation.