Last known geographical classification of the device, such as State, Province, and Region. You can use this attribute to geo-target your campaigns.

Important: Make sure to get explicit consent from your users to log this attribute.

Last known sub-geographical classification of the device, such as County, or District. You can use this attribute to geo-target your campaigns.

Important: Make sure to get explicit consent from your users to log this attribute.

Unique, platform-specific advertiser ID for the device. Depending on the platform, it is either the IDFA or the Google AD ID.

Note: Can be used as a match key for an App Channel List PET import in Responsys. We do not recommend using this as a match key to import into the App Channel List PET when an account has more than one app using the same App Channel List. Because ADVERTISER_ID_ is unique for a device, there will be a conflict when a device has installed more than one app from the same account. Also, device users can reset the Advertiser ID and generate a new one at any time, so there is no guarantee that this value will remain unchanged.

App Id / Mobile App Identifier of the app installed on the device.

The app GUID, platform type, and platform identifier. (Platform-specific API key)

Last known app version on the device.

The mobile carrier on the device.

Contains a value noting the reason that Channel Deliverability Status was set to "U" (Undeliverable). Values can be as follows:

• CAMPAIGN_LAUNCH_FEEDBACK: Uninstall signal received after a campaign launch
• APP_UNREGISTERED: Unregister call received from the mobile app through the SDK
• APP_UNINSTALL_CHECK_FEEDBACK: Uninstall signal received for the device during regular app uninstall check

NOTE: This column was added in 20D and will initially be NULL (empty). It will start getting populated in 21A onwards.

Indicates whether messages can be sent to this device or not. It is set to “D” (Deliverable) when the system creates an App Channel List record (that is, a new user installs an app on a specific mobile device for the first time). It is set to “U” (Undeliverable) when the device can no longer be reached, such as when the user has uninstalled the mobile app. Learn more about permission-related fields for push in the App Channel List.

Indicates whether the user has opted in to receive push notification from this device.

Always set to “I” (Opted-In) for Android device records. For iOS device records, this could be set to either “I” (Opted-In) or “O” (Opted-Out), to reflect the User Preferences on the iOS device. Learn more about permission-related fields for push in the App Channel List.

Date and Time when the record is created in Responsys.

Last known city of the device. You can use this attribute to geo-target your campaigns.

Important: Make sure to get explicit consent from your users to log this attribute.

Last known country code of the device. You can use this attribute to geo-target your campaigns.

Important: Make sure to get explicit consent from your users to log this attribute.

Device ID, GUID/UUID style, as generated by the OS of the device during first run of the app. This means that different apps on the same device will have different device IDs. This ID changes when a mobile app is uninstalled and re-installed. Used internally by Responsys.

Note: Device ID + API Key combination can be used as a match key for an App Channel List PET import in Responsys

Model identifier of the device.

Last known postal or zip code of the device. You can use this attribute to geo-target your campaigns.

Important: Make sure to get explicit consent from your users to log this attribute.

Allows data captured by other SDKs, such as external analytics data about a device.

Note: Can be used as a match key for an App channel list PET import in Responsys. This ID represents the unique Device ID of an external system. Using the Oracle Responsys Mobile App Platform Cloud Service SDK, a Mobile App Developer can log this during the first device registration and subsequent device registration updates.

This is the date when the mobile app is first run on the device, which is when Responsys detects that the mobile app was installed.

The locale of the device. Usually expressed as a combination of the two-character ISO language code and the two-character ISO country code. Example: en_US.

The mobile country code of the device. Populated when available.

Date and Time when the record was last updated in Responsys.

Operating system version of the device.

The platform type of a device. Values are:

• APNS - Apple iOS platform
• SAPNS - Apple iOS Development platform
• GCM - Google Android platform
• WNS - Windows platform (not supported for the Responsys v2 Push platform)

Note: This field is only applicable to iOS devices.

This column indicates whether the iOS user has opted in to App Icon Badging on this iOS device. This could be set to either I (Opted-In) or O (Opted-Out), to reflect the user preferences on the iOS device. Learn more about permission-related fields for push in the App Channel List.

Note: This field is only applicable to iOS devices.

When an iOS app implements iOS Provisional Authorization, this column indicates whether the iOS user is still in the Provisional Authorization state (P) or not. When an iOS app is installed with Provisional Authorization, the application is automatically opted-in to Push Notifications and is provisionally authorized to "Deliver Quietly" (that is to only share non-interruptive notifications with the user), and Push Notifications do not interrupt the user by appearing on the device's lock screen or as banners. For such iOS apps, this column is set to P (Provisionally Authorized) when the user is still Provisionally Authorized and has not updated Push Notification permissions on the device after app installation. The purpose of this column is to let marketers take decisions based on whether or not a certain user is Provisionally Authorized. Learn more about this field and Provisional Authorization.

Oracle Responsys ID that corresponds to a unique device record in the App Channel List. This is a reserved field used to track known and unknown mobile app users, and it is the key that is logged for all Mobile App channel activities (Sent, Opens, Conversions, and the like).

Note: You can use RIID_ as a match key for an App Channel List PET import in Responsys.

Screen height of the device, in pixels.

Screen width of the device, in pixels.

Responsys Mobile App SDK version, used by Oracle Responsys for troubleshooting.

The time zone of the device.

This is the date when the mobile app last communicated with the Responsys system; this may be due to a user interaction or other cause (such as background location update).

Logs the date and time when uninstall detection occurs by Responsys.

NOTE: This column was added in 20D and will initially be NULL (empty). It will start getting populated in 21A onwards.