Hi @lakshmipravallika,
Since your transactional messages are targeted using nms:recipient, and the lists you’d like to exclude are based on different schemas (nms:address and a Redshift schema), you won’t be able to reference them directly in the delivery for exclusions.
Instead, use this approach:
- Extract the relevant identifiers (e.g., email addresses or customer IDs) from both exclusion sources.
- Consolidate them into a single exclusion list using a custom schema (e.g., cus:exclusionList).
- In your transactional workflow, add a filter or typology rule that checks against this list — for example, by excluding any recipients whose email is found in the list.
This method helps align the data across schemas and ensures clean exclusions without breaking targeting dimension rules.
Let me know if this approach works for you.
Thanks,