is_delete flag check during engagement

[Pradeep-Jaiswal]

Cx profile can have is_delete flas as false during the audience creation, but if Cx profile has entered in the journey and currently paused at WAIT journey touchpoint, then we can check is_delete one more time before sending the engagement email/sms/push etc. But this check would be required everytime before we send the engagement communication in the journey., and increase the touchpoint count in journey canvas. is there a way this logic of is_delete can be embded in the channel configuration level, so that we dont need to explicitly check for this flag evertime in the journey before sending engagement?

[Mohan_Dugganab]

Consent policies can be leveraged in your case https://experienceleague.adobe.com/en/docs/journey-optimizer/using/privacy/consent/consent 

Note - Consent policies are currently only available for organizations that have purchased the Adobe Healthcare Shield or Privacy and Security Shield add-on offerings.

[Mayank_Gandhi]

@Pradeep-Jaiswal No, today there is no generic, per‑channel configuration switch in AJO where you can say “always check is_delete before sending” and have that logic applied automatically for every email/SMS/push. You still need to implement the exclusion logic in the journey, or move it into a reusable pattern.

However, there are a few practical patterns that can get you close to “set once, reuse everywhere.”

 Treat is_delete as a consent policy .

If the semantics are “this profile must never receive marketing*”, you can:

1. Map is_delete into the consent model, e.g.
   • when is_delete = true, set consents.marketing.email.val = "n", consents.marketing.sms.val = "n", etc.
2. Ensure all marketing surfaces use marketing actions that are enforced by consent policies.

Result:

• Once the flag is reflected in the consent fields, AJO’s message runtime will suppress automatically at send time, the same as a normal unsubscribe, without any journey‑level splits.

This is the closest thing we have to “embed at channel configuration level” for a boolean flag.

[Pradeep-Jaiswal]

Thank you. This seems great alternative of translating is_delete flag into consent value.

1) How do we ensure all marketing surfaces use marketing actions that are enforced by consent policies ?

2) Similarly is there any possibility to automatically exclude all profiles from the audience without building an exclusion logic into each individual audience definition ? Something that can be done at global level , rather than each audience ?