Manage target mappings target-mappings
About target mappings about
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 蜜豆视频 Campaign, refer to the Campaign v8 Client console documentation.
Create a target mapping create-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鈥檚 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: This option allows you to 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, the schemas to store the logs need to be created. To do this, additional options are avaible in the Storage section. Expand the section below for more details.
accordion 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 鈥渃usbroadlogSupplier鈥�.
-
Delivery logs: Activate the options in this section to enrich the sending logs with a segment code field or with a field containing the delivery IP address. For example you can save a segment code calculated during the workflow into the sending logs in order to refine the target later on. This will allow you to target profiles having this specific segment code.
-
Exclusions: Specify how you want 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鈥檚 schema to use for each delivery address fields. For each field, select the desired attribute to map. You can also build an expression to identify the field. For example, you can apply a lower function to the address attribute.
-
When your target mapping is ready, click the Create button. The systems automatically creates the target mapping and all the related schemas for the logs.
Once your target mapping has been created, two additional sections display in the screen:
-
Denylisting: This section allows you to identify the attributes from the target mapping鈥檚 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: This section 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: This section allows you to specify a list of additional fields to store into the delivery logs. These fields can permanently store information on individual members of the target (eg.
recipient/@firstName) or store additional data calculated during the workflow (eg.[targetData/@offeCode])To do this, select Add field. Identify the information you want to save in the Source field, and the attribute to use in the sending logs to save this information in the Destination field.
-