# 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 either **geolocation (IP-based)** or **subscription data (billing country)**. 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 condition is based on the user’s geolocation (IP address). If you need routing based on a customer’s subscription billing address (e.g. for regulatory flows), use Subscription Billing Country instead.

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

1. Under **Conditions**, open the **Type** dropdown and select **City**, **Country (IP-based),** **Region or Subscription Billing Country**.
2. In the chosen field, type to search your desired journey location (see table below)
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. 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) |

4. For **Subscription Billing Country** verification: Create test subscriptions with different billing countries in sandbox, trigger the journey for each subscription context, and confirm routing matches the subscription billing country (no VPN required).

<figure><img src="https://2981049874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxxxhzz4ER0TH1oIFAttf%2Fuploads%2FKUu3wmDhZVnoUB9Koehr%2Fimage.png?alt=media&#x26;token=8b252e8d-979e-43f8-b934-3637d941b39a" alt=""><figcaption></figcaption></figure>

📷 *Screenshot: View of the "Region" condition in the Journeys tab.*