Audience data reference

Airship evaluates your audience at the channel level or contact level, depending on when your project’s account was created and whether it has migrated to contact-level segmentation. For explanations of each system, see Segmenting your audience.

Contact-level segmentation

The following audience data is available in the contact-level segmentation system.

Segments

Use this data to configure segmentsA reusable audience group you create by selecting unique or shared user data.:

• ChannelA device or address registered with Airship to receive messages, such as a mobile app, web browser, email address, or SMS number. It stores opt-in status, device-specific information, and metadata used for targeting. Each channel has a unique channel ID. IDs
• Named userA contact identified with an ID you provide, such as a customer ID from your CRM. Associating channels with that ID maps multiple devices and channels to one individual. Each named user has a unique named user ID. IDs
• Device propertiesInformation about a channel, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device properties apply to a channel only, not a named user. Values come from the user’s device when an SDK is present, or are set via the API for channels without one. Each property is automatically made available as an attribute, a tag, or both for audience segmentation.
• AttributesMetadata used for audience segmentation and personalization. Attributes extend the concept of tags by adding comparison operators and values to determine whether or not to target a user, helping you better evaluate your audience., including NPS categoryA category based on the score a user submits in an NPS survey in a Scene. Ratings 9 and 10 have category Promoter, 7 and 8 are Passive, and 6 or lower are Detractor. They are available in survey reporting and are also a text attribute assigned to a user. and NPS scoreThe score (0-10) a user submits in an NPS survey in a Scene. It is available in survey reporting and is also a number attribute assigned to a user.
• TagsMetadata that you can associate with a channel or named user for audience segmentation. Generally, a tag is a descriptive term indicating a user preference or other categorization, such as wine_enthusiast or weather_alerts_los_angeles., including Predicted to Churn statusAnalyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk.
• Tag groupsAn array of tags that you can associate with both channels and named users.
• EventsA record of an action in your app, on your website, in the Airship system, or in an external system. Examples are a message send, an app open, or a purchase transaction.
• Audience lists:
  • Lifecycle listsAn audience list Airship automatically populates based on user activity in your app, such as app opens, uninstalls, notifications received, and dormancy.
  • Uploaded listsAn audience list you populate by uploading a CSV of channel or named user IDs. In the API, uploaded lists are called static lists.
  • Subscription listsAn audience list users opt in to for a specific messaging topic. Users can manage their opt-in status using a Preference Center. — The lists must contain channel IDs or named user IDs as the identifier, not a mix of the two.

Segments can also contain other segments.

Audience targeting

The same UI and data for segments are available in these places:

Feature flag audience targeting

This data is available for Target Specific Users in feature flagAn experimentation tool for controlling the availability of content or functionality in your app or website. A flag’s Configurations determine the audience, schedule, and property values to apply when the flag is enabled. Flag properties enable making immediate code updates, bypassing the need for traditional code changes and release processes. configurations:

• Device data:
  • App version
  • LocaleThe combination of a language and country. A user’s locale is determined by their device settings.
  • Platforms
  • Primary device tagsA tag set without specifying a custom tag group. Belongs to the device tag group and applies to a channel only, not a named user. — This is labeled “Device tags” in the dashboard.
• Opt-in status:
  • Location
  • Push
  • Subscription listsAn audience list users opt in to for a specific messaging topic. Users can manage their opt-in status using a Preference Center. — The lists must contain channel IDs or named user IDs as the identifier, not a mix of the two.
• New users
• Feature flag access
• SegmentsA reusable audience group you create by selecting unique or shared user data. — See segment data.

Channel conditions

Use this data to configure Channel conditions in the Message composer, Sequence messages, and each variant in A/B tests and Intelligent Rollouts:

• ChannelA device or address registered with Airship to receive messages, such as a mobile app, web browser, email address, or SMS number. It stores opt-in status, device-specific information, and metadata used for targeting. Each channel has a unique channel ID. IDs
• Device propertiesInformation about a channel, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device properties apply to a channel only, not a named user. Values come from the user’s device when an SDK is present, or are set via the API for channels without one. Each property is automatically made available as an attribute, a tag, or both for audience segmentation.
• TagsMetadata that you can associate with a channel or named user for audience segmentation. Generally, a tag is a descriptive term indicating a user preference or other categorization, such as wine_enthusiast or weather_alerts_los_angeles., including Predicted to Churn statusAnalyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk.
• AutogroupA default tag group. When devices are registered in Airship, they are automatically assigned a tag within the autogroup tag group. The tag is a numeric value of 1 to 100. Some uses for autogroup tags are creating a control group, and to randomly segment your audience. Autogroup must be enabled for your account.
• EventsA record of an action in your app, on your website, in the Airship system, or in an external system. Examples are a message send, an app open, or a purchase transaction.
• Audience lists:
  • Lifecycle listsAn audience list Airship automatically populates based on user activity in your app, such as app opens, uninstalls, notifications received, and dormancy.
  • Uploaded listsAn audience list you populate by uploading a CSV of channel or named user IDs. In the API, uploaded lists are called static lists.
  • Subscription listsAn audience list users opt in to for a specific messaging topic. Users can manage their opt-in status using a Preference Center. — The lists must contain channel IDs or named user IDs as the identifier, not a mix of the two.

