Unica Journey integrations

Unica Journey execution engines for email

Unica Journey supports Unica Deliver and Unica Link for email delivery. You can use either for integration with Journey.

Unica Journey integration with Unica Link

Unica Link provides capabilities to send communications across email, SMS, CRM, ADTECH and JDBC channels. Unica Link provides the following reference connectors to deliver communications to email, SMS, CRM, ADTECH and JDBC channels.

Install the following reference connectors as per your preference:

  • MailChimp – for email
  • Mandrill – for email
  • Twilio – for SMS
  • Salesforce – for CRM

Integration with Unica Link allows Journey to integrate with any third-party vendors for email, SMS, CRM, ADTECH and JDBC executions only.

Table 1. Installation and Configuration of Unica Link
Task Documentation
Installation and configuration of Unica Link See Unica Link V12.1 Installation Guide.
Installing Unica Link connector app for Journey See Unica Link V12.1 Installation Guide.
Installing Unica Link connector – MailChimp See Unica Link Mailchimp Connector User Guide.
Installing Unica Link connector – Mandrill See Unica Link Mandrill Connector User Guide.
Installing Unica Link connector – Twilio See Unica Link Twilio Connector User Guide.
Installing Unica Link connector – Salesforce See Unica Link Salesforce Connector User Guide.
Note: HCL does not provide the account or access to these delivery channel vendors. Based on your preference you can get the entitlements or accounts from these vendors.

Unica Journey integration with Unica Deliver

Unica Journey utilizes the capabilities of Unica Deliver for sending email communications. This also helps in capturing the email responses in real-time and process audience Journey. For more details on enabling Unica Deliver integration with Unica Journey, see Unica Journey Installation Guide.

Unica Journey integration with Unica Campaign and Unica Interact

Unica Journey seamlessly integrates with Unica Campaign and Unica Interact. Unica Campaign and Unica Interact sends audience data to Unica Journey on a specific Kafka topic. The audience data is sent through a Kafka entry source and pushed across all journeys consuming data from these entry sources.

For more information on Unica Campaign and Unica Interact integration with Unica Journey, see the guides mentioned in the following documentation map.

Journey supports data from multiple partitions of Campaign

Journey support data from multiple partitions of campaign.
  1. Journey application does not support multiple partitions.
  2. Only data from multiple partitions of Campaign/Interact/Deliver can be processed in Journeys. For this journey, will run on single partition.
You need to make changes in configuration platform and user roles and permission:
  • Campaign flowchart details displayed under the entry sources come from multiple partitions.
  • Based on the partition the Deliver templates are displayed in email / SMS / WhatsApp touchpoints.
Table 2. Integration of Unica Campaign with other HCL products
Task Documentation
Integration of Unica Campaign and Unica Journey See Unica Campaign Administration Guide and Unica Campaign User Guide.
Integration of Unica Campaign and Unica Interact See Unica Interact Administration Guide.

Unica Journey integration with Unica Discover

Unica Journey seamlessly integrates with Unica Discover. Unica Discover sends audience struggle data to Unica Journey. The audience data is sent through REST entry source and pushed across all journeys consuming data from these entry sources. Four scripts will be provided, after installing Journey you need to immediately run the scripts, this will create two entry sources and two data definition called Discover Entry source for CART and Discover Entry source for Form.

DD Name Cart
Description When Customer abandons any kind of cart or set of selected offerings this event can be triggered.
Table 3. Attributes to be sent across
Name Type Length Note
Email* TEXT 200 It is a mandatory field.
Name TEXT 200
DiscoverSessionId TEXT 50 Discover Session id required to link it back.
CartId TEXT 50 Unique id to identify cart.
CartValue NUMBER
EventDateTime TIMESTAMP Date and time of the event in UTC Longitude
EventType TEXT Event Type can be CART_ABANDONED
CookieID TEXT 1024
TLT_BROWSER TEXT 50 Browser details
TLT_MODEL TEXT 50 Device Details
HTTP_ACCEPT_LANGUAGE TEXT 50 Language
DD Name Form
Description When Customer fills any webform this event can be published.
Table 4. Attributes to be sent across
Name Type Length Note
Email* TEXT 200 It is a mandatory field.
Name TEXT 200
DiscoverSessionId TEXT 50 Discover Session id required to link it back.
FormId TEXT 50 Unique id to identify form
FormName TEXT 100
EventDateTime TIMESTAMP Date and time of the event in UTC Longitude
CookieID TEXT 1024
TLT_BROWSER TEXT 50 Browser details
TLT_MODEL TEXT 50 Device Details
HTTP_ACCEPT_LANGUAGE TEXT 50 Language
EventType TEXT Event Type can be FORM_SUBMITTED, FORM_ABANDONED
Note: From Fixpack 3 onwards Unica Journey integration with Unica Discover feature is available.