Report push analytics

Nexconn provides push statistics so you can view push service data on the Push Success Rate Statistics page in the console.

tip

Push statistics are only collected for production environments of live applications. If your app belongs to an overseas data center, make sure data is reported to the correct data center.

Push statistics include:

• Total Push Volume: The total number of notifications that need to be pushed through configured third-party push providers.
• Total Push Successes: The number of notifications successfully delivered to third-party push providers. A successful delivery does not guarantee that the notification reached the target device.
• Total Push Failures: The number of notifications that failed to be delivered to third-party push providers.
• Total Push Arrivals (requires configuration): The number of notifications actually received by devices. Some devices require the client to actively report arrival data. Currently supports reporting arrival data for one-to-one and group channel push notifications only; Community Channel push arrival data is not supported.
• Total Push Clicks (requires configuration): The total number of notification clicks by end users. Some devices require the client to actively report click data.

Due to differences in vendor push service design across device manufacturers, push arrival and click data cannot be obtained directly from some providers. You need to configure this in the third-party push platform or report it from the client side.

Check SDK initialization timing

If the SDK has not finished initializing when a user clicks a push notification, the SDK cannot report push data.

When integrating, review the components initialized in your Application class and initialize the SDK as early as possible to ensure accurate push-related data reporting.

Collect push arrival data

Push arrival refers to a push notification being successfully delivered to the target device after being sent to the third-party vendor's push channel or push service.

Huawei push arrival data depends on the "delivery receipt" service provided by the vendor's push channel. Google FCM only supports collecting push arrival data for Data Message push method. See the table below for detailed support status:

Push Platform	Push Arrival Data	Configuration Required
Huawei	Supported by vendor	Yes — see Configure Huawei Push Receipt
Google FCM	Not supported by vendor — provided by SDK	See Collect FCM Push Arrival Data

Configure Huawei push receipt

tip

Before proceeding, make sure you have completed the Huawei push integration.

After completing the Huawei push channel configuration, you need to enable and configure message receipts on the Huawei Developer Platform to obtain Huawei push delivery data. For details, refer to the Huawei Developer Platform documentation on Message Receipts. The configuration steps are as follows:

1. Log in to the Huawei Developer Platform, select your app under Push Development Services, and go to the push configuration page.

   

2. On the configuration page, enable App Receipt Status.

   

3. Click New Receipt and configure the following parameters.

   

   • Receipt Name: Enter a custom name.
   • Callback URL: Configure the push receipt callback URL corresponding to your app's data center.
     • Singapore data center: https://callback.sg-light-edge.com/push/callback/huawei
     • North America data center: https://callback.us-light-edge.com/push/callback/huawei
     • Saudi Arabia data center: https://callback.sau-light-edge.com/push/callback/huawei
   • Callback Username: Leave blank.
   • Callback Secret: Leave blank.
   • Supported Version: Both V1 and V2 are supported. V2 is recommended. If you have already configured V1 on the Huawei platform, migrate to V2 as soon as possible.

4. After completing the configuration, click Test Receipt. Once it succeeds, click Submit to save the configuration.

Collect FCM push arrival data

tip

• Before proceeding, make sure you have completed the FCM push integration.
• Confirm that the FCM push method is set to Data Message. Collecting push arrival data in Notification Message mode is not supported.
• Confirm that you have configured the appropriate statistics service.

FCM push arrival data collection is only supported when the FCM push method in the console is set to Data Message. After setting the AreaCode region code during SDK initialization (the SDK uses the region code to resolve the correct statistics service endpoint), the SDK automatically reports push arrival data.

The SDK defaults to the Singapore data center. If your App Key uses Singapore, no additional configuration is needed. For other data centers, pass the corresponding AreaCode during SDK initialization.

For example, configure the region code for an app using the Singapore data center:

kotlin

val params = InitParams(context, "Singapore_dev_AppKey").apply {
    areaCode = AreaCode.SG
    enablePush = true
}
NCEngine.initialize(params)

Java

InitParams params = new InitParams(context, "Singapore_dev_AppKey");
params.setAreaCode(AreaCode.SG);
params.setEnablePush(true);
NCEngine.initialize(params);

AreaCode enum values:

Enum Value	Data Center
AreaCode.BJ	Beijing, China
AreaCode.SG	Singapore (default)
AreaCode.NA	North America
AreaCode.SA	Saudi Arabia
AreaCode.OM	Oman

Collect push click data

Push click data represents the total number of notification clicks by end users.

Click data can be obtained directly from most vendor push channels.

See the table below for detailed support status:

Push Platform	Push Click Event Reporting	Description
Huawei	Supported	Reporting logic is implemented by the SDK by default
Google FCM	Supported	Reporting logic is implemented by the SDK by default

Collect Huawei push click data

tip

Before proceeding, make sure you have completed the Huawei push integration.

The SDK reports Huawei push click data internally by default. No additional action is required.