Device properties

Use automatically collected device properties as tags and attributes for audience segmentation.

View as Markdown
A device property is information about a channel, such as language and time zone settings, OS and browser versions, and notification opt-in status. 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.

Sources and updates

Device properties are available in every project automatically, with no setup required. For app and web channels, the Airship SDK reports values from a user’s device. For email, SMS, and Open Channels, values come from the Airship API.

For web browsers, language and country data come from the browser by default. If the browser doesn’t have country information set, use the Web SDK’s locale override methods to set values manually.

Properties reported by the SDK update daily. To update properties for email, SMS, and Open Channels, register or update the channel using these APIs:

Device properties by channel

Email Domain is available for email channels only, as both an attribute and a tag. Other device properties are organized below by channel availability:

Mobile apps onlyApps and web browsersWeb browsers onlySMS only
- Application Version
- Background Enabled1
- Device Model2
- Device OS Version
- Location Enabled
- Notification Opt-in1
- Language
- Language Country
- SDK Version
- Time Zone
- Browser Name
- Browser Type
- Browser Version
- NDC
- RCS Enabled
- Subdivision

1. Available as a tag only
2. iOS only

For details about each device property, see Default attributes in the Attributes Reference and Device property tags.

Using device properties

You can use device properties directly in segmentation conditions and Performance AnalyticsA customizable marketing intelligence tool that provides access to reports and graphs based on engagement data. reports. Airship also uses some of them automatically. For example, ua_locale_language drives message localization, and timezone drives delivery in the user’s local time.

See also the attributes and tags documentation.