How to exclude the Lists having different Targeting dimension other than Recipient from the Transactional Messages

[LakshmiPravallika]

Hi

We have two Lists , and both of them have the Targeting dimensions as nms:address and a Red shift Schema.

Note: The data in the Schema is different when compared to the Lists data.

We need to exclude these Lists data from the Transactional Messages.

Please let me know if any solution works for this.

[Rch_]

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,

[LakshmiPravallika]

Hi @Rch_ 

There are no common identifiers to club since the sources of data are different.
The Filtering Typology rule was tried by inserting the list's data into a Custom Schema and then adding this Typology rule in the Template. It have also not worked.

[Rch_]

Hi @LakshmiPravallika,

Did you try RowNum() function (creating a common identifier for both using enrichment and then doing the exclusion)?

Let me know if that worked for you.

Thanks,