Surveys

Surveys collect targeted answers from signed widget users without sending them to a separate survey product.

Survey Types and Questions

Create a basic survey, Net Promoter Score survey, or customer satisfaction survey. Questions can use rating, NPS, text, single-choice, multiple-choice, or yes/no responses and can be marked required.

Each survey includes customer-facing question text, optional follow-up text, a thank-you screen, and one of nine display positions. Answers must match the configured question type, range, and choices. Managani stores only the normalized answer: a whole-number score with optional text, the selected choice value (a submitted choice label maps to its value), unique choice values, yes/no, or trimmed text. Customers must answer required questions before completing a response. Paused or closed surveys no longer accept answers or completions.

To draft a survey with AI, click Suggest with AI and describe the goal. Managani suggests exactly one question and opens it in the survey editor with the survey title and description filled in, the suggested question text placed in the question fields, and the answer input and single-selection options matched to the suggested question type. Review it, then click Save to create the survey. Nothing is saved until you save the editor.

Triggering

Surveys can be triggered:

• Manually from your application
• On a matching URL using contains, starts-with, or exact matching
• By a named product event sent through tracking

Configure delay, sample rate, once-per-user behavior, page matching, audience segments, and an optional automatic end date. A survey can be draft, active, paused, or closed. With once-per-user enabled, opening the same survey in another tab resumes the unfinished response. Completed or dismissed responses prevent another start until the survey is reset. Starting or dismissing a survey does not lock the survey, so many visitors can respond at the same time.

Results

Open a survey to review its responses and response count. Resetting a survey clears its collected run state when you need a fresh campaign; use that action carefully.

When you or a teammate saves or resets a survey, only that survey row updates in the list. The row moves between Active and Inactive when its status changes. If you switch sites while a save finishes, its result stays with the original site.

Surveys require a signed widget user so every response stays linked to the correct customer.

Plan a Focused Campaign

Choose one question the team needs to answer before selecting a survey type. Use satisfaction questions after a relevant interaction, or ask an open text question when you need to understand why customers struggle with a workflow. Keep required questions limited to information needed for that decision.

Match the trigger to the experience being evaluated. A named product event can place the question after a completed action, while a URL rule can target users visiting a particular part of the application. Confirm the signed customer identity and event name before activating the survey.

Start with a controlled audience and verify the delay, display position, and once-per-user behavior. Check that the thank-you screen appears after completion and that the response is attached to the expected customer. Review the answers before broadening the campaign. Pause collection when you need to adjust the question, and preserve useful results before using any reset action.