How to Use Dynamic Text Customization Within Your Native SDK

In Qualaroo, you can personalize messages in your native SDK surveys to increase the likelihood that your visitor will provide feedback. The Dynamic Text Customization feature lets you personalize your visitor's feedback experience! 

This article details how to implement this feature and provides a few use-cases to help you get started.

Customizing text within your native SDK surveys lets you:

• Leverage custom properties to insert personalized user information into placeholders within your questions' titles and descriptions. 

• Provide a more inclusive experience and collect valuable feedback from respondents.

Minimum Requirements:

Android SDK version - 1.7.1

iOS SDK version - 1.7.1

To Implement This Feature:

Begin by including a special placeholder in the survey's Create/Edit tab within your Qualaroo dashboard. Placeholders are supported for your questions' titles and descriptions only.

An example placeholder is: ${custom_property_name}

custom_property_name stands for and is replaced by some custom property that our customer has set inside their application via our SDK.

For example, let's say the first question has a title (or description): "Hello ${first_name}!"

When the Custom Property is set via the setCustomProperty("first_name," "Jacob") method call, the user will see a question with the title: "Hello Jacob!" when they are prompted for feedback.

Custom Properties must be set before conducting a survey (properties being set while running a survey will not modify the current live survey).

Use case 1:

Consider you are running a confirmation survey, and a new user named Joe has just completed the sign-up process. You would like to greet him by name and ask him how he discovered our product. Keeping track of all properties related to our users is very important, so you store a Custom Property within our Native SDK right after the user signs up.

This property is named “first_name,” and I set it to "Joe." With those conditions met, I can run a survey that could look like this:

"Hi ${first_name}! So happy to have you here! How did you learn about this app?"

- "it was recommended to me by a friend"

- "I found it on Google Play"

- "I heard about it on the radio"

Use case 2

If you want to divide the user base into two cohorts: Active and Passive users.

Active users are generally eager to participate in any activity, such as replying to a Qualaroo survey. Passive users tend to require more explanation before they agree to provide feedback.

For Active users, you can set a Custom Property "additional_description" to "" (which stands for empty text).

For our Passive users, you can set an "additional_description" to "Answer this question and get a chance to win a wonderful prize!"

Once the Custom Properties are set, the survey logic looks like this:

"Should the app include the dark mode for using at night?" <- title

"${additional_description}" <- description

- "Yes!"

- "I don't need it"

For Active users, this survey will look like this:

"Should the app include the dark mode for using at night?"

- "Yes!"

- "I don't need it"

While passive users will see:

"Should the app include the dark mode for using at night?"

"Answer this question and get a chance to win a wonderful prize!"

- "Yes!"

- "I don't need it"

Use case 3

Say you have a hotel booking app and want to run a template survey whenever a user finishes their stay. Whenever you detect that it’s time to show a rating survey, set two custom properties:

• ${hotel_name} to hotel’s name

• ${hotel_city} to the city that the hotel is located in

Once those properties are set, we can run the following survey:

“Hey! Your trip to ${hotel_city} seems to have finished! How would you rate your stay at ${hotel_name}?”

• 0 - 10 (NPS)

So, the survey would look like this:

“Hey! Your trip to Cracow seems to have finished! How would you rate your stay at Hotel Chopin?”

• 0 - 10 (NPS)

That is all about dynamic text customization within your native SDK.