A Campaign developer configures a delivery with 100 records. After executing the delivery, the developer goes to approve the targeting. The developer sees 100 records as the target count and 90 records as the To Send count.
The Campaign developer needs a detailed listing of the individual records dropped and the reason for exclusion before approving the target.
After opening the delivery, how should the campaign developer perform this task?

Where can a developer configure the archival period of all Delivery Logs?

A client would like to add a new attribute to the Adobe Campaign nms:recipient schema for campaign targeting. How would a developer do this?

A new workflow being built has strict compliance requirements: the workflow's Journal must be archived for
180 clays. The rest of the Adobe Campaign instance must maintain this data for only 30 days.
How would a developer configure the workflow in question to extend the storage of Journal data?

A diem wants to know which email addresses appear more than once in the recipient table. How would a developer determine this?