Typology rule filtering for transactional emails

Hi ​@SkylerQu2 

Have a look to the following documentation. Based on the steps, looks like you have to add it to the message schema (nms:tmpBroadcast)

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-43530

Once updated, be sure to republish transactionals so the changes take effect. 

If you don’t solve it, don’t hesitate to come back. 

Kind regards, 

Celia Castilla

Hello Mate,

This looks like a Campaign Classic / Managed Cloud setup. The likely issue is the rule’s targeting schema: Adobe’s guidance for this transactional-email filter uses Message (nms:tmpBroadcast), not rtEvent, address, or recipient.

Configure a new filtering rule with:

• Type: Filtering
• Channel: Email
• Schema: Message (nms:tmpBroadcast)
• Condition: exclude messages whose address is not in your allowed domain(s). Adobe’s example for allowing @example.com is [address does not contain 'example.com'].

Then add the rule to the Transactional message typology used by the template and republish the associated transactional template(s). Test with one allowed address and one disallowed address, and confirm the excluded message appears in the delivery analysis/logs.

About the RT instance: Transactional messages are sent on the execution (RT) instance, so the updated template/rule must reach the instance that sends them. The guidance is to update the typology and republish the template, then verify the published version is active on the execution instance—not to rely on a rule that exists only in another schema or an unpublished template.

For a strict allowlist, prefer an exact domain-suffix check (for example, ending in @example.com) if the condition editor supports it; a simple “contains” check can also match addresses with the allowed text embedded in a different domain. 

Trt it out. 

Cheers,

Nikhil Kalladithodi