> For the complete documentation index, see [llms.txt](https://academy.gopersonal.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.gopersonal.ai/en/admin-ui/journeys/workflow/flow-control.md).

# Flow control

controlling the flow of User Journeys is essential for delivering personalized and effective customer experiences. The platform offers versatile components that empower you to craft intricate and adaptive journeys tailored to individual customer interactions. Here's how you can manage the flow of your User Journeys:

[**Simple Conditions**](/en/admin-ui/journeys/workflow/flow-control/simple-condition.md)**:**

* **Yes or No:** Conditions that allow you to route customers based on binary responses, such as "Yes" or "No." For example, if a customer has made a purchase (Yes), they proceed to the next step; otherwise (No) the journey ends. 

[**Complex Conditions**](/en/admin-ui/journeys/workflow/flow-control/complex-condition.md)**:**

* **Define Paths:** Create more complex conditions that enable you to define multiple paths within a journey. For instance, if a customer has browsed specific categories, you can define separate paths for each category.
* **Path Conditions:** Assign unique conditions to each path. Customers meeting specific criteria follow the designated path. For example, if a customer's last purchase was within the last 30 days, they follow one path; if it's beyond 30 days, they follow another. 

[**A/B Testing**](/en/admin-ui/journeys/workflow/flow-control/a-b-testing-paths.md)**:**

* **Path Allocation:** Utilize A/B testing to define the percentage of customers allocated to different paths. For example, you can send 50% of customers down Path A and 50% down Path B to analyze which path yields better results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.gopersonal.ai/en/admin-ui/journeys/workflow/flow-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.