One builds an app by adding a selection of “Actions,” which are calls-to-action for either content or functions. Audience control lets one select the audience that will see an individual Action.
With the setting above the designated Action would be visible only to Android users who have installed their and have subscribed to push messages. The value is that premium content can be used to incentivize users to install an app and/or to enable push messages,
App owners can use the feature to create different user experiences for different categories of users.
For another common use case, if one adds an Action such as an “In-App” message promoting the user to install the app, one does not want that message to display to the users who have already installed the app. By setting the “Audience” to “Browser”, the in-app message will display to users viewing the app through their browser but not users who have installed the app.
Similarly, one can have device-specific instructions on how to install an app that are visible when the app is browsed but are not visible after the user installs the app and the directions are no longer relevant.
“All” is the default audience for each audience category.
Other use cases for having different content visible to browser vs app users include:
- Having a simple landing page for browser users that transforms into a rich useful app when installed.
- Offering additional or better deals for users who install an app.
- Having a browser experience that focuses on recruitment and an app experience that focuses on utility.
The most common audience control will be Browser vs. App, where users get an enhanced experience if they install an app. The app preview has a toggle above it (shown below) that will enable one to instantly toggle between the App and Browser views.