In the Configure and Audience tabs of your survey, you can choose the conditions that need to be met to display a survey. You can apply conditions for which screens your survey will appear, what action triggers your survey, which users should see your survey, and set up a recurring display of the survey:
Screens
Under Configure ➡️ Screens, you can define where you'd like to show your survey. This way, you can ensure your surveys are triggered only in the most relevant location.
❗️ Before using this function, information about entering and leaving the screen has to be initialized in the Survicate SDK installation by your developer - click here to learn more.
You can trigger surveys on all screens, or only certain screens:
You can include more screens to display your survey by clicking + Add another screen button:
Would you like to see in the survey's analysis on which screen each user was when they responded? Pass the screen name to Survicate as a user trait in addition to passing it as a screen name, for example:
Survicate.setUserTrait(UserTrait("screen_name", "Screen Name"));
Triggers
You can display surveys after respondents complete specific actions in your app or after they spend a certain amount of time on a particular screen. To do so, navigate to Configure ➡️ Triggers:
Instantly when a user lands on a screen: will trigger the survey as soon as your user lands on the screen defined above
After screen load with delay: Pick the time the survey is displayed after the user lands on your selected page, and enter the duration in seconds.
📌 This option is only available to choose if the survey is targeted at a certain screen.
📌 The user's visit must be continuous for the delay to function properly—it does not accumulate across multiple sessions.
When a user triggers an event: Display the survey after your user completes certain actions in your app. In this case, the survey will trigger as soon as your respondent performs this event. In the dropdown, you should see all event names invoked in your app, so you can choose them for targeting.
Optionally, you can add properties to the event, as well as decide whether the survey should pop up with a delay after the event occurs, after a certain number of event occurrences, or after a specified time has passed since the first or last event occurrence.
You can also add more events via the + Add another event button. If you add more than one event, the survey will be shown if any of the events is triggered.
You can add multiple conditions to your event trigger:
❗️ If you apply more than one filter to the event, all of the applied conditions should be met for a survey to appear.
❗️Event conditions, apart from event properties, are available starting from SDK version 5.2.0. In older versions, these settings will be ignored.
❗️ Event properties are available starting from SDK version 4.4.0
❗️In event properties, the following operators:
doesn't equal
contains
doesn't contain
value exists
value doesn't exist
has any value
are available starting from version 6.4.0. of our Mobile SDK. Operator 'equals' is available from 4.4.0.
Don't show this survey if a user has answered other surveys in the current session: If you are running multiple surveys at once in your app, you might want to limit the surveys your visitors see to avoid bothering them. When this setting is enabled, if your user has engaged with a survey (responded or closed) in their current session, we won't show that survey. The session lasts from the moment the app is opened until it is closed.
Users
You can show your survey to all users that match the selected conditions (triggers and screens), or define a custom audience. To do so, navigate to the Audience tab:
You can use sampling to show your survey to a specific percentage of your users:
Wondering how sampling works? Check the explanation here.
Wondering how sampling works? Check the explanation here.
First, Survicate checks if a visitor meets all the criteria for the survey to be shown:
The visitor matches the audience you set up.
The triggering event from your Target tab occurs.
The frequency settings (how often someone can see the survey) are met.
If the visitor passes all the above checks, Survicate then determines whether they fall within the sample size you defined. For example, if you set sampling to 20%, Survicate generates a random number between 0.0 and 1.0. If the number is less than or equal to 0.2, the survey is shown.
This sampling check is done every time the visitor becomes eligible. The result is not stored. That means:
If your frequency setting allows the survey to be shown only once per visitor, and they qualify the first time, they won’t see it again.
But if your settings allow multiple views per visitor, the sampling check runs each time they become eligible, and they might fall within the 20% again.
You can create a custom audience by clicking +Add audience. There are three audience types to choose from: Users, Visitors, and Manual audience (CSV). We describe the key differences in our What audience type should I choose? article.
If you choose a Users or Visitors audience, you can segment users by parameters such as Attributes, Device language, Operating system, or Screen orientation. Use filters to segment your survey audience:
You can switch between Include / Exclude when adding user information to your Audience (starting from version 4.0.0 of our Mobile SDK):
User attributes
You can assign custom attributes (traits) to your users and target your surveys based on these attributes. Attributes are any information you store about users in your app. You can use attributes to target your survey based on demographics, department, the type of company they work in, their plan, etc.
🧷 To keep things safe and privacy-friendly, do not include any personal data (e.g., name, email, contact details) and specifically any special personal data (e.g., health data, political opinions). If you include them in the attributes used for survey targeting, you risk respondents' data becoming visible to unauthorized parties. We recommend sticking with general data: user types, subscription plans, or broad demographics.
❗️Remember that your developer needs to modify the code to assign attributes to specific respondents. Learn more about it in our documentation for developers.
If you have two or more Attributes in the same audience, you can decide if we should trigger the survey when all of them match the visitor (AND condition) or only one of them (OR condition) - available starting from version 4.0.0. of our Mobile SDK:
If you wish to exclude users with a certain attribute but include users with a different attribute, please add the second attribute by clicking on Add filter instead of on + Add another attribute:
❗️The limit of how many attributes can be passed to one Survicate workspace for all survey types altogether is 2,000.
Device language
Language enables you to target users using the specific language set up on their devices, picking it up from the list. Our code automatically detects the language and doesn't require any SDK customization, since it's not stored as a user trait. You can also trigger the same survey for multiple languages by selecting them from the list:
Operating system
If you have installed the Survicate SDK on both your iOS and Android applications, you can show the survey only to the users of one of these operating systems:
Screen orientation
It’s possible to target your Mobile app surveys by different modes of device screen orientation. Portrait mode or Landscape mode:
❗️The survey with the Screen orientation setting will only appear to respondents if you're using our SDKs starting from version 4.2.0.
Using multiple Audiences
If you have two or more audiences enabled, we trigger the surveys to all enabled audiences. The respondent must match the requirements of at least one of the enabled Audiences (OR condition) to see the survey.
❗ This option is available starting from version 4.0.0. of our Mobile SDK.
Frequency
In Configure ➡️ Frequency, you can adjust your survey frequency to run a single mobile app survey on a recurring basis.
If you'd like each user to only see the survey once, select the "Never show the survey again" setting:
If you want to allow your respondents to complete the survey multiple times, select the option "Recurrence - show multiple times":
Under Recurrence type you can decide whether a respondent should see the survey each time they match the criteria, or if you want to specify the recurrence. Optionally, you can also decide after how long the survey should stop reappearing:
If you're using our SDK version 4.3.0 or newer, you can set a number of days/weeks/months/years that should pass after we’ve shown one mobile app survey to a respondent before we’ll show another one to this person:
💡 You can also set up the Mobile app survey throttling for the whole workspace in Surveys settings ➡️ Throttling which will determine the time frame between showing mobile app surveys from your Survicate workspace to mobile app visitors.
This will also apply to all new Mobile app surveys in your Survicate workspace. However, the survey-level setting (in the Configure ➡️ Frequency tab) can override this global setting.
📌 Setting up survey frequency is available on some of our plans. If you are interested in testing this feature, contact us at sales@survicate.com or strike up a chat conversation
Launch your survey
When you are ready to launch your survey, go to the Launch tab. You can start it right away or set a custom start date. If you select a custom date, we will start your survey on this day at 0:00 GMT.
❗ There can be a delay between survey publication and display. Delays are expected each day 00:00-00:15 UTC due to surveys resetting. Unexpected delays may occur at any time and are often due to heavy traffic.
If you want to run research for a specific number of visitors, you can set a response limit for your survey in the Response limits tab. You can set a Total limit of responses, or a Limit of responses within a period. We will automatically stop the survey when this response limit is reached:
When the periodical Limit of responses within a period is reached, the survey will change its status to Paused with an indication of when it will be reactivated.
Limits of responses within a period are counted on a calendar basis - calendar day, week, month, year. Those limits are counted according to the GMT timezone - for instance, if your survey has a limit of 10 responses per day, it means that it can collect 10 responses from 00:00:00 GMT until 23:59:59 GMT each day. You can also limit responses per clock hour.
❗️If you would like to reactivate it earlier, you need to increase the Limit of responses within a period and enable the survey after that. If you don't enable a survey, it will not be activated automatically when the Limit of responses within a period is increased; you need to enable it on your own.
📌 If the respondent opens the survey before it was disabled and answers it while it is disabled, the response will still be collected and recorded.
In the End date tab, you can choose to stop your survey on a specific date. We will stop your survey on this day at 0:00 GMT.
📌 Whenever you make changes to your survey's setup, they take a couple of minutes to take effect.
📞 If you have any questions or need help setting up the Mobile SDK, please reach out to our team at support@survicate.com.