> 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-query-string.md).

# Journey Based on Query String

## **Overview**

Configuring a journey based on a **URL query string** allows you to personalize user experiences by directing them to specific pages based on parameters in the URL. This approach ensures that users arriving from different campaigns, sources, or user groups receive relevant content. For example, you might want to:

* Route users arriving from a **partner campaign** to a **custom landing page**.
* Redirect visitors with a **specific tracking parameter** to a **personalized offer**.
* Send users from a **corporate account** to a **dedicated business portal**.

By using **query string conditions** in Limio Journeys, you can dynamically route users based on these parameters.

## **Before you start**

A basic understanding of URL query strings, including how parameters are structured and how they affect webpage behaviour is required.

`www.example.com/over/there?company=limio`

The query string is `company=limio`

## **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 Query String Criteria**

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Query String**.
2. In the **Query String** field, input your query string (use commas to separate multiple).
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 an incognito/private browsing window.
2. Enter the URL with the specified query string (e.g `https://example.com/?company=limio`).
3. Ensure that the expected journey behaviour is triggered.

Example: If a user arrives with the query string **company=limio** in their URL, they will be automatically routed to the **UK default campaign page**. This ensures that users from a specific company or campaign receive a tailored experience.

Since the **split is set to 100%**, all users matching this query string condition will be directed to the defined destination without variation.

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

📷 *Screenshot: View of the example above in action*


---

# 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-query-string.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.
