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 send itself. The SDK method behind it (PushwooshRepository.sendPushOpened()) is deprecated and scheduled for removal, and the SDK ignores a repeat call for a notification whose open it has already reported — so calling it by hand either does nothing or corrupts 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
Collect device logs while you send a test push and then open it.
Confirm delivery: you should see a
/messageDeliveryEventrequest when the notification arrives.Look for the open: when you tap the notification, a
/pushStatrequest should follow immediately./messageDeliveryEventpresent but/pushStatmissing confirms open tracking is broken.
Common causes
-
Custom notification building. If your app builds the notification itself (custom
NotificationFactory, custom layout, or a hand-rolledNotificationCompat.Builder) with its ownPendingIntent, 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 Pushwoosh message toPushwooshFcmHelper.onMessageReceived(context, remoteMessage)(guard it withPushwooshFcmHelper.isPushwooshMessage(remoteMessage)) so the SDK owns the notification and its open intent. -
Suppressed display. A
NotificationServiceExtensionwhoseonMessageReceivedreturnstruemeans the SDK never displays the notification, so there is no tap to track. Either returnfalse, or set thecom.pushwoosh.send_push_stats_if_alert_disabledmeta-data totrueso the open is still reported. - 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
NotificationOpenActivitywas not removed or overridden during a merge or an SDK upgrade, and that you are on a current SDK (Android SDK 6.10.1 at the time of writing).
Comments
0 comments
Please sign in to leave a comment.