Integrating Unica Discover and Unica Journey

Unica Discover and Unica Journey integration works with CEP configuration. The CEP configuration enables the event to be sent to CEP and the external systems. Unica Discover-Unica Journey integration is supported from version 12.1.0.3 onwards.

To integrate Unica Discover and Unica Journey, complete the following procedures:

Activating Enable Event bus

Procedure

  1. In the Discover Portal UI, select Discover > Managed Services.
    The Discover Services Management page appears.
  2. Expand Canister.
  3. Select Canister configuration (xxxxx) (Registry).
  4. Within the Config Actions section, select View/Edit.
    The Discover Canister Config popup appears.
  5. Select Services Perform > Event Bus
  6. Enable Enable Event Bus.

Activating Send to Event Bus

Procedure

  1. In the Discover Portal UI, select Event > Manage Events.
    The Event Manager page appears.
  2. Locate the required event by using filters and filtering the values based on Name or ID.
  3. To edit an event, perform one of the following actions:
    1. Double-click the event.
    2. Right-click the event and select Edit Event.
  4. Select More options.
  5. Enable Send to Event Bus.

Configuring DiscoverEventBus.cfg

Procedure

  1. In the Discover Portal UI, select Discover > Managed Services.
    The Discover Services Management page appears.
  2. Expand Canister.
  3. Select Event Bus configuration (xxxxx) (Registry).
  4. Within the Config Actions section, select View/Edit.
    The Pipeline Editor - Event Bus configuration (xxxxx) popup appears.
  5. If CEP does not exist in the Event Bus configuration panel, drag-and-drop CEP from the Available SessionAgents panel to the Event Bus configuration panel. Ensure that you drop CEP after the Decouple option and before the Null option.
  6. Select CEP.
    The Edit Session Agent:CEP popup appears.
  7. For the OutputType field select JOURNEY.
  8. Click Apply.

Configuring REST type of Entry Source

Procedure

  1. Select Journey Entry Source Type REST and click Apply.
  2. Enter Journey Entry Source API Server URL and click Apply. For example, http://localhost:8080/journey/api/
  3. Enter Journey Entry Source API Client ID and click Apply.
  4. Enter Journey Entry Source API Client Secret and click Apply.

Configuring Unica Discover / Kafka type of Entry Source

Procedure

  1. Select Journey Entry Source Type Kafka and click Apply.
  2. Enter Journey Entry Source Kafka Server / Broker, along with the port number for listening, and click Apply. For example, localhost:9092
  3. Enter Journey Entry Source Kafka Security Type.

Configurations applicable when Entry Source Kafka Security Type selected is SASL_PLAINTEXT

Procedure

  1. Enter the Journey Entry Source Type Kafka SASL User and click Apply.
  2. Enter the Journey Entry Source Type Kafka SASL Password and click Apply.

Configurations applicable when Entry Source Kafka Security Type selected is SSL

Procedure

  1. Enter the Journey Entry Source Type Kafka SSL Cert location and click Apply. For example, C:\KSSLCert\client_cert.pem.
  2. Enter the Journey Entry Source Type SSL CA location and click Apply. For example, C:\HCL\KSSLCert\ca-cert.
  3. Enter the Journey Entry Source Type SSL Key location and click Apply. For example, C:\HCL\KSSLCert\client_key.pem.

Configurations applicable when Entry Source Kafka Security Type selected is SASL_SSL

Procedure

  1. Enter the Journey Entry Source Type Kafka SASL User and click Apply.
  2. Enter the Journey Entry Source Type Kafka SASL Password and click Apply.
  3. Enter the Journey Entry Source Type Kafka SSL Cert location and click Apply. For example, C:\KSSLCert\client_cert.pem.
  4. Enter the Journey Entry Source Type SSL CA location and click Apply. For example, C:\HCL\KSSLCert\ca-cert.
  5. Enter the Journey Entry Source Type SSL Key location and click Apply. For example, C:\HCL\KSSLCert\client_key.pem.

Configuring CEPCustomFields.cfg

Procedure

  1. In the Discover Portal UI, select Discover > Managed Services.
    The Discover Services Management page appears.
  2. Expand Canister.
  3. Select CEP custom fields configuration file xxxxx) (CEPCustomFields.cfg).
  4. Within the Config Actions section, select View/Edit.
    The CEP custom fields configuration file xxxxx) (CEPCustomFields.cfg) popup appears.
  5. Add the following properties at the end:
    
    [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>
  6. Access Portal > Event Manager to fetch the Event ID. Modify the Journey Section and specify the Discover Event ID for each of the following events:
    
    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>
  7. Provide a value for Journey_Entry_Source_Code=<Journey_Entry_source_Code>.
    For example,
    Journey_Entry_Source_Code=ES-0000005
    Note: If you are not mapping all event IDs, ensure that you enter all the details correctly. If a Discover Event is followed by a Journey Entry Source Code, ensure that the Discover Event has an EventID. For example, if you want to map ORDER_COMPLETE and not ORDER_ABANDONED, the incorrect format and correct format are as follows:
    INCORRECT FORMAT
    ORDER_COMPLETE=1098
    ORDER_ABANDONED=<Discover_Event_ID>
    Journey_Entry_Source_Code=ES-0000001
    CORRECT FORMAT
    ORDER_COMPLETE=1098
    Journey_Entry_Source_Code=ES-0000001
  8. Provide the Discover traffic attribute for each of the folowing Journey Data Definition fields:
    
    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>