Flows, widgets, forms, and campaigns
You'll learn how flows decide what visitors see, widgets put them on your site, forms collect information, and campaigns change your pages.
A flow is the conversation you have with a visitor. It decides what to ask and what comes next. A widget is how that conversation appears on your site, such as a popup or a box in the corner.
Forms collect information. Offers send people to a page or another destination. Campaigns change content that's already on your website.
How they work together
Our example business, WorkForge (opens in a new tab), wants to offer a planning guide to new visitors and a demo to existing leads. Its flow checks their lifecycle segment. New visitors get a question about what they need, followed by a signup form. Known leads get a demo offer instead.
The widget shows that flow in a corner of the website. Its display settings decide which pages and devices it appears on, and what triggers it. Its design settings control colors and typography.
What to edit when you want to change something
| If you'd like to change… | Edit this |
|---|---|
| Questions, routing, actions, and what comes next | The flow. Widget appearance and timing have their own settings. |
| Placement, design, targeting, triggers, dismissal, or question handling | The widget. The flow still controls its branch rules. |
| A reusable question or its answer settings | The question. Not every answer type creates a contact. |
| Fields or what happens on submission | The form. Ordinary nodes below it in the parent flow aren't its follow-up path. |
| A reusable call to action or its destination | The offer. The destination handles any booking or purchase. |
| Targeted changes to existing page content | The campaign. You keep your website builder. |
You can reuse questions, forms, and offers. Editing one can affect several flows. Removing its node from a flow doesn't delete it from the library.
Choose how the flow appears
Widgets can show the same flow in different places:
| Widget type | Where it appears |
|---|---|
| Popup | Centered over the page |
| Toaster | In a corner |
| Bar | Along the top or bottom |
| Full-screen takeover | Across the screen |
| Embedded | Inside page content at a matching embed location |
One flow can run in several widgets. Each keeps its own appearance, targeting, question handling, and dismissal behavior. Depending on those settings, one widget can skip a remembered answer while another asks the question again.
A system flow runs supported actions on page views without a widget. It can't ask an ordinary question or display a form.
Forms collect information, and offers link somewhere
In a form, Content holds the headline, description, button text, and image. Fields controls what people enter and any hidden values sent with the submission. Actions controls what happens when they submit, such as sending supported data to your connected platform.
The flow node chooses which form to show. The form's Post-Submit Actions For This Form path handles what happens afterward. To ask a follow-up, use that path rather than putting an ordinary question below a terminal form on the parent canvas.
An offer lets you send someone to a resource without asking them to complete a RightMessage form. Neither an offer nor a redirect books an appointment, takes payment, or fulfills a purchase. The destination service does that work.
Campaigns change the page itself
WorkForge could also change an existing headline for visitors interested in planning. That's a website campaign, separate from the toaster widget. Campaigns require Scale or Pro. Campaigns and flows can use the same known answers, but keep their own targeting.
For setup, create a flow. The widget display reference covers placement and timing, and form completion and redirects explains what happens after a form.
Changes stay in your project draft
Editing a flow, widget, form, or campaign saves to the project draft. It doesn't publish to your website. When you publish, changes to shared questions and forms can affect several visitor paths.
Before publishing, follow the whole path. Check that the right widget appears, the right flow branch runs, and the form or offer sends the visitor and their data where you intended.