The encoded Responsys account ID, a unique identifier which helps enable Responsys customers to interact with only their mobile applications.
A device that has successfully installed an application packaged with the Push IO Manager. A device will only be classified as "active" if it has opted in to push notifications. iOS requires a user to explicitly opt-in, while opt-in is implied upon app installation on Android.
An engagement metric that is measured when a user receives a notification while your app is running in the foreground, or if the user tapped your notification while your app was suspended in the background.
The API Key is a platform-specific value that is generated automatically when you create a platform using the Mobile App Developer Console. API Keys are important for sending unique messages to different mobile app platforms when using Responsys to send push notifications and in-app messages to the mobile app. Also known as the App Token.
Each individual application has a unique ID used by the application to communicate with the Oracle Responsys Mobile App Platform Cloud Service.
An audience defines a group of customers that will receive push notifications or in-app messages. Marketers define audiences for the mobile channel using Responsys.
An alphanumeric value generated by the Operating System that is unique to each app installed on a device. It is used to identify the recipient device when sending a push notification by way of the OS provider gateway.
An engagement metric that is measured when a user taps on your notification, therefore opening your app, when your application is not suspended in the background or open in the foreground.
Notification Preferences allow you to collect app user preferences which are used within Responsys to filter your App Channel List. Notification Preferences are stored as key/value pairs and are usually tied to a user interface control such as an on/off switch.
These are tertiary engagement metrics that can be configured with the Push IO Manager to track a variety of different things:
A configuration file that includes important authentication values for targeting your specific application with push.
You download this configuration file from the Mobile App Developer Console and include it in your project.
You must download the configuration file for each platform that you set up in the system. The file is packaged with your application's assets and contains platform-specific information for properly pushing to your app(s).
Push IO Configuration files can be named one of the following:
The push payload contains all the information related to the push notifications you are sending on a general and per-platform basis. It follows the general rule of inheritance in programming, whereby the parent payload data can be overruled by the payload data of the child.
The UUID stands for Universally Unique Identifier, and is created by our SDK (Push IO Manager) when the user opts in for push notifications (or, automatically on Android which has no base opt-in functionality). UUIDs are unique to each device and deleted and reconfigured on application deletion and re-installation. UUIDs can be used to send 1:1 messages to your users - often by tying a UUID to a device on your backend server and pushing to users through a backend configuration.