Get Journey Session action

AI-generated summary

Genesys Cloud's Predictive Engagement feature enables user tracking during website interactions through Journey Sessions. The Get Journey Session action in Architect allows retrieval of Journey Session IDs and stores them in variables for workflow use. Key components include: Configuration elements: - Name field for distinctive action labeling - Journey Session ID field for literal values or expressions - Journey Session Result variable for storing session data - Reference format: State.<variable name> Path options: - Found path: Executes when journey session is located - Not Found path: Triggers when no matching session ID exists The action supports both standard and chat flows, helping create personalized user experiences and achieve business outcomes through action maps. Integration with Architect components enables workflow customization based on session status.

Predictive Engagement allows you to track users as they interact with your website. You can use action maps to design engagements that enhance each user’s personal experience and help you achieve your business outcomes. For more information, see Prepare Architect components.

In Architect, use the Get Journey Session action to obtain the Predictive Engagement Journey Session ID and store it in a variable to use within the workflow. This action is also available in Architect chat flows.

Name	Description
Name field	Type a distinctive name for the action. The label you enter here becomes the action’s name displayed in the call flow structure.
Journey Session ID	Enter a literal value or expression in the Journey Session ID field. Architect creates a variable for use with the Journey Session ID field.
Journey Session Result	Type a name for the variable to store the journey session found in this action. To reference this variable in the rest of the flow, type State.<variable name>. For example, if the variable name is Customer Journey, to reference the variable throughout the flow, type State.CustomerJourney at the appropriate location.

Configure found and not found paths

Name	Description
Found	This path indicates that Architect located the journey session within the organization. Drag the appropriate action below the Found path so that it follows the route you want the interaction to take. For example, a play audio action.
Not Found	This path indicates that Architect did not find the matching journey session ID. Drag the appropriate action below the Not Found path so that it follows the route you want the interaction to take. For example, an End Workflow action.

Name

Description

Found

This path indicates that Architect located the journey session within the organization.

Drag the appropriate action below the Found path so that it follows the route you want the interaction to take. For example, a play audio action.

Not Found

This path indicates that Architect did not find the matching journey session ID. Drag the appropriate action below the Not Found path so that it follows the route you want the interaction to take. For example, an End Workflow action.

[NEXT] Was this article helpful?

Get user feedback about articles.

Loading...

Get Journey Session action

Configure found and not found paths

[NEXT] Was this article helpful?