Push Detection

To help customers quickly identify issues, this platform currently provides online status query and push lifecycle query tools.

Online Status Query

Use Cases

Because the EngageLab channel for EngageLab Push depends on the user being online to receive pushes, if users report that they often do not receive pushes, you can use this tool to check whether the device is online. If the device is offline, it is recommended to restart the app.

Parameter Description

Registration ID: The registration ID of the user's terminal device on the Jiguang service platform. It is the user's unique device identifier. The Registration ID is different for different apps on the same phone. For how to obtain it, see Get RegistrationID.

Instructions

• Enter the app's Registration ID in the input box. Multiple RegIDs are supported and should be separated by ",".

• If the query result shows "false," the device is offline; if it shows "true," the device is online. You can view the last online time on the right.

• If the entered Registration ID is incorrect, the query result will display the specific error reason.

Push Lifecycle

Use Cases

If the issue of not receiving pushes still cannot be resolved through the online status query, you can use the lifecycle tool to query the message lifecycle and handle the issue according to the error code.

Parameter Description

• Registration ID: The registration ID of the user's terminal device on the Jiguang service platform. It is the user's unique device identifier. The Registration ID is different for different apps on the same phone. For how to obtain it, see Get RegistrationID.
• Message ID: The push task ID.

Get Parameters from the Console

On the notification details page to be queried, you can obtain the Message ID. Click "View" in the message body to see the JSON message body for this push.

If the push target is "Registration ID," then the value of "receiverValue" is the Registration ID.

Get Parameters from the Server

After the API call, obtain msg_id (Message ID) from the response parameters:

              
              {
  "sendno": "0",
  "msg_id": "2509042"
}

            

Instructions

After obtaining the Message ID and Registration ID parameters, go to the [Data Search] - [Push Lifecycle] page, enter the parameters, and click "Search" to view the complete lifecycle of the push.

• 1 indicates a response returned by the EngageLab server, and 2 indicates a response returned by the system browser's server.
• If there is no lifecycle process, it means the device is not included in this push target. Please confirm whether the queried Registration ID is included in this push target.