> 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-subscription-billing-country.md). # Journey Based on Subscription Billing Country ## **Overview** Configuring a journey based on **subscription billing country** routes a logged-in customer with the country on the billing address of their subscription. Use it to show a cancel, save or switch page that agrees with the country that pays for the subscription. *Example: A customer whose subscription bills to Germany opens the cancel journey. Limio routes them to a German save page. A customer who bills to France goes to the French save page.* ## **Why the billing country and not the IP address** Cancellation and renewal rules differ by country, and they follow the country of the customer, not the country that the customer connects from. Route with the billing address when those rules decide what your cancel or save page must show. The Country condition reads the IP address of the visitor at the time of the request. It tells you where the person is at that moment. A VPN changes it, and so does travel. A subscriber who pays from Germany and reads from Spain gets the Spanish route. A digital subscription business rarely holds a verified home address. The billing address is the address that the customer gave for payment. It stays the same when the customer travels, which makes it the closest signal you have to the country whose rules apply. {% hint style="info" %} These rules protect consumers, and the detail is different in each country. Ask your legal advisers what you must do in the countries you sell to. {% endhint %} ### When you hold a better measure, use that instead Some businesses hold a stronger record of the country of the customer, for example from a registration form, a CRM, or an identity provider. Route on that value instead: * Put the customers of each country in a Limio Segment, then use the **Segment** condition. See [Journey Based on Limio Segments](/product/journey/what-are-limio-journeys/create-a-journey-based-on-limio-segments.md). * Add the country as a claim in the token, then use the **JSON Web Token** condition. See [Journey Based on Limio JWT](/product/journey/what-are-limio-journeys/create-a-journey-based-on-limio-jwt.md). Both conditions are in the same **Type** dropdown as Subscription Billing Country. ## **Before you start** The condition reads the billing address of one subscription. It matches only when all three of these are true: * The customer is logged in to the shop. * The starting point URL includes a `subId` query parameter that identifies the subscription, for example `/cancel?subId=sub-f556ee8517314c0f56c2b179a3cf4365`. Limio adds this parameter to the links in the Manage My Account pages. * The subscription has an address with the relationship type `billing`. If the subscription has more than one billing address, Limio uses the one created most recently. If any of these is not true, the condition does not match and the customer goes to the fallback tag. Set a **Fallback Tag** on the journey so that these customers get a page. Check the billing address of a test subscription before you start. Click **Subscriptions** in the left-hand navigation, search for the subscription, then open **Details** to see the addresses that are attached to it. ## **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. * Set a **Fallback Tag**. This condition needs one, because it does not match for anonymous visitors. 5. Select the shop **Domains** whose tags you want to search. ## **Adding the Subscription Billing Country criteria** 1. In the rule, click **Add condition**, then open the **Type** dropdown and select **Subscription Billing Country**. 2. In the **Country** field, type to search, then select one or more countries. The field shows the ISO 3166-1 alpha-2 code above the country name, for example **DE** above **Germany**. 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. The condition matches when the billing country is any one of the countries you select. To route two countries to two different pages, create a separate condition for each. **Verification Steps**: 1. Authenticate as a customer whose subscription bills to one of the countries you selected. 2. Access the starting point URL with the `subId` of that subscription in the query string. 3. Confirm that the customer lands on the destination page. 4. Repeat with a subscription that bills to a country you did not select, and confirm that the customer lands on the fallback page. --- # 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-subscription-billing-country.md?ask=&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.