- Send an announcement about a new app version and encourage users to upgrade. — Identifier: app version
- Send messages to a list of users created from your CRM data. — Identifier: Audience list
- Send a re-engagement message based on users’ likelihood to stop using your app or website. — Identifier: Predicted to Churn status
- Display different in-app messages based on your users’ language and country settings. — Identifier: Locale
Identifiers you can use for segmentation
In the Message or A/B Test composers and with the
/api/segments endpoint, you can create a segment using unique identifiers or by an identifier that may belong to or include multiple users, such as a tag, attribute, or event. You can also include a saved segment in another segment. For In-App Automation, all options potentially target multiple users.
Client-side vs server-side data
Airship client-side data mostly comes from apps and websites that use our SDK. This is the source of client-side data used for targeting. Client-side data includes Device PropertiesTags that represent the properties of a device, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device property tags are stored automatically and can be used to target your audience. and AttributesMetadata that you can use to group and target your audience. Attributes differ from tags in that when evaluating users with attributes, Airship uses operators, e.g., equals, less than/greater than, contains, before/after, to determine whether or not to target a user. Supported attribute types are TEXT, NUMBER, and DATE. . See reference: Default Attributes.
You can also group users and add attributes and tags yourself — this is considered server-side data. CRM and POS systems are common sources. For segmentation, you can create:
- AttributesMetadata that you can use to group and target your audience. Attributes differ from tags in that when evaluating users with attributes, Airship uses operators, e.g., equals, less than/greater than, contains, before/after, to determine whether or not to target a user. Supported attribute types are TEXT, NUMBER, and DATE.
- Audience ListsRecipient groups based on either your own data or automatically generated app user lifecycle information. Audience lists help you target specific users.
- Named UsersA customer-provided identifier used for mapping multiple devices and channels to a specific individual.
- TagsMetadata that can be associated with a channel or a named user for targeting. Tags are generally descriptive terms indicating user preferences or other categorizations, e.g.,
weather_alerts_los_angeles. Tags are case-sensitive. and Tag GroupsAn array of tags that you can associate with both channels and named users.
You can then set attributes or tags on channels and named users, or group channels into named users. See:
Channel registration is asynchronous, so it may take up to an hour before you can target newly-created channels.
Creating single-use segments
In the dashboard, select Target Specific Users in the Audience step of the Message, A/B Test, and In-App Automation composers:
In the API, target specific users via the
"audience" object. See:
API: Audience Selection.
Creating reusable segments
You can create reusable segments instead of having to recreate your audience selections.