Overview

Interact can utilize the Deliver capabilities to continuously communicate with users through triggered messages. Triggered messages allows the administrators to define event or event patterns along with other conditions for an offer to be made to the users.

Interact allows the administrators to select the type of message and the required Deliver template under the Source tab. Currently, email, SMS, MobileApp, and WhatsApp messages are supported. The Deliver fields present in the template can be mapped to the Interact audience fields and Offer attributes.

The Interact runtime can trigger communication message for the users with the personalized field values to Deliver system through the outbound channel selected in the Triggered Messages screen.

  • The Interact-Deliver field mapping can be defined under Gateway tab in Interactive channel, when a gateway of type Deliver Outbound is selected.
  • The Deliver fields present for mapping are based on the source type and the associated Deliver document selected. Users can create the template from Deliver Messaging Editor and Quick Builder tabs.
  • The outbound channel configured by users is available for selection in the Triggered Messages Channel list.
  • Interact-Deliver fields mapping details for all channels is transferred to Interact Runtime through the deployment of interactive channel.
  • The Deliver TMS API connection details are required to be configured through the Deliver template in Interact runtime.
If the event or event pattern matches the postEvent Interact API and other conditions of the triggered messages are also met, the system triggers the outbound message with the personalized audience fields and offer attributes as per the Interact-Deliver fields mapping through the Deliver channel.

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


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

Add the following parameters when authentication is required for the proxy server:


-Dcom.hcl.interact.deliver.<proxyProtocol>.proxyUsername=<Username for connecting to the proxy server. Don’t include if no authentication required>
-Dcom.hcl.interact.deliver.<proxyProtocol>.proxyPassword=<Password for connecting to the proxy server. Don’t include if no authentication required>
To enable the proxy at the run-time, add parameters in the Deliver gateway Platform configuration or add the following JVM parameters:
Note: JVM parameters will override all the proxy values defined in the Platform configuration.

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

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


-Dcom.hcl.interact.tms.<proxyProtocol>.proxyUsername=<Username for connecting to the proxy server. Don’t include if no authentication required>
-Dcom.hcl.interact.tms.<proxyProtocol>.proxyPassword=<Password for connecting to the proxy server. Don’t include if no authentication required>

Restart the Interact run-time application server after adding the JVM parameters.