Targeting dimensions targeting-dimensions

The targeting dimension, aka. target mapping, is the type of data that an operation is handling. It lets you define the targeted population: profiles, contract beneficiaries, operators, subscribers, etc.

Workflows’ targeting dimensions workflow

The targeting dimension of a workflow is defined by the first Build audience activity and is used across all further activities until the end of the workflow. For example, if you perform a query on the profiles from the database, the outbound transition will contain data of type ‘recipient’ and it will be transmitted to the next activity.

Note that you can switch the targeting dimension in a workflow using a Change dimension activity. This allows you, for example, to query the database on a specific table such as purchases or subscriptions, and then change the targeting dimension to Recipients in order send deliveries to the corresponding profiles.

When selecting a targeting dimension (in the workflow settings, or in activities such as Build audience, Reconciliation or Change dimension), a selection of commonly used schemas is displayed by default in the list. To show all available schemas, toggle on the Show all schemas button. The option selection is saved for each user.

{modal="regular"}

Targeting dimensions list

By default, email and SMS delivery templates target profiles. Their target dimension therefore uses the fields of the nms:recipient table. For Push notifications, the default target dimension is Subscriber applications nms:appSubscriptionRcp, which is linked to the recipients table.

You can also use other built-in target mappings in your workflows and deliveries that are listed below:

Name
Use to
Schema
Recipients
Deliver to profiles / recipients (built-in recipient table)
nms:recipient
Visitors
Deliver to visitors whose profiles have been collected via referral (viral marketing) for ex.
mns:visitor
Subscriptions
Deliver to profiles who are subscribed to an information service such as a newsletter
nms:subscription
Visitor subscriptions
Deliver to visitors who are subscribed to an information service
nms:visitorSub
Operators
Deliver to Adobe Campaign operators
nms:operator
External file
Deliver via a file that contains all information needed for delivery
No linked schema, no target entered
Subscriber applications
Deliver to profiles who are subscribed to an application
nms:appSubscriptionRcp

In addition, you can create a new target mapping depending on your needs. This operation is performed from the client console only. Learn more in Campaign v8 (client console) documentation.

recommendation-more-help
c39c2d00-ba9a-424b-adf9-66af58a0c34b