Journey interaction logging

Interaction Logging for Journey is executed as a scheduled job. The scheduling parameters are set in application.properties file of the Journey Engine. The following is an example of the setting:

engine.logging.cron=0 15 3 * * ?

The scheduled job exports data into an alternative schema which is defined again in the application.properties files of the Journey Engine.

journey.report.datasource.url =
journey.report.datasource.username =
journey.report.datasource.password =
journey.report.datasource.driver-class-name=

Interaction Logging captures the movement of every contact that enters the Journey application as they move through each Journey, either Published or Completed. Even journeys that are Published but Paused are considered for the Interaction Logging.

All Touchpoints, Email, SMS, or CRM, are considered for Interaction Logging as the audience data is sent using the configured integrations through the respective channels. The responses received, from every contact, is also captured.

Log4j2

Both Journey Web and Journey Engine uses the standard for logging. The log4j2.xml file, for both Journey Web and Journey Engine, is placed within the conf folder in the installation location.

Both Journey Web and Journey Engine produce regular application logs as well as performance logs. For Journey Web, the default location of the logs is within the logs folder. For Journey Engine, the default location of the logs is within the performancelogs folder. For both Journey Web and Journey Engine, the mentioned folders are placed within the installation location.