Using the React Native SDK

Survicate allows you to launch precisely targeted surveys inside your app. In the Survicate Panel, you can set conditions that need to be met for the surveys to appear. Users matching conditions defined in the Survicate panel will see the survey automatically. Here's a list of conditions you can use to target your surveys:

• Name of the screen that a user currently sees
• Any application event
• User attributes and identities
• Language of the device
• Operating system

Make sure to list all the screens and events described in your application. Once you got this covered, you or any person responsible for creating and managing surveys will be able to trigger surveys from the Survicate panel with no need for you to update the application.

Targeting a survey by screen name

A survey can appear when a user is viewing a specific screen. For example, a survey can be triggered to show up on the application's home screen after a user spends more than ten seconds there. To set it up, you need to send information to Survicate about the user entering and leaving a screen.

Note: Multiple active screens are allowed. In specific, calling enterScreen() does not make the previous screen to be discarded. Be sure to call leaveScreen() when you no longer want the screen to be treated as active.

Screen name is case sensitive. If there's any discrepancy between what's declared in the ‘Triggers’ tab of the Target section in the Survicate panel and the application code, the survey will not appear.

Events-based survey targeting

The SDK allows you to launch surveys based on events your users trigger in your app. Your survey will show instantly after an event occurs in your app.

Event name and property keys are case sensitive. If there is any discrepancy between what's declared in the ‘Triggers’ tab of the Target section in the Survicate panel and the application code, the survey will not appear.

Passing user attributes

You can provide user attributes to Survicate as an extra layer of information about your users. The attributes have various use cases:

• Identification of survey participants (answers are anonymous by default).
• Directing surveys to particular users (Audience filters).
• Filtering responses.
• Recalling data in questions.

Bear in mind that user attributes are cached. You only need to provide them once, e.g. when user logs in, not after each initilization. You can also change their values at any time to trigger a survey.

Attribute types

• string: any text.
• number: an integer or decimal.
• boolean: a logic value.
• Date: a Date object suitable for use with date or time interval Audience filters (the time interval filter measures elapsed time from a given timestamp).

Special attributes

• user_id: This corresponds to the "Logged-in status" in the panel's Audience filter. A user is considered logged-in when a trait with the "user_id" key has been set on the device, regardless of the value.

• first_name, last_name, email: If none of these is specified, a response will be marked as Anonymous in the panel.

Additional notes
You can set your own attribute keys without any prior registration. They will show up in the panel once any response with the attribute is uploaded.

Response attributes

Response attributes are session-scoped attributes attached to survey responses. Unlike user attributes, they are cleared at the start of each new app session and are sent to Survicate along with the user's survey answers.

To update a response attribute, call the method again with the same name and a new value. To clear an attribute, pass an empty string as the value.

ResponseAttribute accepts the following parameters:

• name (required): The key that identifies the attribute.
• value (required): The attribute value. Pass an empty string to clear an existing attribute.
• provider (optional): The name of the external service where this data comes from (e.g., "hubspot", "intercom"). This helps integrations identify and match your survey respondents with their profiles in that service.

Attribute types

• string: any text.
• number: an integer or decimal.
• boolean: a logic value.
• Date: a Date object

Setting the locale

Survicate SDK automatically detects the device locale and uses it both to choose the translation of a survey and to evaluate any Device language targeting filters.

If your app allows users to change the locale independently of the system settings, you can override the default by calling:

The argument must be a valid IETF language tag such as:

• A two‑letter ISO 639 code (e.g., "en", "fr")
• A three-letter code for languages without the two-letter equivalent (e.g., "haw", "yue")
• A language tag with region (e.g., "en-US", "pt-BR")

Note: The specified locale setting applies only to the current application session. To preserve the preference after an app restart, make sure to call setLocale(...) again, anytime after Survicate.initializeSdk(...).

Theme mode

When your survey has a theme with both light and dark modes, the SDK will select the proper variant following the system setting by default.

Optionally, you can enforce a specific theme mode with the setThemeMode method:

Custom fonts

Using Survicate.setFonts you can specify custom fonts for survey presentation. You need to provide a font path for each font style required by the SDK.

Place your font files in the assets/ directory of your project:

Declare your font files:

Link the fonts to your native projects:

Call Survicate.setFonts() with a SurvicateFontSystem. The paths must match exactly the filenames declared in your assets folder:

Reseting user data for testing purposes

If you need to test surveys on your device, the reset() method can be useful. It clears all user data stored on the device — including survey views, attributes, and information about answered surveys — as well as the current in-memory state of the SDK.

Event listeners

SDK allows you to utilize event listeners. You may find them useful to trigger actions in your application based on actions performed by respondents. Here's a list of events you can subscribe to:

• survey_displayed - occurs when survey is loaded and appears in the User Interface
• question_answered - occurs after a question is answered ( Survicate stores incomplete survey submissions )
• survey_closed - occurs when a user closes the survey using the close button
• survey_completed - occurs when a user finishes the survey

SurvicateAnswer properties (QuestionAnsweredEvent.answer)

The id, ids and value properties are provided only for the cases enlisted in the table above. Therefore, expect that there might be answer objects that consist only of the type property.