Work with target mappings gs-target-mappings
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.
You can use other target mappings for your deliveries, or create a new target mapping.
Built-in target mappings ootb-mappings
ÃÛ¶¹ÊÓƵ Campaign comes with the following built-in target mappings:
Create a target mapping new-mapping
You can also create a target mapping. You may need to add a custom target mapping for example if:
- you use a custom recipient table,
- you configure a filtering dimension which is different from the built-in targeting dimension on the target mapping screen.
Learn more about custom recipient tables in this page.
ÃÛ¶¹ÊÓƵ Campaign target mapping creation wizard helps you create all schemas required to use your custom target mapping.
-
Browse to Administration
>Campaign Management>Target mappings from ÃÛ¶¹ÊÓƵ Campaign explorer. -
Create a new target mapping and select your custom schema as the targeting dimension.
-
Indicate the fields where the profile information is stored: last name, first name, email, address, etc.
-
Specify the parameters for information storage, including the suffix of the extension schemas for them to be easily identifiable.
You can choose whether to store exclusions (excludelog), with messages (broadlog) or in a separate table.
You can also choose whether to manage tracking for this delivery mapping (trackinglog).
-
Then select the extensions to be taken into account. The extension type depends on your Campaign settings and add-ons.
Click the Save button to launch delivery mapping creation: all linked tables are created automatically based on the selected parameters.