> 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-a-session-cookie.md).

# Journey Based on Session Cookie

## **Overview**

Configuring a journey based on cookies allows you to personalize user experiences by directing them to different pages depending on their authentication status or browsing history. For example, you might want to:

* Route **logged-in users** to the **Manage My Account** page.
* Redirect **guest users** to a sign-in or promotional page.

Limio supports all cookies starting with the prefixes `lmo_` and `limio-`, making it easy to segment users dynamically. This guide explains how to create a journey and apply cookie-based criteria to control user flow.

*Example: If a user has the `lmo_uid` cookie (indicating they are authenticated), they can be automatically routed to the **Manage My Account** page. Users without this cookie can be directed to a **sign-in page** or **subscription offer**.*

## **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 Cookie Criteria**

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Cookie Exists**.
2. In the **Cookie String** field, enter one or multiple cookie names, separated by commas (e.g `lmo_uid`).
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**:

1. Open a browser and ensure the cookie is set (e.g `lmo_uid`).
   * Right-click> Inspect
   * Click the Application tab
   * Under the Storage heading > Cookies
2. Access the starting point URL.
3. Confirm that the browser redirects to the specified destination URL.

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

📷 *Screenshot: View of the "Cookie Exists" condition in the Journeys tab.*


---

# 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-a-session-cookie.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.
