Labels

The SDK renders a small amount of fixed chrome text — navigation buttons, input placeholders, NPS anchors, and the progress counter. You can override any of it to match your tone of voice or translate the survey UI into your app’s language.

Most teams set labels once from the dashboard — see Dashboard → Labels — which needs no app update. Use init({ labels }) only when you want code to override the dashboard (for example, to drive labels from your app’s own i18n system).

Override in code

Pass a labels object to init(). Any key you omit falls back to the dashboard value (if set) and then to the SDK default.

import { MicroSurvey } from "@insito/react-native";

MicroSurvey.init({
  apiKey: "proj_xxx",
  labels: {
    next: "Continue",
    submit: "Send",
    npsLowLabel: "Not likely",
    npsHighLabel: "Very likely",
    progressFormat: "Step {current} of {total}",
  },
});

Available keys

All keys are optional and take a string.

Key	Default	Where it shows
`next`	`Next`	Advance to the next question
`submit`	`Submit`	Submit the final answer
`back`	`Back`	Go to the previous question
`skip`	`Skip`	Skip an optional question
`submitting`	`Submitting…`	Submit button while sending
`retry`	`Retry`	After a failed submit
`otherOption`	`Other`	Multiple-choice “Other” option label
`otherPlaceholder`	`Please specify…`	“Other” free-text input
`openTextPlaceholder`	`Type your answer…`	Default open-text placeholder
`npsLowLabel`	`Not at all likely`	NPS low anchor (under 0)
`npsHighLabel`	`Extremely likely`	NPS high anchor (under 10)
`progressFormat`	`Question {current} of {total}`	Progress counter
`progressFormatShort`	`Question {current}`	Progress counter for surveys with branching logic

The progressFormat and progressFormatShort strings support the {current} and {total} placeholders, which the SDK fills in at render time.

Renaming otherOption changes only the displayed text. The stored answer value for an “Other” selection is unchanged, so your analytics and exports stay consistent.

A per-question open-text placeholder (set on the question in the builder) still takes priority over openTextPlaceholder.

Precedence

Labels resolve in this order, with later sources winning: SDK defaults → Dashboard labels → init({ labels }) This mirrors the theming precedence — code always wins over the dashboard.

Get started

Concepts

React Native SDK

Flutter SDK

Dashboard

MCP server

Override in code

Available keys

Precedence

​Override in code

​Available keys

​Precedence

Override in code

Available keys

Precedence