Configuring Publish

Use the Publish orachastration to save contact details at a particular stage. You can use these contact details for analytics, reusing the CSV files and Kafka Entry source in other Journeys, or other actions.

About this task

To configure a Publish control, complete the following steps:

Publish control gathers audience information at a particular stage and posts this information to a CSV file, a Kafka Entry source, or a Kafka topic. The file will be saved in the Journey server (engine). The file path is configured in the spring.entity.files.upload.defaultPath property inside the application.properties file of the Journey engine and the Journey web, and the paths should be the same in the Journey engine as well as the Journey web. The default output location of the Journey files is <JOURNEY_ENGINE_HOME>/Files.

Procedure

  1. From the Journey control panel within the Palette, drag-and-drop the Publish control to the required part on Canvas.
    The Publish dialog appears.
  2. Provide values for the following fields:
    • Name - Mandatory
    • Description - Optional
  3. Select one of the following options to save the contacts:
    • CSV - The fields configured in Data Definition is exported to the CSV file. You can either provide a new CSV file name or type in the name of an existing CSV file. If you select an existing file, the data will be appended to the existing file.
    • Kafka > Entry Source - With a single Publish control, you can configure a maximum of 10 Kafka entry sources. Kafka entry sources, associated with Journeys, will not be listed while configuring the Kafka entry source on the Publish journey control. For a Journey, if a Kafka Entry Source is configured with a Publish Journey Control, and if that same Kafka Entry Source is associated with any other Journey, the data gets processed for the selected Journey as per the configured Data Definition.
    • Kafka > Topic - Posts audience information on a Kafka topic for use by third-party applications. Provide an appropriate name for the topic. The topic is stored on the Kafka server. A Kafka topic name can be up to 50 characters in length and should have A-Z, a-z, 0-9, period (.), underscore (_), and hyphen (-).
      Note: When user wants to use multiple kafka brokers and they start their engine with single kafka borker, then topics by default get created on this single broker. Later, when user updates the broker list then kafka doesn’t replicate the topics on other brokers because at the time of installation the replication value was set to one.

      Hence, during installation only, user needs to specify whether they want to use kafka with multiple brokers or with single broker.

  4. Add Offers - Check the checkbox I want to associate Offers to this touchpoint
    Select Offers button will get enabled.
  5. Click on Select Offers.
  6. The Offers screen from Centralized Offer Management appears. User can select one or multiple offers from the list of offers displayed or double click on the offer to select from the offer variant.
  7. From Select Channel of communication dropdown, select the required communication channel.
  8. Click on Done.
    Note: CH will be updated for orchestration point as soon as the record is outputted into and treatment code can be generated with same attribute.
    Note: On Publish Touchpoint, Select Offers button will be enabled only when user sets the partition setting for the Journey.
    Note: User is only able to configure Offer with Publish Touchpoint with CSV and Kafka Topic. User is not able configure Publish Touchpoint with Kafka Entry source.