Coordinate multiple flows and widgets

Give each widget a clear job and a place to appear. That lets you run several flows without showing someone competing questions or offers on the same page.

You'll need access to edit the project's flows and widgets. Start by listing the real pages where each one belongs, plus any pages you want to leave alone, such as checkout or account pages. If you're excluding customers or applicants, make sure RightMessage has reliable identified-contact data to recognize them.

Choose where each widget belongs

For each widget, decide which pages and audiences should see it. Where only one should appear, give the widgets nonoverlapping rules rather than relying on which one opens first.

For example, WorkForge (opens in a new tab) could place an embedded survey on its homepage (opens in a new tab) and show a demo toaster to leads on its pricing page (opens in a new tab).

For a floating widget:

1. Open Widgets and select the widget.
2. Open Display, then expand Targeting rules.
3. Choose Manage conditions.
4. Set the pages and audiences that should see it.
5. Repeat for the other widgets.

Enlarge

Widget targeting rules excluding the welcome and landing pagesOriginalOriginal

For an embedded widget, use Where it appears to choose its location. It doesn't have the floating widget's targeting card or trigger controls. Add a condition inside its flow when you also need an audience decision.

Targeting decides who can see a floating widget. Its trigger decides when it opens. A ten-second delay won't exclude customers, and a customer-exclusion rule won't set the delay. Each widget also keeps its own question handling and dismissal settings. Changing their shared flow doesn't make those settings identical. See the widget display reference for those options, including device rules and No visitors targeting.

Keep exclusions in every matching rule

If visitors must meet both an audience rule and a page restriction, choose All of the following are true. That way, an unrelated matching condition can't bypass the page restriction.

WorkForge's demo toaster could require both its pricing-page path and a lead segment. Its homepage survey would use a different page rule. Any checkout or account exclusions need to apply to the complete rule, not sit among the allowed alternatives.

Use a current-page condition when you're deciding where a widget appears. A previous visit to a page doesn't mean the visitor is on it now. A page-path rule checks the path, not the hostname.

The condition builder reference explains all the combinations, including rules that match any or none of the listed conditions.

Add decisions inside the flow

Use a condition inside the flow when some visitors should see different questions or when an embedded widget needs an audience check.

1. Open the flow.
2. Add Condition before the questions, offers, or actions that depend on the rule.
3. Set the rule in its editor.
4. Put the matching steps under Yes.
5. Put Exit Flow under No if nothing should run for other visitors.

For exclusions you reuse across flows, a segment group can represent ignored pages. Each flow can check that group and exit before its actions or questions.

Check background flows too

System flows don't wait for a widget trigger or depend on a widget's Enabled switch. Give each system flow its own page and audience conditions before its actions.

Check visible widgets and background actions separately. A hidden widget won't stop a system flow from updating data. Pay particular attention when several flows write to the same variable or contact field.

Test each page and audience

Choose Preview on your site to load the draft, then visit each included and excluded page. Try an unknown visitor, a known lead, and a customer. Let widgets open normally rather than forcing them open with the debugger. Use the debugger to inspect their targeting and any background actions.

For WorkForge, that means checking the homepage survey, the pricing-page toaster, and pages where neither should appear. Check every attached widget, not just the one you edited.

Once the right widget appears for each visitor and excluded pages stay clear, review the pending project changes and publish.

Keep shared content in mind when managing flows

Duplicating a flow keeps references to its shared questions, forms, and offers. Deleting only a flow leaves its attached widgets in place but clears their flow assignment. The flow settings reference covers renaming, duplication, and each deletion choice.

If you only need to stop showing a flow for a while, pause its widgets rather than deleting it.