Get Journey Segment action

AI-generated summary

Genesys Cloud's Predictive Engagement feature enables website user tracking and personalized engagement through action maps. The Get Journey Segment action in Architect retrieves Journey Segment IDs and stores them in variables for workflow use. Key configuration elements include a customizable action name, Journey Segment ID field accepting literal values or expressions, and a Journey Segment Result variable that can be referenced using State.<variable name> syntax. The action includes two routing paths: "Found" for successful journey segment location within the organization, and "Not Found" for unsuccessful matches. Each path can be configured with subsequent actions like play audio or End Workflow to determine the interaction flow. This functionality helps organizations design targeted customer experiences and achieve specific business outcomes through website interaction tracking.

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 Segment action to obtain the Predictive Engagement Journey Segment ID and store it in a variable to use within the workflow.

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 Segment ID	Enter a literal value or expression in the Journey Segment ID field. Architect creates a variable for use with the Journey Segment ID field.
Journey Segment Result	Type a name for the variable to store the journey segment ID 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 segment 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 segment 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 segment 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 segment 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 Segment action

Configure found and not found paths

[NEXT] Was this article helpful?