Noun concept
Last updated：2022-03-14
Noun concept
Basic terminology
| noun | description |
|---|---|
| AppKey | The unique identification ID of the application created by the developer within the Jiguang platform. |
| Master Secret | Used in conjunction with AppKey to achieve authentication when developers call the Jiguang service API. Please keep the Master Secret to prevent leakage. |
| Three-party manufacturer channels | Push channels built by mobile phone device manufacturers in the Android ecosystem, such as Huawei, Xiaomi, and FCM, and channels such as APNs and VoIP officially built by Apple in the iOS ecosystem. |
| Push platform (platform) | Android, iOS, Windows, web, etc. are platforms based on operating systems or business hosting platforms, with independent ecology and user isolation. |
| Push target (audience) | The target object to which a notification message can be pushed. JPush provides a variety of methods, such as: alias, label, RID, grouping, broadcast, etc. |
JiGuang RID (registration_id) |
The registration ID of the user's terminal device on the JiGuang service platform is the user's unique device identification ID. The aliases and tags of the push target are based on RID. |
| Device tag (tag) | Developers can set tags for JiGuang RIDs and use tags to quickly select and push RIDs in batches. Each JiGuang RID can be bound to 1,000 tags, and there is no upper limit to the devices that can be associated with each tag. |
| Device Alias (Alias) | Developers can set an alias for JiGuang RID and complete the push through the alias. Each JiGuang RID can only be bound to 1 alias, and up to 10 JiGuang RIDs can be bound under each alias. |
| User segmentation | Divide users into different groups based on geographical location, activity, smart tags, device attributes, etc. to achieve flexible, accurate and efficient push. |
| Broadcast (all) | All registered users of the Jiguang service for applications created by developers will be pushed to all users through broadcast. |
Message type
| noun | description |
|---|---|
| Notification bar messages | Notification bar messages are usually messages displayed in the notification bar area of mobile terminal devices. Notification bar messages are the most commonly used message type. Reminders such as sound, vibration, and light can be set. Notifications are mainly used to remind users, and are used in various scenarios such as news content, promotions, product information, version update reminders, order status reminders, etc. For details, please refer to the document [Notification Bar Message](/en/jpush/server/push/rest_api_v3_push#notification: Notification). |
| Custom messages | Custom messages are usually not displayed in the notification bar area of mobile terminal devices, and are usually invisible to end users. The content of the custom message is completely defined by the developer and is mainly used to process the internal business logic of the application. For details, please refer to the document [Custom Message](/en/jpush/server/push/rest_api_v3_push#message: Custom Message). |
| In-app messages | In-app messages (rich media messages) are messages with rich forms such as full-screen pages, pop-up windows, floating windows, graphics, videos, H5, etc. that appear when an APP application is opened. They are usually combined with notification bar messages. The user clicks on the notification bar message, opens the APP application, and displays the in-app messages. |
| Geofence messages | Geofence messages are geofences created independently by developers. When users of the APP enter/leave the geofence, push notification messages can be triggered to implement online and offline marketing operations. |
| Notification bar + custom message | Android platform developers can combine notification bar messages and custom messages into one push message to implement business logic in special business scenarios. |
Custom messages are converted to notification bar messages |
Android platform developers can prioritize pushing custom messages to better meet business logic needs. When the device is offline and custom messages cannot be delivered in time, the custom messages are converted into notification bar messages and are immediately delivered through the manufacturer channel. |
| In-app reminder message | When the device notification permission is turned off, the notification bar message is converted into an in-app reminder message. When the device runs the APP in the foreground, the content of the notification bar message will be displayed as an in-app message. |
| noun | description |
| --- | --- |
Planned target |
Developers push the number of devices through the initial target set by various rules and conditions. |
| Valid targets | The initial target device population selected for the push task will be filtered by the device validity filtering mechanism of the JiGuang push service and the final number of effective target devices. |
| Sending quantity | Among the valid target devices, the number of devices that the JiGuang push service actually successfully created the sending task (JiGuang channel and third-party manufacturer channel). |
| Delivery quantity | Delivered through JiGuang channel and third-party manufacturer channel, the number of user equipment terminals that actually receive the notification message and successfully return the delivery receipt. The number of delivery after 5 days is not included in the calculation. |
| Impression quantity | After the notification message is successfully delivered to the device terminal, it is successfully exposed and displayed on the notification bar of the device terminal, and the display receipt is successfully returned. The number of impressions after 5 days will not be counted. |
| Number of clicks | After the notification message is successfully displayed on the terminal device, the number of clicks on the notification message and the successful return of click receipts. The number of clicks after 5 days will not be counted. |
| Delivery rate | Delivery rate = delivery quantity / sent quantity. The notification message delivery rates in the APP dimension and msgid dimension are calculated backward for 5 days, and data after 5 days will not be counted. |
| Click-through rate | Click-through rate = number of clicks / number of deliveries. The click-through rates of notification messages in the APP dimension and msgid dimension are calculated backward for 5 days, and data after 5 days will not be included in the statistics. |
Message loss stage
| noun | description |
|---|---|
Plan Target - Valid Target |
|
| Valid target - sent quantity | Based on the device ID granularity, Jiguang Service successfully initiated a service request. However, due to various exceptions such as push exceeding the limit and manufacturer parameter errors, the message push task was not successfully created. |
| Sent quantity - Delivered quantity | Based on the device ID granularity, the message push task has been successfully created. However, due to various exceptions such as the user being offline and exceeding the message offline period, the message was not successfully delivered to the device terminal. |
| Number of deliveries - Number of clicks | Based on the device ID granularity, the message has been successfully delivered to the device terminal. However, due to various exceptions such as display failure and callback failure, the message has not been successfully opened or the jump target address has been damaged. |
| Sending failure | Based on msgid granularity, due to various exceptions such as parameter errors, insufficient permissions, and black word review, the entire message fails to be sent. The red color is displayed in the message record and the reason for the message failure is prompted. Messages that failed to be sent cannot be entered into the message details. |
Was this document helpful?
