Skip to content

Publishing a survey ​

INFO

A survey must be 'Published' and active before it can collect responses. If your form has changed, a new version must be built and published before the changes are seen by respondents.

Context ​

Respondents will access your survey using links. The Link Builder generates these links for you and provides extensive control over the respondent experience.

TIP

Your survey links remain the same whenever a new version of the survey is published, so you never need to worry about updating shared links.

Step 1: Choose a Publishing Strategy ​

Before distributing the survey, you can set the strategy for making the survey active (e.g., immediate, manual, or scheduled). This determines when the survey becomes available to respondents.

Choose the strategy for publishing
Select the strategy for making the survey active.

Step 2: Build a New Version ​

Before sharing, you must build a version of the form to ensure all recent changes are compiled and ready for production.

  1. Navigate to the Publish tab.

    Navigate to Publish
    Click on the Publish link.
  2. Click on the Create a new Version of the... button.

    Create a new version
    Click the Create a new Version button.
  3. You will be prompted to give the version a label (e.g., "A new version to share"). This helps you differentiate between different builds of the survey. Click to build the survey.

    Build the survey dialog
    Provide a versioning message and confirm the build.

Resolving Build Warnings (Duplicate Question Codes) ​

During the build process, the system validates form integrity. If any issues are detected, the build report displays warnings describing the problem and identifying the affected items.

The most common build warning is a duplicate question code. Question codes determine how responses are keyed in the database and exported in CSV and JSON datasets. By default, a question's code is automatically derived in camelCase from its label. If two or more questions share similar starting phrasing, their generated codes can collide.

To resolve a duplicate question code:

  1. Navigate to Build → Compose.
  2. Switch on Advanced Mode using the toggle in the builder toolbar.
  3. Select the question identified in the build warning from the survey tree to open its settings drawer.
  4. In the Question Code (build.code) field, enter a unique, descriptive camelCase identifier (for example, feedbackService instead of an auto-generated duplicate).
  5. Return to Publish and build a new version. The warning will clear once all codes are unique.

Step 3: Take the Survey to Production ​

Building a version prepares the survey, but it does not make it live yet. The production link stays hidden until you explicitly take the survey to production. Taking a survey to production:

  • reveals the production link you share with respondents, and
  • redeems one survey from your plan's quota.
  1. Navigate to the Distribute section.

    Navigate to Distribute
    Open the Distribute section.
  2. A Survey quota card below the button shows how many surveys are left on your plan and how much of the plan has been used. It is shown until the survey is in production; after that, the quota is on the Status page.

    Survey quota left on the plan
    The remaining survey quota and the used share of the plan are shown in the quota card.
  3. Click Go to Production.

    Go to Production button
    Take the survey to production.
  4. Confirm the action. The dialog states what the press costs (for example, "redeems one of the 5 surveys left on your plan"); it cannot be undone.

    Go to Production confirmation dialog
    Confirm that you want to take the survey to production.

Once the survey is in production, the Display Link for Production button is revealed next to the test link:

Display Link for Production
The production link becomes available once the survey is in production.

WARNING

Taking a survey to production cannot be undone and redeems one survey from your plan's quota. When your plan has no surveys left, buy more quota before taking another survey to production.

Once the survey is in production, the Distribute section gives you access to the Link Builder. This tool gives you granular control over the type of link you generate.

Test vs. Production Modes ​

  • Test Mode: Generates a link used to preview the survey. Respondents' answers are not saved to the database. You can optionally skip the landing page while testing.
  • Production Mode: Generates the link you share to collect real responses. Answers are saved to the database automatically.

Production Deployment ​

Clicking Go to Production redeems one survey from your plan's active survey quota and marks the survey as in production. Once confirmed, the Display Link for Production button becomes available to generate and copy your live survey link.

Displayed production link
Click the Display Link for Production button to get the real URL.

Step 5: Preselect Options (Optional) ​

When generating the link, you have the option to preconfigure certain settings so the respondent gets a tailored experience immediately upon opening the link. These options include:

  • Select a language:

    Select language
    Preselect the default language for the survey link.
  • Select a sign language:

    Select sign language
    Preselect the default sign language.
  • Select accessibility modes:

    Select accessibility modes
    Preselect specific accessibility modes like Read Aloud or Easy Read.

Once you have configured the desired options (Test/Production, options, and accessibility pre-selections), copy the generated link and distribute it to your audience. You can share it via your website, email, or social media.

Copy link to share
Copy the final production link and share it.

Link Shorteners

If you are using a link shortener to share your survey, be aware that some services do not handle URL parameters properly. Because features like language selection and accessibility modes rely on these parameters, always test your shortened link to ensure the survey loads correctly and your intended settings are preserved.