Set up an environment pipeline

Who can use this feature?

You can define environment pipelines to serve as groups of staging and production environments for any application where you'd like to publish In-App experiences. These pipelines simplify the process of publishing experiences across staging and production environments so that you can seamlessly create, test, and deploy experiences without updating delivery rules and other settings.

Set up a new environment pipeline

Environment pipelines require that your staging environment and a production environment have the same subdomains.*

  1. From within the Builder, click the (globe icon).
  2. Enter the pipeline details:
    • Pipeline Title: Name to refer to the pipeline.
    • Production environment: URL of root domain where published experiences appear.
    • Staging environment: URL of root domain where staged experiences appear.
  3. Click Save Environment.

*In the case where you have a staging environment and a production environment with different subdomains, you won't be able to leverage pipelines. Instead, adjust the delivery rules in the deliver tab of the Lou Builder to unpublish an experience from staging and publish to production. Once your experience is ready to be moved from staging to production, change the URL to your production environment subdomain.

To make an experience live in staging and production, duplicate the experience and set the URL on one to staging and production on the other. In this case, we recommend clearly labeling your experience as ‘staging’ or ‘production’ to minimize confusion.

Publish experiences between environments

Once you've defined an environment pipeline and associated it with an experience, you can begin to publish that experience between environments. All pipeline options are available from the Publish drop-down within the Builder.


To publish your experience to a staging environment, click the dropdown arrow and select Publish to Staging. This will update the current status of your experience to Staged. In this state, the experience will only appear for users on the staging environment domain that you defined in your pipeline.


To publish your experience to a production environment, simply click the main Publish button. This will update the current status of your experience to Published. In this status, the experience will appear for users on both the staging and production environment domains that are defined in your pipeline.


Lastly, if you would like to schedule your experience to publish in the future. You can do so by selecting Set a Schedule. This will allow you to define a date/time for when you want the experience to publish to production and also a date to unpublish on.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request