Use this data to configure Channel conditions in In-App Automations and Scenes:

• Device data:
  • App version
  • LocaleThe combination of a language and country. A user’s locale is determined by their device settings.
  • Platforms
  • Primary device tagsA tag set without specifying a custom tag group. Belongs to the device tag group and applies to a channel only, not a named user. — This is labeled “Device tags” in the dashboard.
• Opt-in status:
  • Location
  • Push
• New users

Channel-level segmentation

The following audience data is available in the channel-level segmentation system.

Segments

You can create segmentsA reusable audience group you create by selecting unique or shared user data. using this data:

• ChannelA device or address registered with Airship to receive messages, such as a mobile app, web browser, email address, or SMS number. It stores opt-in status, device-specific information, and metadata used for targeting. Each channel has a unique channel ID. ID
• Named userA contact identified with an ID you provide, such as a customer ID from your CRM. Associating channels with that ID maps multiple devices and channels to one individual. Each named user has a unique named user ID. ID
• Device propertiesInformation about a channel, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device properties apply to a channel only, not a named user. Values come from the user’s device when an SDK is present, or are set via the API for channels without one. Each property is automatically made available as an attribute, a tag, or both for audience segmentation.
• AttributesMetadata used for audience segmentation and personalization. Attributes extend the concept of tags by adding comparison operators and values to determine whether or not to target a user, helping you better evaluate your audience., including NPS categoryA category based on the score a user submits in an NPS survey in a Scene. Ratings 9 and 10 have category Promoter, 7 and 8 are Passive, and 6 or lower are Detractor. They are available in survey reporting and are also a text attribute assigned to a user. and NPS scoreThe score (0-10) a user submits in an NPS survey in a Scene. It is available in survey reporting and is also a number attribute assigned to a user.
• TagsMetadata that you can associate with a channel or named user for audience segmentation. Generally, a tag is a descriptive term indicating a user preference or other categorization, such as wine_enthusiast or weather_alerts_los_angeles., including Predicted to Churn statusAnalyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk. and Channel CoordinationA group of strategies for targeting users where they are most likely to receive your message. tags
• Tag groupsAn array of tags that you can associate with both channels and named users., including autogroupA default tag group. When devices are registered in Airship, they are automatically assigned a tag within the autogroup tag group. The tag is a numeric value of 1 to 100. Some uses for autogroup tags are creating a control group, and to randomly segment your audience. Autogroup must be enabled for your account.
• EventsA record of an action in your app, on your website, in the Airship system, or in an external system. Examples are a message send, an app open, or a purchase transaction.
• Audience lists:
  • Lifecycle listsAn audience list Airship automatically populates based on user activity in your app, such as app opens, uninstalls, notifications received, and dormancy.
  • Subscription listsAn audience list users opt in to for a specific messaging topic. Users can manage their opt-in status using a Preference Center.
  • Uploaded listsAn audience list you populate by uploading a CSV of channel or named user IDs. In the API, uploaded lists are called static lists.

Segments can also contain other segments.

Audience targeting

The same UI and data for segments are available in these places:

In-App Automation, Scene, and feature flag audience targeting

This data is available for Target Specific Users in In-App Automations, Scenes, and feature flagAn experimentation tool for controlling the availability of content or functionality in your app or website. A flag’s Configurations determine the audience, schedule, and property values to apply when the flag is enabled. Flag properties enable making immediate code updates, bypassing the need for traditional code changes and release processes. configurations:

• Device data:
  • App version
  • LocaleThe combination of a language and country. A user’s locale is determined by their device settings.
  • Platforms
  • Primary device tagsA tag set without specifying a custom tag group. Belongs to the device tag group and applies to a channel only, not a named user. — This is labeled “Device tags” in the dashboard.
• Opt-in status:
  • Location
  • Push
• New users
• Feature flag access — Available for feature flag configurations only.
• SegmentsA reusable audience group you create by selecting unique or shared user data. — See segment data.