What are Limio Journeys?

Limio Journeys enable you to deliver dynamic and personalised experiences to your customers, such as geographic routing, A/B testing, or segmentation. With Limio Journeys, you can ensure customers see the most relevant content based on various conditions.

The technology behind Limio Journeys

Limio Journeys are powered by a Content Delivery Network (CDN) with an Edge Handler. This technology allows custom code to run closer to the user's location, enabling functionalities such as:

• Modifying HTTP requests and responses
• Making decisions based on user location
• A/B testing
• Authentication

This architecture provides a highly personalised and efficient user experience by dynamically redirecting customers based on predefined conditions. For example:

• A US-based user accessing the Limio Shop homepage can be redirected to the US-specific homepage.
• A French user may be routed to a French-language page.

From the app user’s perspective, Limio Journeys operate via URLs. You define a starting point URL (e.g. /landing-page) and set conditions to redirect users to destination URLs (e.g. /us/landing-page or /fr/landing-page).

Creating a Journey

1. Select Journeys from the left-hand navigation pane.
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.
6. Set your Conditions and Actions based on the desired journey behaviour
   (see Limio Journey usage below)
   • 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.
7. Finally, click Save to put the Journey live

Important Considerations for Limio Journeys

• Preserved Display URL: Users will continue to see the starting point URL in their browser, even after redirection. This helps prevent URL manipulation to access ineligible deals.

• Journey Activation: Clicking Save immediately activates the journey. To prevent premature activation, use a placeholder starting point (e.g., /placeholder250120). Replace it with the actual starting point when you're ready to go live.

 

Limio Journey usage

Acquisition Journeys:

• Create a Journey based on the customer location: Direct users to country-specific Pages using their IP address (e.g. UK customers see UK-specific offers).
• Create a Journey based on devices: Redirect users to device-specific Pages (e.g. mobile users see a mobile-friendly page).
• Create a Journey based on a A/B Test: Show different Pages to the same users at random to measure performance.
• Create a Journey based on a Session Cookie: Route users to specific offers based on the presence of a session cookie.
• Create a Journey based on Subscription Offer Labels: Route users who just purchased a subscription to a different order complete page.

Cancel/Save and Switch Journeys:

• Create a Journey based on Subscription Offer Labels: Route logged-in users to Pages based on their subscribed offers.
• Create a Journey based on Limio Segments & Journeys: Show Pages tailored to customer segments.
• Create a Journey based on Query String: Redirect users based on specific query strings in the URL.
• Create a Journey based on Subscription Status: Differentiate experiences for active subscribers vs. non-subscribers.
• Create a Journey based on the customer location: Direct logged-in customers to offers based on their original purchase country.

Example:

A company wants to run a limited-time promotional campaign but wants to ensure that only active subscribers accessing the site from a mobile device see the offer. Additionally, they want to A/B test two different landing pages to determine which version performs better.

Users will be randomly split if:

• ✅ They have an active subscription based on Subscription Status criteria
• ✅ Is visiting from a mobile device based on Device criteria

📷 Screenshot: Example above in action