Use the survey editor

Open a survey from your site's Surveys page. The editor has three steps beside a persistent preview: Questions, Targeting, and Look & words.

Questions

Add and connect questions on the canvas. Select a question to open its settings in the inset panel. Each question's outgoing connections determine what follows an answer; review every branch, skip and ending before publishing. Canvas options also include List view, zoom and layout controls.

Adding a question extends an ordinary survey's final completion path. Named endings, conditional exits and experiment branches keep their existing connections; review those routes explicitly when extending them.

Moving a card changes its editor layout, not what visitors answer. Question IDs and option IDs identify existing data and logic; preserve them when editing a survey that already has responses. See Survey definition, Answer randomisation and Survey experiments for the underlying behavior.

Targeting

Choose the audience, trigger, sampling, frequency and any schedule. Read the condition summary before publishing. An audience-size estimate may be unavailable for these conditions; an unavailable estimate is not a count of zero.

An event trigger requires the application to report that event after the corresponding action succeeds. Merely creating the survey or opening its preview does not wire the event. See Targeting and Application events.

Look & words

Set the presentation and theme, then review the survey's languages and translations. Check the preview for each intended language and device size. Automatic translation still needs review, especially after changing the source wording.

The editor's Settings menu also controls Save partial responses. When enabled, submitted answers are retained even if a visitor leaves before the survey finishes. See Partial responses for how saved and completed answers differ.

Preview draft and live content

Resize or collapse the preview panel without leaving your editing step. Select Draft to inspect your current edits. For a published survey, select Live to pin its published definition while you continue editing the draft. The Live preview also captures the currently resolved published appearance when selected; it is not a historical theme archive. Select the experiment version separately when applicable.

Changing a draft does not change a pinned Live preview. The preview language must be available in the selected content. Device controls change the preview viewport; they do not change targeting.

The URL bar is decorative context for the preview. It does not load or capture your customer's page. A survey preview is not evidence that a real visitor qualifies, that an event was sent, or that a response reached your site.

Conversation tests use the configured live AI provider and the workspace's test allowance. Changing conversation configuration makes an existing test stale; restart the test to use the updated draft. Test feedback is separate from real visitor responses.

Wait for the draft to save

Questions, settings, translations and layout changes save automatically. Saved confirms the current draft reached the server. Incomplete drafts may need correction before saving or publishing.

If the network fails, unsaved edits stay only in this tab and retry when connectivity returns. They do not survive a reload, tab close or browser restart. Read the save status before navigating away. The editor warns when leaving would lose changes.

If another editor changes the survey, Save conflict keeps your edits in the tab and asks you to reload the saved draft. Reloading discards the unsaved version; it does not merge the two. Preserve anything you need before confirming that reload.

If the result of a save or publication is unknown, use the displayed retry or status action. The editor reconciles the original attempt before allowing another mutation. Do not assume a failed connection means the server rejected the change.

Review and publish

Use Review & publish to check content, targeting, translations and any diagnostics. Publishing waits for the draft save to finish. Confirm publication only when the intended changes are ready for visitors.

Published delivery uses the published version, so later draft edits remain private until the next publication. Connected SDKs pick up published configuration on their next refresh. Verify the result in a development site with a fresh eligible visitor, then check the response in the dashboard. Your first survey provides a complete verification path.