Survey pages

Pages represent the sections in a survey that organize a list of content elements. Most pages contain survey questions or thank you messages, but they can also control survey workflow through logic. Survey takers can navigate through pages using the Back and Next buttons, and when moving to the next page, their partial responses are saved.

Additionally, you can add some special type of pages, which implement special features or an integration with a Medallia partner:

Restriction: Bazaarvoice page is only available for instances with existing implementations.

Add and manage pages

When creating a new survey, the Survey editor comes with the first and last page. The last page contains a Text element with a thank-you message.

You can change the messages content or delete the element and add any other that fits best. See Survey content for more details.

Add pages

On the canvas, hover above or below a page and click Add page (or Add page within the group if the page is part of a group of pages) and select an Empty page or End page to add a new page in that location.

Alternatively, you can add a page by clicking Add page below on the survey structure pane.

Click 'Add Page below' from the survey structure pane or 'Add page' from the canvas.

Select the Create new tab to create any page from scratch, or select Add from to include a page from an existing library. For more information, see Question libraries.

Click 'Add page' to add a new page and 'Add content' to add content elements to pages.

Within a page, hover and click Add content to add any available content element at that location. For more information, see Add and manage content.

Page menu

The page menu — both in the survey structure pane and the preview canvas — displays the general actions that apply to each page, whether they are Empty pages or End pages.

From both the structure pane and canvas, you can:

Duplicate: Copies the entire page including its content elements. Questions and choice sets have new Question and Choice set IDs, as appropriate.
Add a group: Adds a new content group within the page.
Move: Moves the page to another page. Select the page and the target position (before or after) to place the element.
Add to library: Adds the page to an existing Question library.
Hide/Show page: Hides the page from the survey and prevents displaying from survey takers. Page disappears from the preview canvas but persists in the structure pane to make it visible again.
Delete page: Deletes the current page. If the page includes content, you are prompted to decide if you want to move content to another page or delete the content together with the page.

Survey page menu from the survey structure pane and canvas

To edit page details, click on the page name in the structure pane or the page header on the preview canvas.

Reorder pages

After adding page, you can rearrange it to optimize the survey flow and present survey takers a smooth completion path.

To change the order, click to drag the page to reorder and drop it in the desired place. Note that where the page was originally located, now a gray placeholder appears. Additionally, if the target destination is valid, a blue line appears in the survey structure pane showing the page can be located there.

Navigate to pages

From the survey editor, click the survey structure pane menu and select Go to page to choose the page to navigate to.

Go to page under the survey structure pane menu

Empty pages

Empty pages are the most common, since they hold the content to show to survey takers. They begin empty and can be placed anywhere in a survey.

Configuration pane

The configuration pane controls how Empty pages appear and behave. The configuration pane layout is made up of three tabs:

Content — Has all the basic and required configuration needed for the page to work, including:
- Page name — Name that identifies the page in the survey editor. This is not shown to survey takers.
- Button label — Text displayed when survey takers progress past an empty page. Each page can have a different text name depending on how each it should behave:
  - Default — Automatically adapts to the page's location in the survey to become Begin survey, Next, and Finish as appropriate based on the location of the page. When reordered, it changes to reflect its new position.
  - Begin survey — Indicates that when exiting the page, the surveys begins.
  - Next — Indicates that there are further pages that need to be completed.
  - Finish — Indicates that exiting this page immediately finishes the survey.
    Note: Begin survey, Next and Finish are all the different values for exit_event — the event that raises when getting pass a page. Survey engine implements finish_survey by internally setting the Metadata field (M-field) Finished equal to Yes (m_is_finished = 1). The Survey engine renders Finish on the button on the last visible page. However, a page comprised entirely of logic elements is not considered "visible", because the Survey engine doesn't know when the page appears until it is rendered and the conditions evaluated. Consider a page that prompts the survey taker to enter a product code: depending on the code value entered, the next (and last) page might be comprised of logical, follow-up questions. For some codes, there are no follow-up questions.
    Tip: You can customize the button label text using English > English translations. However, note that the button label text belongs to the Shared survey text category, which means that changes to button text string impact all surveys.
- Content options — Allows for randomizing the content elements of the page, which helps to remove order bias. Additionally, you can set the maximum number of page elements to randomize as well as select the ones to exclude from randomization by clicking the pin.
  
  In the following example, Page 2 includes five different content elements, in which up to three of them are randomized for survey takers, except for the third element (What we can do to improve?) which is always excluded from randomized (pinned).
  
  Warning: Consider the intersection of advanced randomization between Show up to X randomized content and Hide/Show element options in the content menu. If a content element is hidden when a page is first loaded, it remains hidden even if you later change it to be shown.
Logic — Includes all the properties related to logical rules and conditions, such as when the page is displayed. See Page logic for more information.
Advanced — Gathers the internal and Experience Cloud-related settings. Empty pages have the option to include extra internal notes about the page.

