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

# Journey Based on Devices

## **Overview**

Device-based routing allows you to personalize user journeys by directing users to specific pages based on their device. This is useful for optimizing user experiences across different devices, such as:

* Redirecting **mobile users** to a mobile-optimized page.
* Routing **iOS users** to an **App Store landing page**.
* Directing **desktop users** to a **full-featured web experience**.

This guide explains how to configure **device-based conditions** within Limio Journeys.

*Example: If a user is on an iOS device (e.g., iPhone), they can be automatically redirected to an App Store page. Android users can be routed to a Google Play Store page, while desktop users remain on the main site.*

## **Before you start**

The page(s) you are routing to should already have been created with the relevant tag e.g 'App Store landing page'.

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

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Device**.
2. In the **Device** field, choose one or several options from the drop-down.
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. Access the starting point URL.
2. Toggle the device to check for expected behaviour (e.g., Chrome's mobile emulator).
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-f91753ffc060ec66b30cc2c4494931d201101122%2Fimage%20(149).png?alt=media" alt=""><figcaption></figcaption></figure>

📷 *Screenshot: View of the "Device" 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-devices.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.
