Deliver an experience using launch rules

Who can use this feature?

Launch rules allow you to define which URL(s) an experience should appear on and/or what events should trigger them for users within your application. These rules are designed to fit a wide range of use cases so that you can ensure experiences/checklists only appear exactly when you want them too.

Launching on static URLs

A static URL is a route that remains exactly the same for every user visiting your platform. This is the most simple type of URL to create a rule for. Here's an example of a rule that would launch an experience on a specific page of an application (reports):

Launching on dynamic URLs

A URL is considered dynamic when it contains a variable or id that changes from user to user (e.g., To create a rule for a dynamic url, you can simply replace the dynamic section with an '*' which will act as a wildcard like so:

Wildcards can also be used to replace other parts of a url rule that may be dynamic. For example, you may have a different subdomain set up for each one of your users (e.g., & You can even use wildcards multiple times within the same rule to replace multiple dynamic sections:

You cannot use wildcards in redirect URLs. Instead, you can use the relative URL path instead. For example,*/settings/integrations/hub/applications would be /#/settings/integrations/hub/applications

Launching experiences on URLs with query parameters

Query parameters are the section of a URL that appears after a question mark ("?"). For example, the query parameters in the following url appear in bold:

In the "Advanced options" dropdown menu for a single Launch Rule, you will find an option to toggle query parameters on or off.

Query Parameters OFF

With query parameters off, Lou will ignore the question mark and query parameters in the website URL when comparing against your Launch Rule. For example:

If a user visits:

And your launch rule is:

Then your experience will appear.

Query Parameters ON

However, if you have query parameters toggled on, Lou will take all of the query parameters of the website URL into account when comparing against your Launch Rule. For example:

If a user visits:

And your launch rule is:

Then your tour will appear.

But, if a user visits:

Then your tour will not appear.

Launching when a user navigates away from a URL

Launch rules can also be used to trigger an experience when a user navigates from one url to another. For example, you may want to trigger a tour on your "Reports" page only if a user navigates there from the "Dashboard" page To achieve this, you can create a second launch rule and use the "advanced options" dropdown to select "use previous url":

Launching when an event is tracked

If event tracking is configured, simply create a new event by selecting a website element in your application and providing a unique name. This example shows an application with an "Update task" function.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request