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
-
In the Discover Portal UI, select
.The Discover Services Management page appears.
- Expand Canister.
- Select Canister configuration (xxxxx) (Registry).
-
Within the Config Actions section, select
View/Edit.
The Discover Canister Config popup appears.
- Select
- Enable Enable Event Bus.
Activating Send to Event Bus
Procedure
-
In the Discover Portal UI, select
.The Event Manager page appears.
- Locate the required event by using filters and filtering the values based on Name or ID.
-
To edit an event, perform one of the following actions:
- Double-click the event.
- Right-click the event and select Edit Event.
- Select More options.
- Enable Send to Event Bus.
Configuring DiscoverEventBus.cfg
Procedure
-
In the Discover Portal UI, select
.The Discover Services Management page appears.
- Expand Canister.
- Select Event Bus configuration (xxxxx) (Registry).
-
Within the Config Actions section, select
View/Edit.
The Pipeline Editor - Event Bus configuration (xxxxx) popup appears.
- 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.
-
Select CEP.
The Edit Session Agent:CEP popup appears.
- For the OutputType field select JOURNEY.
- Click Apply.
Configuring REST type of Entry Source
Procedure
- Select Journey Entry Source Type REST and click Apply.
- Enter Journey Entry Source API Server URL and click Apply. For example, http://localhost:8080/journey/api/
- Enter Journey Entry Source API Client ID and click Apply.
- Enter Journey Entry Source API Client Secret and click Apply.
Configuring Unica Discover / Kafka type of Entry Source
Procedure
- Select Journey Entry Source Type Kafka and click Apply.
- Enter Journey Entry Source Kafka Server / Broker, along with the port number for listening, and click Apply. For example, localhost:9092
- Enter Journey Entry Source Kafka Security Type.
Configurations applicable when Entry Source Kafka Security Type selected is
SASL_PLAINTEXT
Procedure
- Enter the Journey Entry Source Type Kafka SASL User and click Apply.
- Enter the Journey Entry Source Type Kafka SASL Password and click Apply.
Configurations applicable when Entry Source Kafka Security Type selected is
SSL
Procedure
- Enter the Journey Entry Source Type Kafka SSL Cert location and click Apply. For example, C:\KSSLCert\client_cert.pem.
- Enter the Journey Entry Source Type SSL CA location and click Apply. For example, C:\HCL\KSSLCert\ca-cert.
- 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
- Enter the Journey Entry Source Type Kafka SASL User and click Apply.
- Enter the Journey Entry Source Type Kafka SASL Password and click Apply.
- Enter the Journey Entry Source Type Kafka SSL Cert location and click Apply. For example, C:\KSSLCert\client_cert.pem.
- Enter the Journey Entry Source Type SSL CA location and click Apply. For example, C:\HCL\KSSLCert\ca-cert.
- Enter the Journey Entry Source Type SSL Key location and click Apply. For example, C:\HCL\KSSLCert\client_key.pem.
Configuring CEPCustomFields.cfg
Procedure
-
In the Discover Portal UI, select
.The Discover Services Management page appears.
- Expand Canister.
- Select CEP custom fields configuration file xxxxx) (CEPCustomFields.cfg).
-
Within the Config Actions section, select
View/Edit.
The CEP custom fields configuration file xxxxx) (CEPCustomFields.cfg) popup appears.
-
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>
Note: An example foremail=<loginid or some other field including session attributes>
, in the earlier configuration, isemail=CustomVarN
where CustomVarN is the JavaScript Name of the concerned session attribute. For more information, see the topic "Session attribute list" in Unica Discover Event Manager Manual.
In the earlier configuration example, you can use session attributes for all Journey data definitions, except
CookieID
. -
Access
Discover Event ID
for each of the following events: to fetch the Event ID. Modify the Journey Section and specify thePRODUCT_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>
-
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 mapORDER_COMPLETE
and notORDER_ABANDONED
, the incorrect format and correct format are as follows:INCORRECT FORMATORDER_COMPLETE=1098 ORDER_ABANDONED=<Discover_Event_ID> Journey_Entry_Source_Code=ES-0000001
CORRECT FORMATORDER_COMPLETE=1098 Journey_Entry_Source_Code=ES-0000001
-
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>