Message Push Service (MPS) provides real-time statistics on the multiple-push and broadcast-push tasks that are created through MPS console or triggered by calling API to help you get the message push status.
View push tasks
Log in to the mPaaS console, select your app, and enter the Message Push Service > Message management > Multiple push records page.
In the search box displayed in the upper right corner, enter a complete push task ID or task name, and specify the time range to search the tasks. The eligible tasks will appear in the task list.
In the task list, the tasks are sorted in descending order by creation time. The task information displayed includes:
Task ID: The unique identifier of the push task, which is automatically generated by the system.
Task name (API): If the push task is delivered through the MPS console, the task name is automatically generated by the system, usually named in the format “console + time”, for example, “Console Wed Mar 24 14:47: 23 CST 202”; if the task is triggered by calling an API, the task name is the name filled in by the caller.
Push type: It indicates that the message was pushed immediately upon creation or was pushed in schedule.
To view the push details, click the Expand button (+) of the target task on the list.
Pushed messages: Refers to the total number of messages pushed by message push backend, which is counted by the backend.
Successfully pushed messages: Refers to the total number of messages successfully pushed by message push backend, which is counted by the backend.
Message arrivals: The number of messages that actually arrive the device. For iOS channel or Android third-party channels (such as Xiaomi and Huawei), the statistics relies on the result returned from the corresponding third-party channel’s backend after the messages are pushed to the third-party channels. For the Android self-built channel, the statistics relies on the tracking report after the messages are pushed the client.
Offline retention period: Indicates the validity period of the message. In the validity period, MPS delivers the message to the target devices or users once the target devices get connected or the users initiate a binding request till the message is pushed successfully. Once the message expires, the MPS will no longer deliver the message.
It is supported to revoke the messages that have been pushed in past 7 days. For more information, see Message revocation.
Silent messages will be immediately withdrawn once you revoke them, and the client-side users have no sense about that. For non-silent messages, stop pushing the ones not arriving user devices, and cancel presenting the ones that have arrived the user devices but not appeared.
The messages with "Failed" push status cannot be revoked.