SurveysCreating a Survey

Creating a Survey

Walk through the survey editor step by step — pick a type, write your question, choose a display and rating style, add a follow-up, and set up detractor routing or a promoter nudge.

Where to find it

Open Surveys

Sidebar → SurveysNew survey

Direct link: https://app.productbridge.io/dashboard/surveys

In-app path: Sidebar → SurveysNew survey

Requires: a plan that includes the app_surveys feature. Without it the Surveys item does not appear in the sidebar.

GoalDirect link
Build, publish, and analyse surveys/dashboard/surveys
Install the survey script on your site/dashboard/settings/survey
A published survey's public linkhttps://app.productbridge.io/s/{organizationId}/{surveyId}

Before You Start

Open Surveys from the dashboard sidebar and select New survey. Creating a survey is a two-step flow: first you pick a type, then you configure it. The type is locked once the survey exists, so choose it deliberately — see Survey Types if you're unsure.

Step 1 — Pick a Type

Choose one of the five types. Each card shows a one-line description and seeds sensible defaults for the question, scale, and rating style so you have a working survey immediately.

Select a type

Click NPS, CSAT, CES, Poll, or Open feedback. The editor pre-fills the question and scale for that type.

Continue to configuration

Move to step 2 to name the survey and tailor its content, behavior, and audience.

Step 2 — Configure

The configuration screen is organized into collapsible sections next to a live preview that updates as you type. The preview uses your organization's brand color, so it matches what recipients actually see.

General

The core content of the survey.

FieldApplies toDescription
Survey name (internal)AllA private label for your team — never shown to users.
QuestionAllThe single question shown in the card.
Answer optionsPollTwo or more choices; drag to reorder.
SelectionPollSingle choice or Multiple choice.
Low / high score labelNPS, CSAT, CESText anchors shown at each end of the scale.
Rating styleNPS, CSAT, CESNumbered, Stars, or Emoji faces.
Lowest / highest valueCESThe editable scale range (lowest 0–9, highest 2–10).
Ask an open-ended follow-upAllAdds a free-text prompt after the main answer.

For scored surveys, enabling a follow-up captures the reasoning behind a score without launching a second survey — the follow-up appears in the same card once the user answers.

Behavior

Controls how the survey displays and when it can reappear.

FieldDescription
DisplayPopover (a card in the bottom corner) or Modal (centered, dims the page).
StatusDraft, Published, or Archived. Only published surveys are shown to users.
TriggerAuto (on page load), Event (when your app fires a named event), or Manual (only when your app calls startSurvey()). See Targeting & Triggers.
Event nameThe event that triggers the survey — used with the SDK's track() call. Applies to the Event trigger.
Delay (seconds)How long to wait after load, the event, or the startSurvey() call before showing the survey. 0 shows it immediately.

The Frequency controls decide how often a user can see the survey after they interact with it:

  • If the user responds — never show again, or show again after a set number of days.
  • If the user closes — never show again, or show again after a set number of days.

Frequency is enforced for identified users only. Anonymous visitors have no stable identity to remember, so recurrence and "show again after" rules don't apply to them.

Audience

Who is eligible to see the survey — everyone, or a specific user segment — plus an option to restrict it to identified users and rules for which pages it appears on. This section is covered in depth in Targeting & Triggers.

Advanced

Available for scored survey types (NPS and CSAT), the Advanced section turns a rating into an action.

Once a survey is saved, the editor gains a Share by link section with a public URL you can copy and send. See Distribution for how the link behaves.

Publish

Set the Status to Published to make the survey live. Eligible users start seeing it on their next matching visit or event. Keep it as a Draft while you're still editing — drafts are never shown, though you can still copy the share link to preview it yourself.

You don't need to redeploy anything to publish. Once your app has the surveys script installed, publishing a survey is enough for it to start appearing.