Manage target mappings
About target mappings
Each communication channel uses a default target mapping to target their recipients. For example, by default, email and SMS delivery templates target Recipients. Their target mapping therefore uses the fields of the nms:recipient table. For Push notifications, the default target mapping is Subscriber applications (nms:appSubscriptionRcp), which is linked to the recipients table.
Target mappings are accessible from the Administration > Target mappings menu. From this screen, you can access details on each target mapping or create new target mappings to suit your needs.
For more information on the built-in target mappings provided with Adobe Campaign, refer to the Campaign v8 Client console documentation.
Create a target mapping
To create a new target mapping, access the Administration > Target mappings menu. Click the Create mapping button, then follow the steps detailed in the sections below.
-
In the Properties section, enter a Label for the target mapping.
-
Expand the Additional options section to define advanced settings such as the target mapping’s internal name, storage folder, and description.
-
Select the target population. You can either:
- Use the targeting dimension directly: Select the dimension to target directly from the list of available dimensions.
- Use linked data: Start from a targeting dimension (for example subscriptions), and then switch to the targeting dimension that you want to target (for example recipients).
-
If the selected dimension is not already used by an existing target mapping, schemas to store the logs need to be created. Additional options are available in the Storage section. Expand the section below for more details.
Storage options for new targeting dimensions-
Namespace: Identify the namespace that will be used to create the logs.
-
Suffix of the extension schema: Provide a suffix for the new schema.
In the example below, the broadlog name will be “cusbroadlogSupplier”.
-
Delivery logs: Activate the options in this section to enrich the sending logs with a segment code field or a field containing the delivery IP address. For example, save a segment code calculated during the workflow into the sending logs to refine the target later on. This allows targeting profiles with this specific segment code.
-
Exclusions: Specify how to store the exclusions logs.
-
Tracking logs: Activate the Generate a schema for tracking option to generate a storage schema for tracking logs.
-
-
Use the Mapping section to identify which attributes from the target mapping’s schema to use for each delivery address field. For each field, select the desired attribute to map. You can also build an expression to identify the field. For example, apply a lower function to the address attribute.
-
When your target mapping is ready, click the Create button. The system automatically creates the target mapping and all related schemas for the logs.
Once your target mapping has been created, two additional sections display on the screen:
-
Denylisting: This section allows you to identify the attributes from the target mapping’s schema to use for denylists.
-
Storage: This section allows you to identify the tables to use to store logs.
-
Message schema: Identifies the schema to use to store the sending logs.
-
Messages excluded: Specifies how to manage delivery and exclusion logs storage.
- Store exclusions and messages in the same table
- Store messages only: Do not store exclusions.
- Store exclusions and messages in separate tables: Select the schema to use to store exclusion logs in the Rejection schema field.
-
Tracking logs: Choose where to store tracking logs and the default traffic source.
-
Additional fields: Specify a list of additional fields to store in the delivery logs. These fields can permanently store information on individual members of the target (e.g.,
recipient/@firstName) or store additional data calculated during the workflow (e.g.,[targetData/@offeCode]).To do this, select Add field. Identify the information to save in the Source field, and the attribute to use in the sending logs to save this information in the Destination field.
-