1. Product introduction
MobPush is a free push service tool launched by Mob. The client SDK supports both iOS and Android platforms. It is easy to integrate, simple and quick, and provides complete visual data and powerful management background.
The main function
1.1 Our advantages
2. Push flow chart
2.1 Andorid Push process
2.2 IOS push process
3. Message type
MobPush offers three push message formats: notifications, custom messages, and local notifications.
3.1 notice
Notification refers to the display of a notification message on the mobile phone notification bar (status bar). Notification notifications are sent to users for application scenarios such as hot content, promotion, version update, order status, and payment status.
3.2 Custom Messages
Custom message, also known as transparent message, is a message protocol defined by MobPush. After receiving the message, MobPush SDK passes it to App for processing. MobPush does not display the message to the notification class.
3.3 Local Notification
Local notification is not dependent on the network and can send a visible notification to the current device based on conditions without the server. Local notification is usually used to send notifications at a specific time, such as an alarm clock. The MobPush SDK reports local notifications for developers to view notification details.
4. Notification properties
MobPush supports both timed and untimed push properties.
4.1 timing
For certain needs that require regular notifications, MobPush can set the delivery time on the developer platform, and can set push notifications that need to be sent one hour later.
4.2 the timing
Non-timing means instant messages. After a push task is set, it enters the sending queue immediately.
5. Push goals
MobPush supports push targets including: entire population, set tag, set alias, Registration ID, and geographic location
5.1 the label
In MobPush, tagging is usually the same for a specific group of users who install the App. Up to 100 tags can be assigned to each user, and tags can be used as one of the target group options for creating a push. For example: man, women, old users.
5.2 the alias
In MobPush, only one alias can be assigned to a device, and MobPush recommends setting it to a unique alias for users within the same App so that unique users can be identified based on the alias. For example, you can set the unique identifier of the App user’s system, such as Id and mobile phone number, as an alias.
5.3 Registration ID
Registration ID is the unique identifier assigned by MobPush to each device after MobPush SDK initializes successfully (Registration ID is different for different apps on the same mobile phone), which can be obtained through the interface provided by IOS SDK and Android SDK. Developers can send a push to a single device by specifying a Registration ID.
5.4 Geographical Location
Geolocation is a feature provided by MobPush that can be sent to devices in a specific region. Currently, it can be sent to a city.
5.5 User Group
Group setting can be carried out for different users according to tag set + geographical location + registration time + online time + system version, so as to achieve a more refined range of target push.
Explanation of common nouns
6.1 AppKey
After registering as a Mob.com developer, go to the console and add the app’s identity, which is automatically assigned by mob. In MobPush is one of the identifiers for SDK, RestAPI, and server communication.
6.2 App Secret
It is the corresponding key assigned by Mob together with Appkey, which is an important part of SDK, RestAPI and server communication verification in MobPush.
6.3 APNs
Apple’s official push notification service, APNs, allows devices to remain constantly connected to Apple’s push notification server. MobPush IOS notifications are sent through APNs.
6.4 APNs Authentication Mode
There are two APNs authentication modes:
One is through a P12 certificate, which is a file with the extension P12 and is proof that the application sends messages to APNs. APNs has different certificates and passwords for different environments. Therefore, p12 certificate files have two sets: developer environment certificate and key, production environment certificate and key.
One is through Token Authentication, which does not distinguish between developer environment and production environment. P8 certificate with APNs Auth Key is also required, and information such as BundleID needs to be set.
6.5 DeviceToken
To use the APNs service, a 64-bit unique identifier obtained by Apple push service is required, and this Token is not constant. Therefore, when using MobPush, initial DeviceToken needs to be obtained at each startup, and SDK will report to MobPush server and Registration ID binding.
6.6 New Users
Number of newly registered bound devices currently applied.
6.7 Creating a Push Quantity
Currently, the number of new pushes created by an app is the sum of those created through the developer platform and those created through the Rest API.
6.8 Target Quantity
The total number of devices involved in the current app creation push.
6.9 Number of push successes
Current application create push Total number of devices that receive push messages.
6.10 Clicks by Users
Total number of clicks on the device after receiving notification messages.
6.11 Number of API Calls
Total number of RestAPI calls requested.
6.12 Offline Message Retention Duration
A push message is sent to a user. If the user is not currently online, it is saved as an offline message and will be sent to the user the next time the user goes online. This value can be used to specify the offline message duration. That is, within this duration, users will continue to receive notifications when they go online. Otherwise, the notification duration expires. The default duration is 1 day, and the maximum duration is 10 days. If the value can be set to 0, offline messages are not reserved and only online users can receive them.