In-App Surveys enable brands to gather solicited feedback directly within their mobile apps during key customer interactions. You can choose from pre-designed formats like micro-surveys or create fully customized pop-ups to align with your brand. Creatives can be activated based on set criteria, like browsing habits or the length of a session, or they can be initiated by custom events to gather specific feedback. You can also refer to In-Apps article for use cases and value additions.

Prerequisites

You would need access to the Survey Level View and Edit Distribution in order to access In-Apps distribution.

Setting up the In-App distribution with Trigger Conditions

1. Go to Distribution page.

   ​

2. Click on Create Distribution and select In-App distribution.

   ​

3. Define Distribution Details:

   ​

   1. Distribution Name: Enter a meaningful name to the distribution.

   2. Expiration Date: Enter an expiry date.

   3. Live Chat Application: You can select an existing LiveChat application or create a new one. Any proactive prompts related to the chosen LiveChat will be displayed in the dropdown menu. If you select an existing LiveChat, you will also be able to see all other distributions tied to that particular LiveChat instance.

      

      Note: Selecting a LiveChat here does not immediately display a live chat on the Mobile App. Instead, it links the proactive prompts to the appropriate code required to render the creative within the app.

      The LiveChat ID is utilized during the SDK installation process.

4. Click Next and go to Setup Conditions:

   ​

   Add Variant details (one can select multiple variants. Variant details help to define the trigger condition). 

5. Variant Name: Add variant name. 

6. Intercept Condition: Define the criteria that will trigger the survey. Start selecting conditions. Keep adding conditions by clicking on + Add Condition. (Multiple conditions can be added). There is also a possibility to add condition group by clicking on + Add Condition Group.

   ​

   Intercept Conditions & Operators

   Operators

   The following operators will be used while setting up conditions. They will change depending on the condition.

   Operators	Description
   Containing	“Containing” verifies if the value exists in the parameter.
   Not Containing	“Not Containing” verifies if the value does not exist in the parameter.
   Greater Than	“Greater Than" refers to a value that is larger than the one specified in the parameter.
   Greater than or equal to	“Greater than or equal to” refers to a value that is either larger than or exactly equal to the specified parameter.
   Less than	"Less than" refers to a value that is smaller than the specified parameter.
   Less than or equal to	"Less than or equal to" refers to a value that is either smaller than or exactly equal to the specified parameter.
   Equals	"Equal" refers to a value that is the same as the specified parameter.
   Not Equals	"Not Equals" refers to a value that is different from the specified parameter.
   Contains	"Contains" refers to whether a specified value is present within a set, string, or collection.
   Regex	"Regex" is a pattern used for matching text in strings.
   Does not contain	"Does not contain" refers to when a specified value is absent from a set, string, or collection.

   Conditions

   The following conditions are supported to create In-App intercepts:

   Conditions	Value	Definition
   Operating System These conditions allows targeting users based on the operating system (e.g., iOS or Android) or its version.
   Device and App Info	iOS and Android	You can select the operating system for running the survey.
   App Version	iOS and Android	You can select App Version for iOS and Android.
   App Usage during a Session These conditions track how frequently and actively users engage with the app while they are in a session.
   Condition	Value	Definition
   Screen Views	Add a numeric value. There can be dependent condition set for App Screen ID.	Screen views define the number of views on the screen. The views are reset after every app session.
   Button Click Count	Under dependent, conditions add App Button ID and select operator and enter value.	Button click count defines the number of times button is clicked.
   Session duration	Enter time duration in minutes and seconds.	Session duration defines the duration of one mobile app session. A session refers to a period of continuous interaction with an app or service, starting when a user opens the app and ending when they close it or become inactive for a set amount of time.
   App Usage over time This condition tracks the frequency of app engagement over different time intervals. Note: Not enabled by default Due to certain architectural considerations, these conditions are not enabled by default. Please reach out to the product team with a specific use case to assist you in enabling them if required.
   Condition	Value	Definition
   Daily App Usage	Enter time duration in minutes and seconds.	This defines the frequency of app engagement on a daily basis, calculated using a 90-day rolling average
   Weekly App Usage	Enter time duration in minutes or seconds	This defines the frequency of app engagement on a weekly basis, calculated using a 90-day rolling average
   Monthly App Usage	Enter time duration in minutes and seconds.	This defines the frequency of app engagement on a monthly basis, calculated using a 90-day rolling average
   Geographic Region This condition allows targeting based on the user's geographical area.
   Condition	Value	Definition
   Geographic Region	Select value from the drop down.	The Geographic Region defines the country the customer is located in.
   User Country	Select Country from the drop-down menu.	The User Country defines the country the customer is located in.
   Manage Repeated Displays Control how often creatives or surveys are shown to users, preventing repetition within a specified timeframe.
   Condition	Value	Definition
   Creative Shown	Enter "Last Shown" greater than "time",in minutes or seconds or days.	This condition can be used to control repeat displays. For example, use this to prevent triggering creatives if a creative was shown in the last 30 days.
   Survey Completed	Enter "Survey Completed" greater than "time", in minutes or seconds or days.	This condition can be used to control repeat survey displays. For example, use this to prevent showing a survey if it was completed in the last 30 days.
   Creative Dismissed	in minutes or seconds or days.

   Note: The conditions can be added using a combination of AND or OR operators, or both. Additionally, condition groups can be created using the same combination of operators to tailor targeting criteria more precisely.

7. Creative: Create the Creative and look at the preview (Learn how to create a creative at the end). To find more details refer to this article.

   ​

8. Schedule: Click Schedule and set the time zone, start date, and end date for when the survey should be distributed.

   

   1. Time Zone: Select the time zone for sending the survey. 

   2. Start Sending From: Select the start date for sending the survey. 

   3. Stop Sending From: Select the end date to stop sending the survey. 

      Note: We have the ability to regulate the number of times surveys can be completed, even if the conditions are met. For instance, if we set this limit to 1, you will need to exit the app and reopen it in order to fill out the survey again, which helps prevent spam.

9. Disable Auto Trigger for Variant: Enable this option to prevent the creative from automatically displaying when the variant is evaluated and the conditions are met.

   

   Note: Disabling auto trigger provides the client app’s developer with greater control over when the creative is shown, allowing for more customized user experiences.

   This will be discussed in the In-App SDK Documentation

10. Click Create and Enable to create the distribution in active state.