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 survey builder lives at admin.insito.app → your project → Surveys → New survey. This page walks through each step.

​
The builder

A survey has four parts:
  1. Basics — name, trigger key, status.
  2. Throttling — how often a single user can see this survey.
  3. Questions — 1 to 10 questions of four types.
  4. Audience (optional) — platform filters.
Each is its own section in the builder; you can save a draft at any time and come back later.

​
1. Basics

​
Survey name
required
Internal label only — never shown to users. Use something descriptive (Post-checkout NPS Q2 2026) so it’s easy to find in the survey list later.
​
Trigger key
required
The string your app passes to MicroSurvey.trigger(). Must match ^[a-z][a-z0-9_]*$ and be unique among active surveys in this project. See Triggers.
​
Status
default:"draft"
draft = never shown to users. active = eligible. inactive = paused (still in the dashboard, just not served). Toggling active/inactive takes effect within seconds — no app rebuild needed.

​
2. Throttling

​
Cooldown days
default:"28"
Once a user sees this survey, they won’t see it again for this many days. The default is 28 days which matches industry NPS conventions. Lower numbers are okay for a beta funnel; higher numbers risk overfitting.
Throttling is per (survey, userId) pair. Different surveys fire independently — a user can complete an onboarding survey and still get a checkout NPS later the same week.

​
3. Questions

Add 1 to 10 questions. The user sees them one at a time inside the modal; they can swipe back if isRequired is false on a question.

​
Question types

NPS (0–10)

The standard NPS scale. Detractors (0–6), passives (7–8), promoters (9–10). Insito auto-scores responses and computes the canonical NPS in the analytics view.

Rating (1–5)

Five-point star rating. Best for “how easy was that?” or feature satisfaction.

Multiple choice

Single-select by default, multi-select toggleable. Each option is a free-form string up to 80 characters.

Open text

Free text input with a configurable max length (default 280 chars). Lands verbatim in the responses tab.

​
Common patterns

Pure NPS (one question, two if you want a follow-up):
  1. NPS: “How likely are you to recommend us to a friend?”
  2. Open text: “What’s the main reason for your score?”
Feature satisfaction (three questions):
  1. Rating: “How satisfied are you with this feature?”
  2. Multiple choice: “What did you like most?” — ["Speed", "Reliability", "Design", "Other"]
  3. Open text (optional): “Anything else we should know?”
Onboarding effort (one question):
  1. Rating: “How easy was it to set up the app?” — labels Very hard–Very easy.

​
Required vs optional

Toggle Required on each question. Required questions block the “Next” button until answered; optional questions show a “Skip” affordance. Open-text questions ignore the required flag if the user submitted at least one character of whitespace, so be explicit in your question copy.

​
4. Audience (optional)

Filter who sees the survey by:
  • Platform — ios, android, or both.
  • App version — exact match, range, or “any”. Useful for cohort studies (only ask users on the new build).
Filters AND together. If the user’s identify() payload doesn’t include the field a filter requires, they don’t see the survey.

​
Activate and ship

1

Save the draft

Save at the bottom. The survey appears in your project’s survey list with status draft.
2

Preview

Use the Preview button (top right of the builder) to render the modal exactly as the SDK will. No data is recorded — it’s a static preview.
3

Activate

Toggle status to active. Within a few seconds, the next call to MicroSurvey.trigger(yourKey) will be eligible.

​
Editing live surveys

Editing an active survey is safe — changes propagate within seconds to all users. There are two caveats:
  • Changing the trigger key rewrites history. Existing responses stay attached to the new key, which can be confusing if you’re comparing across rollouts. Prefer creating a new survey under a new key (e.g. checkout_completed_v2).
  • Removing questions soft-deletes them — historical answers are preserved but won’t appear in the new analytics roll-up. Add a new question instead of editing an old one’s text if you want before/after analytics.

​
Next

Triggers in the dashboard

The triggers view — see which keys are wired and to what.

Analytics

Read NPS, response rate, and per-question breakdowns.