Skip to content

Choose and manage experiences

An experience is guidance or a message delivered inside your product. Choose the format after deciding who needs help and what they should do next.

FormatExample use
GuideWalk a new user through two or three connected actions.
SurveyAsk for feedback after a real product task.
ChecklistKeep onboarding tasks visible across visits.
BannerAnnounce an update at the top or bottom of a page.
Anchored cardExplain a specific control next to that control.
ToastGive a brief, non-blocking message.
ModalAsk for focused attention in an overlay.
SlideoutPresent a longer message from an edge of the screen.
HotspotMark a feature with a beacon that opens more context.
Cursor followerKeep a compact message beside a pointer on a suitable desktop flow.

Guides, Surveys, Banners, and Checklists have sidebar entries. Find the other widget collections under Experiences → Other. Anchored cards provide the contextual pattern often called a tooltip; there is no separate Tooltip collection.

Use the collection’s Create action, name the experience, and choose Open Editor. Non-checklist experiences need a build page on the site’s configured domain. Follow Build your first experience.

StateMeaning
DraftEditable content that has not been made available as the live version.
LiveThe published version can be delivered to eligible visitors.
PausedDelivery is paused; the experience can be edited and published again.

Use Edit to change a draft, Pause to stop delivery, and Publish to publish/resume from the collection when setup is valid. For a controlled launch or draft update, use Review & publish inside the editor. Surveys also offer Build and View Results.

Delete permanently removes an experience after confirmation. Check any checklist tasks that launch a guide before deleting or pausing that guide.

Creating, changing, publishing, pausing, and deleting requires Owner or Admin access. Available advanced settings also depend on your plan.

Next: Visual editor · Publishing.

Movcues Create guide form with a demo name, manually entered build URL, and Start blank template.
Name the draft and choose the product page used to build it. Demo workspace; synthetic data only.