The 'Delivered' metric tracks whether a push notification actually reached the user's device, as confirmed by the device itself sending a confirmation back to Pushwoosh. This is different from 'Sent', which only confirms that the push gateway (APNs/FCM) accepted the notification from Pushwoosh for delivery.
There are several reasons why 'Delivered' might be low or inaccurate:
- Missing SDK Implementation: Accurate delivery tracking requires specific implementation within your app's code using the Pushwoosh SDK.
- iOS: Requires adding a Notification Service Extension to your app. Without it, delivery cannot be tracked accurately on iOS.
- Android: Delivery tracking is generally handled automatically by the SDK, but issues can arise from customizations or SDK errors.
- Device Status: The device might be offline, turned off, or have no internet connection when the push is sent. Gateways will attempt delivery for a certain period (Time-To-Live or TTL), but if the device doesn't come online in time, it won't be delivered.
- OS/Battery Optimizations: Modern operating systems aggressively manage battery life.
- Android: Features like Doze mode or manufacturer-specific battery savers can delay or prevent background app activity, including push delivery confirmation.
- iOS: Features like the Duet Activity Scheduler Daemon (DASD) can delay or block notifications if the battery is low, CPU usage is high, or the user hasn't interacted with the app recently.
- User Settings: The user might have disabled background app refresh or specific notification permissions for your app.
- Network Issues: Firewalls, VPNs, or general network problems can interfere with delivery.
Important: Even if 'Delivered' tracking isn't fully implemented or shows a low number, it doesn't necessarily mean pushes aren't reaching the gateway ('Sent'). Implementing the required SDK components (especially the iOS Notification Service Extension) is crucial for accurate 'Delivered' statistics.
Comments
0 comments
Please sign in to leave a comment.