Survey 2.0 is a significant enhancement to the survey functionality, primarily designed to be integrated with Workflows. Unlike the previous iteration (Surveys in Journeys), Survey 2.0 introduces modularity and reusability, offering a much richer set of features and capabilities. This document provides an overview and guidance on utilizing Survey 2.0 within the Workflow automation platform.
Key Features
- Modularity and Reusability: A core advantage of Survey 2.0 is that surveys can be created once and reused across multiple workflows. This eliminates the need to build the same survey from scratch for every touchpoint, a limitation in Surveys in Journeys.
- Workflow Integration: Survey 2.0 is specifically built for use within Workflows. It cannot be used in Journeys.
- Integration with SurveyJS: Survey 2.0 is integrated with SurveyJS.
- Entity Constraint: A survey can only be attached to a workflow if the workflow's focus entity matches the survey's entity. For example, a survey created for a 'candidate' entity can only be used in a workflow focused on the 'candidate' entity.
Difference between Survey 2.0 and Surveys in Journeys
The key differentiators between Survey 2.0 and the previous Surveys in the Journeys version:
| Feature | Survey 2.0 | Surveys in Journeys |
| Modularity & Reusability | Surveys are modular and reusable across multiple workflows. They can be created once and used repeatedly. | Surveys were de-modular. A survey created for one touchpoint could not be reused and needed to be recreated from scratch each time. |
| Integration | Primarily designed to be used within Workflows and can be attached within email and SMS (via sense modules) workflow nodes. | It was used in Journeys. |
| Question Types | It supports a wider range of question types and leverages integration with SurveyJS. | Limited question types, only supporting Free Text, Date Picker, Multiple Choice, NPS, and Rating (only on a 1-10 scale, with no flexibility to make it 5). |
| Conditional Branching | It supports multi-level conditional branching, allowing visibility of the subsequent question based on multiple rules/conditions. | The visibility of the subsequent question was limited to only one level. |
| Text Piping | Text piping is supported. Responses from previous questions can be dynamically included in subsequent question text or elements. | Text piping was not supported. Responses from one question could not be included in the text of a later question. |
| Theming & Design | It offers flexibility in defining the background theme, font selection, font size, background color, background image, logo alignment, and accent color. The logo and theme color can be automatically taken from brand settings. | No flexibility in defining the background theme, logo alignment, and accent color. |
| Inbuilt Validations | It includes built-in validations for responses, such as date, month, time, email, and number format validation. | No inbuilt validations on responses like email, number, or month. |
| Automation-Friendly | Automation-friendly. Survey completion events and individual responses can be used as filter conditions within automation flows, enabling personalized and dynamic workflows. | Less integration with automation flows. No capability to add dynamic conditions in Journeys, and hence difficult to configure automations. |