> 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-jwt.md).

# Journey Based on Limio JWT

## **Overview**

Configuring a journey based on **Limio JSON Web Token (JWT)** allows you to personalize user experiences by directing customers to specific pages depending on their Identity Token. This approach ensures that different customers can receive different experiences. 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 JSON Web Token will look at attributes defined in your Identity System JWT token. Learn more on how to configure your Identity System to pass information to Limio on [Set up Authentication for Customers](/product/authentication/sso-your-authentication.md).

## **Before you start**

* Ensure that the required Claims in your Identity system.
* Once done, go through a purchase journey and check that the JWT token has the Claims. You can do by going to Limio Subscription > select a Limio Customer > click on Limio Owner > then identify the Identity with @limio/external-id.

## **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 **JSON Web Token**.
2. In the **JSON Web Token** field, press (+) and fill in the **Condition, Operator and Value** you need.
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 JSON Web Token has **status is equal to trial**:

1. Identify test users and confirm the JSON Web Token (JWT) has a custom attribute **status** and a value of **trial.**
2. Access the starting point URL.
3. Verify that changing value of status updates the user’s journey.

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

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


---

# 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-jwt.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.