One builds an app by adding a selection of “Actions,” which are calls-to-action for either content or functions. Audience control let’s one choose whether an individual Action will be visible only to users viewing an app through their browser, only to users viewing an installed app, or to both. App owners can use the feature to create different user experiences for different categories of users
For example, 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 additional or premium content that is visible only to the loyal users who have installed the app by setting the audience these Actions to “App.”
“All” is the default audience for an Action, which means it will display to all users, no matter how they access the app.
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 a browser experience that focuses on utility.