> 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-subscription-status.md).

# Journey Based on Subscription Status

**This feature is currently in beta. Please test it in a sandbox environment before deploying it to production.**

## **Overview**

Configuring a journey based on **subscription status** allows you to personalize user experiences by directing them to specific pages depending on whether they have an active subscription. For example, you might want to:

* Route **active subscribers** to exclusive content or account management pages.
* Redirect **non-subscribers** to sign-up or promotional pages.

This approach enhances user engagement by ensuring that each user encounters content relevant to their subscription status.

*Example: If a user has an **active subscription**, they can be automatically routed to a **premium content page**. Conversely, users without an active subscription can be directed to a **subscription offer** or **sign-up page**.*

## **Before you start**

Check that the Limio customer is authenticated with an Identity that is correctly linked to an active Subscription. If the identity is missing or incorrect, the journey may not work as expected.

You can verify this by clicking the Subscriptions dropdown in the left-hand navigation > clicking Subscriptions > the left-hand navigation changes click Subscriptions here > search for the Subscription to verify > click Details > Owner will be populated as will Identity.

## **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 the Subscription Status criteria**

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Subscription Status**.
2. In the **Subscription Status** field, choose an option of **activeSub** or **noActiveSub**.
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. Authenticate as a user with the relevant subscription status (e.g activeSub).
2. Access the starting point URL.
3. Confirm that the redirection aligns with the defined journey.

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

📷 *Screenshot: View of the "Subscription Status" 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 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-subscription-status.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.