Important: Style is only visible and editable if it was previously used in the survey. For surveys using v6 designs, entering v6, v5, etc. overrides the chosen design template for that specific page.

Randomize pages

Besides randomizing the content within a page, you can also randomize the order of pages to remove bias. Complete the following steps to randomize pages:

From the survey editor, click the survey structure pane menu and select Randomize pages.
Select the pages to randomize. For example, Page 1 and Page 3.
Optionally, select Create group to generate a group of pages to randomize instead of randomizing individual pages. Click Group.
Optionally, under Additional options, set the maximum number of pages (and page groups, if any) to randomize.
Click Save. Upon saving, pages that were randomized show shuffle in the structure pane.

Restriction: You can't randomize End pages.

End pages

End pages represent the last page a survey taker visits. End pages should contain static, read-only content only, and should be treated as a way to signal survey takers that the survey has ended. It is common to use the End page as a way to thank survey takers for completing the survey.

Each survey must have at least one End page as the last page, though you can add more than one if you have complex logic that could result in different survey endings based on survey takers' answers to questions.

You can only add the following types of content:

Configuration pane

The configuration pane controls how End pages appear and behave. The configuration pane layout is made up of three tabs:

Content — Has all the basic and required configuration needed for the page to work, such as its name and trigger. Trigger determines when an End page closes a survey, and whether survey results are submitted to the Experience Cloud. Select from these triggers:
- No special trigger — It adds a page with back button and progress bar, which makes the survey not to be marked as finished.
- Condition must be met — When the End page Display logic is met, the Trigger closes the survey without submitting it as a valid survey. This is a special End page case when the survey is terminated, but not as the result of submitting the survey. For example, if a survey taker enters a duplicate or invalid "code", or is unwilling to accept the terms of the survey, such as rejecting cookies when they are required.
- Preceding section is set to finish survey and condition must be met— When the End page's Display logic is met, it closes the survey and submits it as a valid survey.
Logic — Includes all the properties related to logical rules and conditions, such as when the page is displayed. See Page logic for more information.
Advanced — Gathers the internal and Experience Cloud-related settings. Empty pages have the option to include extra internal notes about the page.

Important: Style is only visible and editable if it was previously used in the survey. For surveys using v6 designs, entering v6, v5, etc. overrides the chosen design template for that specific page.

Note: End pages can quickly terminate a survey, such as when the survey taker answered a question in a way that invalidated their participation in the survey.

Redirect survey takers to other websites

An End page can redirect to another website, for example to the main company website. To do so, follow these steps:

Add an HTML element in the end page.

On its HTML Markup field, add the following code snippet (replacing the URL for the corresponding website):

<script type="text/javascript">
  (function () {
    var redirectUrl = 'https://www.medallia.com';
    var redirectTimerMsec = 3000;
    setTimeout(
      function () {
        window.location.href = redirectUrl;
      },
      redirectTimerMsec
    );
  }());
</script>

Restriction: Experience Cloud cannot track click-through to the hyperlinks added to the End pages.

Page logic

Page logic manages the settings to display pages in the survey. It includes the following:

Note: Question randomization (and its option to exclude a question from randomization) only appears if it was previously configured in the survey.

Display logic

Display logic is made up of a rule with specific conditions that pages must follow to display their content to survey takers. Display logic decides when to the display the page and it must be met before the page is used in the survey. For example, you might use a Display logic rule to show a page only for survey takers who indicated they want to continue with the survey. For more information, see Logic, rules, and conditions.

Display logic now supports dynamically displaying content in the same page of a survey. For example: display a question based on an answer to a previous question on the same page.

To update display logic for new versions of a survey:

Click the Learn more link.
Click Apply update.
Display logic is updated to the survey draft.
Create a new version of the survey.
Important: Once the update is applied, display logic is updated for all new versions of this survey. However, Experience Cloud does not apply the update to previous versions of the survey.

JavaScript validation

JavaScript validation activates when the survey taker clicks to pass a page. It must be written as JavaScript, and can accomplish several goals. For more information, see JavaScript validation.

A JavaScript icon and a tooltip show which questions use JavaScript validation.

Screen capture showing icon and tooltip marking question with JavaScript validation

Restriction: End pages and TripAdvisor page do not support JavaScript validations.

Note: The Survey engine is responsible for evaluating page logic and establishing its operation order, taking into account two scenarios:

When loading the survey without submitting data, the survey has an assigned page to render, and logic is evaluated for the elements inside the page to determine which parts the survey taker sees.
When loading the survey submitting data, the Survey engine executes:
1. Display logic runs for the elements in the current page, to see which of them are active.
2. JavaScript validation runs only for the active elements. If an element — or any of its validations — fails, the submitted values are not saved and the same page is rendered to the survey taker with the corresponding validation errors. If all validations pass, the data is stored, and surveys moves in the direction the survey taker requested.
3. Display logic runs for the elements in the new page, to see which elements are active. If no elements are active, Survey engine moves to the next page until there is one with active content.