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 on the Push IO Web Dashboard. The API Key contains the value of your App ID, followed by 4 characters. For instance, if your App ID is aBcDeFgHiJ, an API Key for iOS could be something like this:
API Keys are important for sending unique messages to different platforms when using the Push IO API.
Each individual application has a unique ID used by the application to communicate with the Oracle Push Cloud Service.
An audience defines a group of users based on one or more categories or platforms. For example, you might make an audience out of all of the users who have registered to a category for a team in the Western Conference who are using your app on Android.
An integer displayed on the corner of your application's icon on the home screen of your device. A badge can be configured on both the Web Dashboard and through API. Furthermore, a badge number of "0" will reset the badge to not be visible on the device.
A category is a way to tag the user for a specific topic of interest. For example, if your app is a sports app, a category may be a specific team. Categories are often configured based upon a user interface control such as an on/off switch.
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. The Device Token will occasionally change, so do not expect it to be a static value.
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.
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 Web Dashboard 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.
With this approach, unique messages can be sent to users on iOS versus Android using a single cURL command to our backend.
This is a secret shared between Push IO and the developer using direct device messaging which authorizes them to send to an account.
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.