PlatoForms User Guide
Design forms for Insights
Tabs
The fields and structure of a form determine which analyses Insights can provide. Use this guide when creating or updating a form to check which question types are required for specific charts, visitor journey measurements, and data-quality checks.
| If the form has… | Insights can show… |
|---|---|
| Choice / dropdown questions | Pies, columns, breakdowns, cross-tab matrices, significance chips |
| A rating or slider (any scale) | Statistics card (median, quartiles, spread), distributions |
| A 0–10 rating (“How likely are you to recommend…”) | NPS chart, NPS pack, NPS alerts |
| A short-text question | Top answers, example-answer quote walls |
| A long-text question (“What could we improve?”) | Word cloud, AI themes & sentiment, AI summaries |
| An email field | Duplicate-submission detection in Data quality |
| Two related choice questions (e.g. source × plan) | Breakdown charts and the cross-tab matrix |
| Multiple pages | Per-submission fill duration (better speeder detection) |
Example survey structure
To make the listed feedback analyses available, a survey can include:
- One How did you hear about us? choice question.
- One satisfaction rating from 1 to 5.
- One likelihood-to-recommend rating from 0 to 10.
- One open-text What could we improve? question.
- One email field.
This structure supports the customer feedback pack, NPS pack, sentiment analysis, word cloud, significance testing, and duplicate-submission detection.
Requirements and data behavior
- To collect field-level Journey data, publish or re-publish the form. Field-level data is collected only from form pages published after Insights launched. Page opens are recorded for all forms, including forms published earlier.
- Statistical features appear only when enough data is available. Significance chips require at least 30 responses, unusual-day markers require a few weeks of daily history, and the Journey leak and worst-field markers require at least 100 visitors. Below these thresholds, the related features remain hidden.
- Charts count submissions rather than submission events. Re-submitting or editing an existing submission updates its values instead of counting it again.