Joins in Journey Management
The transition from event to event can be controlled by clicking on the connector between the events. That will allow you to specify what you can use as a join between two events. Note that the values for attributes used as a join are not available for filtering or charting. They are identifiers only. The list of what is available depends on the events.
| Category | Scope | Usage |
|---|---|---|
|
Customer |
Unique customer identifier set by Genesys Cloud. |
Primary join that enables Journey Management to measure unique customers at each step of a journey. This is the default. |
|
Conversation |
Typically, conversationID. This will be available as a secondary join for any events in a sequence that derive from a conversation (agent-led, AI-enabled, digital). |
Can be used as a secondary join to specify that the count should reflect those events that happen on the same set of conversations. |
|
Search |
Used exclusively in Knowledge events to capture a search event which is triggered when knowledge is requested. |
Can be used as additional join (individually or in combination with others) when working with knowledge events to limit scope of analysis to a select set of searches. |
