What is a Web Flow?

Web Flows, previously called Cards, are containers for Web Pages in Studio. Within a Journey there can be multiple Web Flows that are each built with a specified purpose and each of the Web Flows can contain one or many Web Pages. Web Flows can be considered the individual processes/workflows within a journey, while Web Pages are the steps/action within that process. 

Web Flows can be illustrated by the following example:

There's a digital appointment scheduling application that will capture a user's information in a form and after the information is collected, the application will ask the user to schedule an appointment by selecting a time slot. There are two web flows that exist here:

  • Capturing the user's information
  • Scheduling the appointment


The reason that these two tasks are two separate web flows is because each of them can be considered a standalone process. Having these web flows be separate enables developers to create more modular experiences and connect the web flows via events or use the web flows as modals. 

When to use a Web Flow vs Web Page

An application can technically be built with only Web Pages, but it is generally recommended and a best practice to leverage Web Flows when building out an application. Web Flows can be used to organize and compartmentalize various processes in a journey, so typically when there is a separate process in the journey that can potentially be re-used, then that is when to use a Web Flow. Also, Web Flows can also be used as a modal within an application using the Open Modal Action, while Web Pages cannot. 

Web pages are different in that Web Pages are the steps or actions within that process that is broken out into multiple pages. Web Pages are encapsulated by a Web Flow and are typically related to the same process or flow.  

Events and Web Flows

Events can be used to link Web Flows to each other, serving as a bridge that connects multiple Web Flows resulting in the overall journey.  The Go To Web Flow Action can be used to connect Web Flows together either through the Action Builder/tab from a control or as an action in an event. Leveraging events provide a mechanism that allows the Web Flow to be reused and also diagram meaningful actions connected by events in Journey Builder

Further Reading

Web Flows are an integral part of the application building process and provide a way to create individual processes in a journey that can be reused. Web Flows also provide an organization mechanism as well, and provide a way to separate different user flows in an application. For more information on how to use Web Flows, see:








Was this article helpful?

0 out of 0 found this helpful