You can create In app surveys to collect feedback from your users. There are three different types of In-app Surveys that you can create:

• Custom Survey: create a set of customized questions using different question types
• NPS Survey: find out whether your users would promote your application or not, then have them rate your application
• App Rating: ask your users if they like your app. If they answer yes, they'll be prompted to rate your application

Surveys

You can choose between three types of surveys when creating a new one: Custom Survey, NPS Survey, and App Rating.

Custom Survey

Create your own custom surveys with any number of questions displayed to your user one by one, sequentially. You can select between three types of answers:

• Text Field: The user must answer the question by typing their response in a text field.
• Multiple Choice: The user must answer the question by choosing one of any number of answers you have defined in your dashboard.
• Stars: The user must answer the question with one to five stars.

This type of survey can use both manual and automatic targeting.

NPS Survey

The default first question in an NPS Survey is "How likely are you to recommend to a friend or colleague?" The user must reply on a scale of 1-10, least to most likely.

Depending on the rating given by the user, they will be shown one of two possible follow-up questions:

• User rating is 9 or 10 (Promoter): The user will be asked for feedback about how to improve the app. You will also have the option to allow the users to rate the application while creating the survey. A link is generated to your app on Google Play. The user will be asked to rate your app. If they accept, they will be redirected to the Google Play link. If your app is in beta, or if your app is not available on Google Play, the user will instead be asked to submit their survey.
• User rating is 7 or 8 (Passive): The user will be asked for feedback about how to improve the app. You will also have the option to allow the users to rate the application while creating the survey.
• User rating is less than 7 (Detractor): The user will be asked for feedback about how to improve the app.

This type of survey can use both manual and automatic targeting.

From your dashboard, you can customize the text of any question in an NPS Survey.

App Rating

This template is used to identify happy users and ask them to rate your app.

First, your users will see an alert, native to the OS, which asks if they are satisfied with the application.

• If the user answers yes, they will be asked to rate the application on the Play Store in another alert automatically. If the application is in beta mode, the user will not be asked to rate on the Play Store.
• If the user answers no, they will be asked how the application can do better in a survey format similar to the one in the custom survey section.

This type of survey can use both manual and automatic targeting.

You can set the frequency for how often this message shows. By default, it is set to every 30 days.

📘

Changing the Alert Text

During the creation process, you can edit any of the text that will be in the alerts shown to the users.

Survey Localization

You can display your surveys and announcements to your users in their language. To do this, you only need to add the locale when creating the survey, then add the questions in that language.

Editing Survey Locales

There are some rules that should be adhered to when adding and editing locales and languages for surveys and announcements.

Default Language

Every survey and announcement you create must have a default language. This default language is used when no locale is set and you don't support the device's current locale, so make sure you set the right default language. By default, the default language is set to English.

For each locale you add, a new tab will be added in the dashboard from where you can modify the text that will be displayed for that locale. Other changes to the survey, like adding or removing questions, can only be done from the default locale tab.

Determining Shown Locale

The SDK determines which survey language is shown based on a few priorities. If you use the set locale API, this locale will take precedence over the device locale so the survey will be shown in the locale you set through the API. Otherwise, surveys will be displayed in the language that matches the device locale. In case you don't support this locale, the survey will use the default language.

To summarize, in order of priority:
1 - Locale set through API (as shown here)
2 - The device locale
3 - Default locale set through the dashboard (if device locale isn't supported)

Supported Locales

Currently, most locales supported by the SDK are supported in the survey localization, with more locales to be added soon. Below is the list for supported locales.

- English en
- Arabic ar
- Czech cs
- Danish da
- German de
- Spanish es
- French fr
- Italian it
- Japanese ja
- Korean ko
- Dutch nl
- Norwegian (no, nb) --> nb-NO
- Polish pl
- Portuguese Brazil pt-BR
- Portuguese Portugal pt-PT
- Russian ru
- Slovak sk
- Swedish sv
- Turkish tr
- Chinese Simplified (zh-hans, zh-CN) --> zh-CN
- Chinese Traditional (zh-TW,  zh-hant-TW, zh-Hant) --> zh-TW
- Hindi hi
- Greek el
- Finnish fi
- Estonian et
- Romanian ro
- Vietnamese vi

📘

Backwards Compatibility

Multiple locale surveys will appear starting from version 8.3. If you're targeting older SDKs, only the default survey locale will be shown. All surveys created before version 8.3 will continue to work with only a single locale.

Duplicating Surveys

If you need to create a copy of an already existing survey, you can duplicate it by opening the survey itself from the survey list, and clicking on the duplicate button in the survey results page. Please note that any duplicated survey is placed directly in a draft state, so you'll have to publish it manually once the duplication is complete.