Interact-Journey fields mapping

Interact provides a mechanism to map the Interact and Journey fields and identify the information to be sent. This Journey fields mappings can be defined on Gateway tab of an interactive channel, when Journey Outbound option is selected. These Journey fields mappings can be defined on Gateway tab of an interactive channel, when Journey Outbound option is selected. Configuration based mapping is removed and is no longer supported.

Journey details (Prior to version 12.1.0.3)

A category called “Journey” is available under outboundChannels, which defines the Interact Journey mapping information.

Journey category has the following parameters:
  • New Category Name: The configuration name.
  • Name: The outbound channel name that appears in the Triggered Messages list.
  • EntrySourceCode: This is a Journey specific mandatory field that identifies the source of the incoming data and triggers one or more journeys. EntrySourceCode is a part of the outbound message from Interact to Journey.
  • DataDefinition: The data definition name for this mapping. This field is only for information purposes in Interact so that the users can identify the fieldMappings. The field is not used in Interact for message processing.

Field mapping

Once the Journey basic details are saved, a new category named “FieldMapping” is displayed under Journey.

The FieldMapping category replicates the data definition in Journey. The category allows to define a Journey field similar to data definition field in Journey.

New Category Name: The Interact field name which is mapped against this Journey field. The format of the Interact field name is “Prefix.fieldname” and it is case insensitive for Interact. The field names on Journey side are case sensitive, hence ensure that the matching case is used for field mapping. The prefix can have two possible values.
  • OFFER – If the Journey field is mapped against an Offer attribute, the fieldname/ attribute name must be prefixed with “OFFER”.
  • PROFILE – If the Journey field is mapped against a profile attribute, the Interact field name must be prefixed with “PROFILE”.
Note: Real-time attributes and session parameters must also be considered profile attributes and must be prefixed with “PROFILE”

The Interact fields/parameters/attributes which are not offer specific must be prefixed with “PROFILE”.

FieldName:The Journey field name to which the value of the above-mentioned Interact field is mapped to and sent to Journey through an outbound message. The Journey field name mentioned here is part of the outbound messages.

DataType: There are three data types to select from, similar to Journey Data definition.
  • String
  • Numeric
  • Datetime

The data type is used to validate and format the Interact field value before sending it to Journey.

DefaultValue: If the Interact field value is not available, the system assigns the default value to the Journey field.

Mandatory: Interact runtime validates if the Journey field is defined as mandatory. If the field is defined as mandatory, and the corresponding Interact field value is not available, an error is logged and the message is discarded.

Note: If defaultValue is defined for such field, system uses the default value rather than discarding the outbound message.

DatetimeFormat: This property is only applicable for datetime data type. This is the datetime format, which formats the Interact field value.

MaxLength: This property is only applicable to string data type. This provides an additional validation to the field value. If MaxLength is defined and the corresponding Interact field value exceeds MaxLength, an error is logged and the message is discarded.

Users must configure a field mapping for each Journey field, which is a part of the outbound message to Journey.

You can define the Interact-Journey field mappings using the Journey Outbound options available under Gateway tab in Interactive Channel.
  • It allows the marketers to select the existing data definition from Journey.
  • It enables the users to select the entry sources which exists in Journeys of type Unica Interact.
  • After Entry Source and data definition is selected, on clicking the Retrieve button, the details of the selected data definition populated under the Journey fields are displayed. This provides details of Journey fields like name, data type, mandatory / significant field on Journeys.
  • For the Journey field, users can map the Interact fields. These can either be the Profile field, RTA or the Offer attribute from Interact.
  • If the Journey field is mandatory, then the default value is required. In case, the value cannot be retrieved from Interact fields on Runtime side, the default value is used and sent to Journey.

Triggered messages

The Triggered messages screen lists the available outbound channels to select. The Journey outbound channels are also visible in the Triggered Messages Channels list.