What is a use case for a custom target mapping in Adobe Campaign Classic?

A custom target mapping in Adobe Campaign Classic is fundamentally used to define a delivery destination other than the default recipient table (nms:recipient). Its primary use case is to enable sending deliveries to profiles whose data, including their delivery address (e.g., email), is stored in a separate, custom table or schema. This is necessary for scenarios such as targeting event attendees, subscribers to a specific service, or any other audience segment managed independently from the main recipient database. The mapping links the delivery process to this custom table, specifying which fields contain the address, recipient ID, and other necessary data.

A. Include seed addresses in the delivery: Seed addresses are a standard delivery feature used for testing and monitoring, and they can be added to any delivery without requiring a custom target mapping.
B. Retarget on the basis of segmentation: Retargeting is a marketing strategy executed via workflows and queries. While it can be applied to audiences in custom tables, the act of retargeting itself does not necessitate creating a custom mapping; the mapping is a prerequisite for targeting the custom table in the first place.

1. Adobe Campaign Classic v7 Documentation, "About target mappings": This document explicitly states, "By default, deliveries are aimed at recipients. But you can also deliver to other types of targets... To do this, you need to create a new target mapping." This confirms that the purpose is to target data stored outside the default recipient table. The section "Creating a new target mapping" details the process, which starts with creating a new data schema (i.e., an individual table).

2. Adobe Campaign Classic v7 Documentation, "Use case: delivering to subscribers": This guide provides a practical example that directly supports the correct answer. It walks through the entire process of creating a custom schema for subscribers (nms:subscribers), populating it, and then creating a new target mapping to enable sending deliveries to this distinct list of individuals stored in their own table. This exemplifies storing addresses in an individual table and using a custom mapping to target them.