Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.insito.app/llms.txt

Use this file to discover all available pages before exploring further.

The Responses view at admin.insito.app → your project → Responses lists every submitted response across all your surveys, newest first.

​
Columns

ColumnMeaning
SubmittedWhen the user tapped Submit. Local timezone.
SurveyWhich survey produced the response.
UserThe userId passed to MicroSurvey.identify(). Clickable — opens that respondent’s full history.
Platformios, android, etc. from identify().
App versionFrom identify().
PreviewFirst answer’s value, truncated. Click the row for full details.

​
Detail view

Click any row to open the response detail panel. Shows:
  • Full answer transcript — every question + the user’s answer, in display order.
  • Respondent metadata — userId, platform, app version, plus any metadata you set in identify().
  • Timing — when the survey was shown vs. when the response landed.
Use the right/left arrow keys (or the buttons in the panel header) to step through responses without closing the detail view.

​
Filters

  • Survey — narrow to one survey at a time.
  • Date range — last 7 / 30 / 90 days or custom.
  • Platform — iOS / Android / both.
  • App version — single or range.
  • Search — free text across answers (matches open-text answers and multiple-choice option labels).

​
Bulk export

Top-right → Export CSV. Same shape as the analytics export but for all filtered responses, not just one survey. Pro+ plans can export the full data set. Free plans are capped at the most recent 100 responses.

​
Respondent history

Click any userId to jump to the respondent detail view. Shows:
  • All responses from this user across all surveys.
  • All screens visited (if you’ve enabled screen tracking).
  • Identify metadata — last identify() payload received from this user.
Useful for support: when a beta tester emails saying “I gave you NPS feedback”, you can find their entry in seconds.

​
Privacy

  • The dashboard never displays raw PII unless your identify() payload contains it (we recommend it doesn’t).
  • Free-text answers are stored as-is; if you collect anything sensitive, scrub it before submission.
  • Use the GDPR delete endpoint to fully purge a user from the system on request.