Best way to get the excluded recipients after a Delivery activity? (Workflow)

[CampaignerForLife]

Hello, 

I would like to know what's the best way to get the excluded recipeints in a delivery activity that is playing in a workflow

Thank you in advance

[ParthaSarathy]

Hi @CampaignerForLife ,

Place a Query activity with targeting & Filtering dimension as Recipient, and apply the below filtering condition:

excludeLog exist such as

[delivery/@deliveryCode] equal to 'yourDeliveryCode'

[Giriprasath-B]

Hi @CampaignerForLife 

 In Adobe Campaign Classic, the recommended and best practice to retrieve excluded recipients from a delivery activity running in a workflow is to use the outbound transitions of the Delivery activity.

---

Recommended Approach

A Delivery activity in a workflow can generate outbound transitions such as:

• Sent

• Excluded

• Rejected

• Errors

To capture excluded recipients:

1. Open the workflow

2. Select the Delivery activity

3. Enable “Generate outbound transitions”

4. Use the Excluded transition

5. Connect it to a Query, List update, or Data extraction activity as needed

The Excluded transition includes all recipients excluded during delivery analysis, such as those excluded due to:

• Typology rules (pressure, fatigue, control rules)

• Quarantine status (invalid or bounced addresses)

• Duplicate detection

• Targeting or filtering conditions

• Blacklists or suppression rules

This method is workflow-native, reliable, and fully supported, and allows excluded recipients to be handled immediately within the same workflow.

---

Note

Querying technical tables such as excludeLog using a delivery code can be used for post-delivery analysis, but it is not considered best practice for workflow execution, as it is less maintainable and not directly tied to the delivery activity’s execution path.

---

Conclusion

✔ Best practice: Use the Excluded outbound transition of the Delivery activity
✔ Fully supported in Adobe Campaign Classic
✔ Avoid relying on technical logs for operational workflows

Thanks,
Giriprasath B