Why did my Android push open statistics suddenly drop to zero or become very low?

A sudden drop in Android push open rates — especially right after an app update — usually means the notification tap no longer goes through Pushwoosh's notification-open flow, so the /pushStat request is never sent.

Important: /pushStat is not something your app should call itself. In the Android SDK the corresponding method is private and documented as internal-only; calling it manually will corrupt your statistics. Open tracking is emitted automatically by the SDK's notification-open handler chain when the tap is routed through NotificationOpenActivity. The fix is to restore that routing, not to add a call.

How to diagnose

1. Collect device logs while you send a test push and then open it.

2. Confirm delivery: you should see a /messageDeliveryEvent request when the notification arrives.

3. Look for the open: when you tap the notification, a /pushStat request should follow immediately. /messageDeliveryEvent present but /pushStat missing confirms open tracking is broken.

Common causes

• Custom notification building. If your app builds the notification itself (custom NotificationFactory, custom layout, or a hand-rolled NotificationCompat.Builder) with its own PendingIntent, the tap goes straight to your Activity and bypasses Pushwoosh entirely. The content intent must point at Pushwoosh's notification-open entry point.
• Own FirebaseMessagingService. If you handle FCM messages yourself, forward every message to PushwooshFcmHelper.onMessageReceived(context, remoteMessage) so the SDK owns the notification and its open intent.
• Deeplink / trampoline changes. A recent change that intercepts the notification intent to handle deeplinks is the single most common regression — check your git history around the version where opens dropped.
• Manifest changes. Verify NotificationOpenActivity was not removed or overridden during a merge or an SDK upgrade, and that you are on a current SDK (Android SDK 6.10.0 at the time of writing).