We've rebuilt the Onsite Messaging editor around two new tools: a visual Flow builder and a Design Studio. This guide walks through what's changed, why it matters, and how to find your way around.
What's new at a glance
Previously, you configured an onsite message through a set of forms and settings tabs. The new editor keeps all of that power but adds a visual way to see and shape the whole experience.
| Area | Before | Now |
|---|---|---|
| Building the flow | Screens configured separately through forms; hard to see the whole journey. | Flow builder: a visual canvas showing every screen and how visitors move between them. |
| Styling | Style options spread across settings. | Design Studio: style each element directly, with live preview and per-device control. |
The Flow builder (New)
This is the biggest change. Instead of configuring screens in isolation, you now see the entire visitor journey on one canvas, with each screen shown as a node and connected in the order visitors experience them.
What you can do here
- See every screen (for example Minimized, Message, Form, Reward) and how they connect.
- Add reward, reminder-email, and confirmation-email steps and see where they are placed in the visitor flow.
- Open any node to edit its settings in a side panel.
The Design Studio (New)
The Design Studio is where a message gets its look. Select any element on the preview and style it directly, with no need to hunt through settings.
- Element-level styling: click an element, edit its properties in the panel.
- Live preview: see changes instantly.
- Per-device: switch between mobile and desktop; set device specific overrides on top of a shared base.
- Real form fields: build the actual fields visitors will fill in.
Try it: create your first message
- From the message list, select Create onsite message (New).
- Choose a template to help you pick a starting point.
- You land in the Flow builder. Review the screens and connect or add steps.
- Open the Design Studio to style elements and build your form fields.
- Set scheduling and any display conditions, then publish.