Interact can utilize the Journey capabilities for continuous communication with users in case of triggered messages. Triggered messages allows the administrators to define event/ event patterns along with other conditions after an offer is made to the users. Interact can facilitate the Journey fields mapping with audience fields and the Offer attributes. The Interact Runtime can trigger communication journey with users by passing the audience details to Journey system through the outbound Kafka channel selected in Triggered Messages screen.
  • The Interact-Journey field mapping can be defined under Gateway tab in Interactive channel, when a gateway of type Journey Outbound is selected. Configuration based mapping is removed and is no longer supported.
  • The outbound channel configured by users is available for selection in the Triggered Messages Channel list.
  • Interact-Journey fields mapping details for all channels is transferred to Interact Runtime through the deployment of interactive channel.
  • The Kafka connection details are required to be configured through the gateway configuration parameters in Interact runtime.
  • If the event or event pattern matches for postEvent Interact API and other conditions of the triggered messages are also met, the system triggers the outbound message with the audience fields as per the Interact-Journey fields mapping through the Journey-Kafka channel.

If required, you can configure a HTTP / SOCKS proxy with authentication between the Interact design-time and Journey. To enable the proxy, add the following JVM parameters and restart the Interact design-time application server:

-Dcom.hcl.interact.journey.proxyProtocol=HTTP or SOCKS 
-Dcom.hcl.interact.journey.<proxyProtocol>.proxyHost=<IP address of the proxy server>
-Dcom.hcl.interact.journey.<proxyProtocol>.proxyPort=<Listening port of the proxy server>

When authentication is required for the proxy server, add the following parameters:

-Dcom.hcl.interact.journey.<proxyProtocol>.proxyUsername=<Username for connecting to the proxy server. Don’t include if no authentication required>
-Dcom.hcl.interact.journey.<proxyProtocol>.proxyPassword=<Password for connecting to the proxy server. Don’t include if no authentication required>
Note: The communication between Interact run-time and Journey passes through Kafka. Hence, the HTTP / SOCKS proxy configuration is not supported.