> 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-the-customer-location.md).

# Journey Based on Customer Location

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

## **Overview**

Configuring a journey based on **customer location** allows you to personalize user experiences by directing them to specific pages tailored to their geographical area. Journeys can route users based on **geolocation (IP-based)**. This approach can enhance engagement by presenting region-specific content, offers, or language preferences.

**Note:** For more specific geographical routing, you can target users based on their region using ISO 3166-2 subdivision codes.

*Example:* *If a user is located in the **Bayern region of Germany (DE-BY)**, they can be automatically routed to a **German-language promotional page**. Users from other regions can be directed to a **default English-language page**.*

## **Before you start**

Ensure you understand how Limio determines customer location (e.g IP address) and what factors may affect accuracy (e.g customer using a VPN).

Note: The Country and Region conditions are based on the user’s geolocation (IP address).

## **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 customer location criteria**

1. In the rule, click **Add condition**, then open the **Type** dropdown and select **City**, **Country (IP-based), or** **Region**.
2. In the chosen field, type to search your desired journey location (see table below)
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. Use a VPN or online geolocation tester to simulate different locations.
2. Access the starting point URL.
3. Confirm that the following journey redirects based on the expected location.

| **Country** | country name as the input                                     |
| ----------- | ------------------------------------------------------------- |
| **City**    | city name as the input                                        |
| **Region**  | ISO 3166-2 subdivision code (use commas to separate multiple) |

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

📷 *Screenshot: View of the "Region" 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-the-customer-location.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.
