> 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 the **plus** **+** button and select **Add Journey Group**.
3. Enter a name for the group and click **Save**.
4. Click the **pencil** ✏️ icon next to **Starting Point** to define how users enter the journey:
   * Choose an existing tag or create a new one.
   * (Recommended) Set a **Fallback Tag** to ensure proper routing.
5. Select or deselect **Domains** to determine where the journey applies.

## **Adding Segment Criteria**

1. Under **Conditions**, 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 **Actions**, ensure **Type** is set to **Destination**.
4. Click the **pencil** ✏️ icon next to **Split (%)**, which defaults to **100%**, and specify the endpoint.
   * Click **Add Condition** to include an additional condition for the journey.
   * Click the **plus +** button below an existing condition to add an **AND** criteria within that condition.
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="/files/R5xxIraZTRYDrt4123Ka" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/hbeQSI5ZBsu8G8hmNZ7U" 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 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://docs.limio.com/product/journey/what-are-limio-journeys/create-a-journey-based-on-limio-jwt.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.