> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/journey/what-are-limio-journeys/create-a-journey-based-on-limio-segments.md).

# Journey Based on Limio Segments

## **Overview**

Configuring a journey based on **Limio Segments** allows you to personalize user experiences by directing customers to specific pages depending on their segment membership. This approach ensures that different customer groups receive relevant content, offers, or promotions. For example, you might want to:

* Route **high-value subscribers** to an **exclusive upgrade offer**.
* Redirect **trial users** to a **conversion-focused page**.
* Send **churned customers** to a **win-back campaign**.

Limio Segments are predefined groups of customers based on factors such as engagement level, subscription history, or purchase behaviour. These segments can be managed within Limio and applied dynamically within Journeys.

This guide explains how to apply **segment-based criteria** to control user flow.

## **Before you start**

Ensure that the required OSegments have been created in the Limio app.

Check this by navigating to Offers in the left-hand navigation, selecting your Segments > search in the navigation panel.

## **Creating a Journey**

1. Select **Journeys** from the left-hand navigation panel.
2. Click **New journey**.
3. Enter a name for the journey and click **Save**.
4. Click **Set starting point** to define how users enter the journey:
   * Choose an existing tag or create a new one.
   * (Recommended) Click **Set fallback tag** to ensure proper routing.
5. Select the shop **Domains** whose tags you want to search.

## **Adding Segment Criteria**

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Segment**.
2. In the **Segment** field, select one or multiple segments you want to target.
3. Under **Action**, ensure **Type** is set to **Destination**.
4. Click **Add action** if the rule has none, then **Add Split**. The split defaults to **100%**. Click the pencil ✏️ on the tag next to it and choose the endpoint.
   * Click **Add rule** to add another rule to the journey.
   * Click **Add condition** in a rule to add an **AND** criteria to that rule.
5. Finally, click **Save** to put the Journey live.

**Verification Steps**:

Check Segment Membership:

1. Identify test users and confirm they belong to the expected segment (e.g Weekly Term)
2. Access the starting point URL.
3. Verify that changing segment conditions updates the user’s journey.

Test Redirections for Different Segments:

1. Set up multiple test journeys with different segments.
2. Access the journey URL with different segment criteria and confirm expected behaviour.

## **Example:**

If a user belongs to the **Weekly Term** segment, they can be automatically routed to a **rescue campaign page**. Users who do not meet this segment condition will be directed to the **fallback rescue-weekly page**.

In this setup, **10% of users** who meet the segment condition are split and routed to a **rescue trial fortnight page**. This allows for controlled testing or gradual rollout of different experiences.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-d8ffeb08b6890dcb5796a9c838da040cfd97b5ab%2Fimage%20(151).png?alt=media" alt=""><figcaption></figcaption></figure>

📷 *Screenshot: View of the example above in action*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/product/journey/what-are-limio-journeys/create-a-journey-based-on-limio-segments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.