Journey process box

Journey process box enables the marketers to streamline data flow between Campaign and Journey application. Here are the details.
  • Journey process box allows the Campaign users to select the audience data to be sent to Journey (input cells).
  • 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 and are of type Campaign.
  • The View Journey button available on Journey process box allows the users to view the Journeys associated with the selected entry source (ES) and data definition (DD). This Journey process box sends data to the associated Journeys.
  • View Journey button is not enabled, unless users select ES and DD.
  • On selecting data definition, the details of the selected data definition are populated under the Journey fields. This provides details of Journey fields like name, data type, mandatory / significant field on Journeys.
  • Journey process box allows the users to map and generate output from the fields from Journey application as per the data definition selected.
  • While executing the Journey process box, the audience information is sent as per the field mapping to Journey on kafka topic identified with entry source code.
  • Once publishing of audience data is complete, Journey process box execution is marked as complete.
  • The Campaign flowchart designer has access to view the entry source, data definition and only associated Journeys created.

Journey process box - Associated Journeys

This tab lists all the associated journeys as per the selected entry source and data definition. This lists only the associated journeys. The Campaign user gets a quick view of the Journeys in which Campaign audience information is pushed.

Journey process box - Field mapping

This allows the marketers to map Campaign fields which are pushed to Journey’s entry source.

The left pane displays all available fields in Campaign including:
  • Table mapping fields
  • Campaign generated fields
  • User variables
  • Derived fields
  • Extract fields

The users can create derived fields and profile the available fields.

The right pane display fields as per selected data definition. There is a field indicator ( * ) to highlight the Journey field is mandatory.

It provides the ability to the users to map or match the fields. While mapping the fields, datatype of both side fields are not considered. Available field of any datatype can be mapped with journey field of any datatype. e.g. available field of String datatype can be mapped to Journey field of numeric datatype. Execution of Journey process box is successful even with field mappings of mismatched datatype.If the data format is not matched as per the data definition, then audience information would be discarded in Journey.

But mapping of all mandatory journey fields are required, otherwise, Journey process box configuration will not be complete.

Journey process box – General tab

This tab has process box name and Notes field.

Delete Process box

Delete process box deletes the process box. No associated journeys objects are deleted.

Copy Process box

  • The Process box copy operation creates a copy of process box. Copy operation is same at Campaign side.
  • It does not create copies of Entry sources and data definitions associated.
  • Copied process box retains all the information such as associated entry source, data definition, mapped field information, derived fields, or user variables, etc.

Sending Campaign/Flowchart information to Journey

Journey process box allows the users to select and map data as per the data definition. It is important to let Journey know which Campaign or flowchart has sent the audience information to Journey. The Journeys data definition must be created along with CampaignName, CampaignCode, FlowchartName, etc, fields. While mapping the fields Campaign flowchart designer must map the identified fields with the data definition fields. New API is created from campaign to return flowchart information like Campaign Name, Campaign Code, FlowchartName, FlowchartId and Last Run date time. Any changes in this information will be updated as per the Run of respective flowchart.

Note: V12.1 FP3 onwards new API is created from campaign to return flowchart information.

Get Response from Journeys

Campaign marketer would need to include Campaign / flowchart identification information along with the audience information being sent to Journey. This could include any Campaign generated information and audience information. User can pick up the required Campaign generated fields like (but not limited to)

  • CampaginCode
  • CampaignName
  • FlowchartName
  • FlowchartID
  • CellName
  • CellCode
  • AudienceID
  • RunID

Journey will maintain the audience information throughout Journey execution. In Journey flow, marketer can output the data using Publish touch point in flat file. Also, audience information can be outputted in to any database table in Journey application.

Campaign can read this information either from flat file or from respective database tables. Campaign/Flowchart information sent from Campaign would be available in this response. This will help marketer to identify the responses for respective audiences.

Please refer to Journeys User Guide for more information.