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

1. Under **Conditions**, 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 **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**:

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="/files/hYvvoEfpMaVeITlqmzWD" 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 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-query-string.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.