Skip to content

Working with Unica Journey

The following steps provide a guide to configuring HCL Discover with Unica Journey using built-in integration. The integration provides Discover with the ability to send data points to Unica Journey when an event occurs.

Tip

Always refer to the official product documentation.

Configure Unica Journey

  1. Setup a Journey Link REST integration, note down the ClientID and Client Secret.

    journey.link.rest

  2. Create an Entry Source, node down your code. This can be either RestAPI or the Discover option.

    journey.entry.source

  3. Create a Data Definition file, again note down the code.

    journey.data.definition

  4. Create a Journey using the Entry Source and Data Definition codes you created in the previous steps.

    journey.integration.journey

Configure Discover

Discover Events

Ensure that the event you wish to use to trigger the integration with Journey is setup correctly and the option Send to Event Bus is enabled. This can be found in the More Options tab when editing/creating your event.

discover.event.managemer.send

Event Bus

Configure CEP for Unica Journey by modifying the Discover DiscoverEventBus.cfg file

  1. Navigate to Discover Services Management - Discover -> Manage Services

    discover.services.management

  2. Expand your Canister/Processing server

  3. Expand the Canister option

  4. Select Event Bus configuration then click on View/Edit

    discover.dms.event.bus

  5. Drag the CEP Session Agent from the Available SessionAgents on the right hand side to the pipeline on the left and place below Decouple

    discover.dms.vent.bus.2

  6. Once in the pipeline click on the new CEP session agent to bring up the configuration

  7. Fill out the following options:

    Key Value
    Journey Entry Source API Client Secret Client Secret from step 1 of the Unica Journey configuration steps
    Journey Entry Source API ClientID ClientID from step 1 of the Unica Journey configuration steps
    Journey Entry Source API Server https://{unica_domain}/journey/api/
    Journey Entry Source Type REST
    Output Type JOURNEY

    discover.dms.vent.bus.3

    discover.dms.vent.bus.4

  8. Click OK then Save

CEP Custom Fields

Configure CEP for Unica Journey by modifying the Discover CEPCustomFields.cfg file

  1. Navigate to Discover Services Management - Discover -> Manage Services

    discover.dms

  2. Expand your Canister/Processing server

  3. Expand the Canister option

  4. Select CEP custom fields configuration file then click on View/Edit

    discover.dms.cep

  5. Scroll to the section titled [Journey] - if there is no section in your file you can use the base configuration provided in the official product documentation

    discover.dms.cep.config

  6. A basic example of the config is as follows:

[Journey]
Type=Journey
# Below is explicit mapping of Journey Events with Discover Event ID, and Journey Entry Source
PRODUCT_ADDED=<Discover_Event_ID>
PRODUCT_REMOVED=<Discover_Event_ID>
ORDER_COMPLETE=<Discover_Event_ID>
ORDER_ABANDONED=<Discover_Event_ID>
FORM_SUBMITTED=<Discover_Event_ID>
FORM_ABANDONED=<Discover_Event_ID>
Journey_Entry_Source_Code=<Journey_Entry_source_Code>

#Below is explicit mapping of Journey data definition fields with Discover traffic attribute
email=<loginid or some other field>
Name=<customer_name>
formId=<form_id>
formname=<form_name>
CartId=<cart_id_field>
CartValue=<cart_value_field>
CookieID=<JSESSIONID>

[Journey]
Type=Journey
# Below is explicit mapping of Journey Events with Discover Event ID, and Journey Entry Source
# Comment out any that are not to be used
#PRODUCT_ADDED=<Discover_Event_ID>
#PRODUCT_REMOVED=<Discover_Event_ID>
#ORDER_COMPLETE=<Discover_Event_ID>
#---StruggleScore Event used for ORDER_ABANDONED mapping---
ORDER_ABANDONED=140
#FORM_SUBMITTED=<Discover_Event_ID>
FORM_ABANDONED=171
Journey_Entry_Source_Code=ES-00000161
# Below is explicit mapping of Journey data definition fields with Discover session attributes
# CustomVarX is the id of the Session Attribute which stores the relevent data 
email=CustomVar3
Name=CustomVar4
forename=CustomVar5
formId= CustomVar1
CartId =CustomVar9
CartValue=CustomVar6