When targeting recipients based on a custom schema (e.g., policy holders) instead of the default nms:recipient schema, a new targeting dimension must be created. The best practice for this involves creating a new, custom target mapping. This new mapping must reference the custom schema for targeting. Crucially, it also requires the creation of new, custom broadlog and tracking log schemas. These custom log schemas are necessary to correctly link delivery events and user tracking activities back to the records in the custom targeting schema, ensuring data integrity and enabling accurate reporting.

A. Use the out-of-the-box recipient target mapping

This is incorrect because the out-of-the-box mapping is configured to work exclusively with the nms:recipient schema, not the custom policy schema.

C. Modify the out-of-the-box recipient target mapping to use email id from policy

Modifying out-of-the-box components is strongly discouraged as a best practice. Such changes can be overwritten during system upgrades and may lead to instability.

D. Create a custom target mapping using the out of box broadlog and tracking log schemas

This is incorrect because the out-of-the-box log schemas (nms:broadLogRcp, nms:trackingLogRcp) contain a mandatory link to the nms:recipient schema and cannot be used with a different targeting schema.

1. Adobe Experience League - Campaign Classic v7 Documentation

"Creating a new targeting dimension": This guide explicitly outlines the required steps. It states

"To be able to use your new schema as a targeting dimension for deliveries

you must... Create the delivery log schema... Create the tracking log schema... Create the new target mapping." The instructions detail creating new schemas for logs (e.g.

cus:broadLogEx

cus:trackingLogEx) that link to the new custom recipient schema

not the OOTB nms:recipient. This directly supports creating custom log schemas as part of the process. (See Steps 2

3

and 4 in the guide).

2. Adobe Experience League - Campaign Classic v7 Documentation

"Target mapping": This document explains the purpose of target mappings and their components. It specifies that a mapping defines the "schema for delivery logs" and the "schema for tracking logs" for a given targeting dimension. This confirms that the log schemas are an integral part of the mapping definition and must be compatible with the chosen targeting schema.