Targeting helps you intelligently interact with the right customers, in the right place, at the right time. Targeting interactions with your customers proposes a delicate balance. You want to achieve a positive experience for your user while still gaining vital information about their time using the app. In the dashboard, under any interaction (excluding Message Center), there will be a tab for “Targeting.” Here is where we will customize our prompt.
The first targeting tool is called “Who,” which segments out customers based upon certain predetermined attributes and actions. Making sure you set fair and precise standards can ensure you receive feedback from the users you want. Additionally, be sure you are not interacting with any one customer too frequently by adding additional parameters around how many Notes or Surveys each customer has seen over a given period of time. For instance, you may want to add a “Who” threshold to not show a Note to a customer if they have already seen another Note or Survey in at least fifteen days. There are two different ways we can segment (and both can be combined). First, adding a segment (like pictured below) is a good start. Here, we set the interaction only to occur for users with their language set to Japanese.
There are two different paths we can take at this point. We can set an or statement by clicking the far bottom ‘Add A Segment’ button:
Which would mean that all users shown the prompt would need to have their language set to Japanese or their app version is 1.2.3. Another option would be to add an and statement, by clicking the ‘Add A Segment’ button closest to the segment we want to pair it with:
Which would mean, all users shown the prompt would need to have their language set to Japanese and their app version set to 1.2.3. As previously stated, these options can be combined in many different ways, to achieve specific audiences from your userbase.
Next is “Where,” which relies on defined Events. Events are times and places in your app that help you to understand the customer is using your app for it’s intended purpose. They must be defined in-app as well as on the Apptentive dashboard. It is important that, considering the context of your app, you define actions taken in your app where you would be catching your user at a significant but not intrusive time. These can either be positive (
made_purchase) or negative (
app_crashed) if you wanted constructive critiques. We recommend having 10-20 pre-defined events. To continue the previously defined flow, this would decide where the user with their language set to Japanese would see the prompt they are eligible for.
Some more examples
- Clicked specific button
- Purchase view opened
- Payment made
- Completed level
- Shared something on a social network
- App crashed
- Logged a diary or achievement
How Often / When
In this section, we determine the duration and parameters around which the prompt will be shown. Some interactions work off of “How Often,” others, off of “Where.” Specifically, the Ratings Prompt will never show to any particular customer more than once per app version. You can choose to only show a prompt to a person once, ever. Or, you can choose to show once per person for each version of your app released. Meaning, for each app release, a person’s interaction opportunity will be refreshed and they will be prompted again within the next selection.