In This Section
When selecting your audience in the Message or A/B Tests composers, you have the option Target Specific Users, which lets you choose a recipient group based on segmentation data, e.g., a tag, predefined segment, or audience list. Find the data via Search or Explore.
Search by the name of any segmentation data you have about your audience’s user attributes or behavior.
As you type, results will appear in a list, with the data type shown in the left-hand column. To filter by data type, click the dropdown arrow to the right of the search box, then choose a filter. To make a segment selection, click a row in the listed search results.
Available segmentation data and filters for Search:
Not supported for Web Notify: Lists, Device IDs, Predicted to Churn.
Explore the available segmentation data by drilling down into listings of each audience type. Click a type to get started, then choose between Bolded options. Each option displays its definition and/or an example. To make a segment selection, click a row in the listed search results. To go back, click the breadcrumbs in the header of the Explore box. Enter a term in the Filter search box to help narrow your choices.
Available segmentation data for Explore:
As you make your selections, they will appear in the Targeted Audience pane. To remove selections, hover over the item, then click the X icon that appears at the end of its row.
By default we include audience members if they meet ALL the conditions you select. For example, if you selected ALL, with tags “VIP” and “female,” you’d only reach female VIPs. If you selected ANY, you’d reach all VIPs and all females.
Use the ALL/ANY dropdown menu to change your selection.
ALL = all criteria must be met (Boolean AND)
ANY = any criteria must be met (Boolean OR)
If this logic does not meet your targeting needs, you can create a Segment to define more complex, nested logic.
Tags are data set on a device or user to track user attributes or behavior. Tags let you dynamically track user interactions for follow-on retargeting campaigns by setting one or more tags when the user interacts with this push. For example, if you set a tag “responded-campaign1” then you can target them with another message at a later date, knowing they are active users. Alternatively, you can re-engage them with an automated message if they are inactive for a period of time. Use the Set a tag button in the Content step of the A/B Tests or Message composers, or set tags through server API calls.
Urban Airship buckets tags into groups. The primary device tag group tracks anything you set from within your app (Engage) or your website (Web Notify only). You can also configure additional groups to track, e.g., purchase history or CRM data. Search works across all tag groups.
Learn more about Tag Groups.
Segments are predefined groupings of your audience that you can construct using combinations of Tags, Lists, Device Properties, and Location, using the Segments Builder.
Target your audience through our automatically generated Lifecycle Lists, or upload your own custom audience list.
Lifecycle Lists are populated by members of your audience who have performed the following actions in the past 24 hours, one week, or 30 days:
First App Open
Rich Page Sent
Rich Page View
Uploaded Lists are created by uploading a CSV of up to 10 million Named Users, Channel IDs, or Aliases.
Read about working with Audience Lists.
Lists are not supported for web channels at this time.
Urban Airship automatically collects data from your users’ devices, storing them as Device Properties consisting of:
For mobile app platforms:
- Data we collect from your app
- Push, Location, and Background Processing opt-in status of your app
For web browsers:
- Data we collect from the user’s web browser
The best way to understand this data is via the Explore pane.
Mobile apps and Web browsers
Time Zone settings
Mobile apps only
iOS Device Model
iOS/Android app version
Web browsers only
Web SDK Version
Mobile apps only
Notification opt-in status
Background push status
Location enabled status
Use a named user to address all devices for a user through a single identifier. A named user typically maps to a customer identifier in your internal systems, or provides a human-readable way to address your device. Named users are set via the SDK or the API.
See the full documentation for Named Users.
Device-level identifiers are searchable as Device IDs.
See the Channels Primer.
Predicted to Churn
Predictive Churn analyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, and Low Risk.
High Risk: Users most likely to become inactive.
Medium Risk: Users who exhibit signs of potentially becoming inactive.
Low Risk: Users least likely to become inactive.
See Settings: Configuration: Predictive to enable this for your app.