Similarly to how it works in our Web product, App Campaigns are used to collect feedback from a specific group of users. We have a number of targeting options available to help you set this up. These can be found on the "User targeting" page of your Campaign editor.
The targeting options work based on AND logic, meaning all active criteria have to be met for the Campaign to show.
Target on the following event X
One of the key aspects of running an App Campaign is an event. When an event occurs in your app, it allows you to trigger a Campaign based on it. This can be initiated by the user (e.g. clicking a link) or by the app itself (e.g. the user's flight has just arrived).
We have dedicated a whole support article to this targeting option, which goes through what they are, how they're created, as well as some examples to help you decide based on what event you should trigger your Campaign. You can find it here.
Apart from adding the event name in the Campaign editor, you'll also need to make sure that this event is sent by your app to our SDK. This can be done via the sendEvent() method, which you can read more about in our iOS and Android documentations.
Show campaign when the event has occurred X time(s)
By default, the Campaign will be triggered after the event occurred once in your app, however, you can set the number of times an event has to occur before it is displayed to your users.
Show campaign when the custom variable apply
Custom variables are little bits of data that you can include when a user leaves feedback through your Campaign. They're used to add extra information about your user or the application about which the user left feedback. Furthermore, you can also use them to target a specific group of users with your Campaign.
You can target based on multiple custom variables at the same time. These work based on AND logic, meaning all custom variables you add have to be a match for the Campaign to trigger.
Aside from defining the variables in the Campaign editor, you'll also need to make sure they're sent form your application to our SDK. You can find the method you need to use for this in our iOS and Android documentations.
Some examples of data you could send along as custom variables:
- user ID
- email address
- subscription type
- shopping cart value
- whether the user is logged in or not
Show campaign when the device language is set to X
This targeting option can be helpful if your application is available in multiple languages and therefore planning to run Campaigns in different languages as well. It's important to highlight, that this is option is based on the device's language and not the app's language.
% of the visitors
If you'd like to limit the amount of people who can see your Campaign, an option would be the % targeting.
The way it works in the background is that when there is an event ready to be triggered, the user has X% chance of being included in the group of users who'll be eligible to see the Campaign. For example, if you set it to 50%, they'll have 50% chance of seeing it.