β³How long does it take for push messages to be received by our customers?
Learn more about push delivery time
Push messages typically are delivered within a few (20-30) seconds. However, Android and iOS handle the messages differently.
Sometimes if the user has the card open or uses the phone, a message may not automatically trigger. Unfortunately, this user experience is controlled by Apple and Google and is beyond our control.
A simple way to check if the message has been received is to check the βLatest Updatesβ section on your Customerβs card. If the phone has already received and processed the message, you will see it there.
Please note that card preview will not receive push updates. These passes are simply there to allow you to test how your design looks on a phone.
The average delivery speed
The delivery speed of push notifications via Apple Push Notification Service (APNS) can vary significantly based on several factors, including the device's network connectivity, the device's current state (e.g., powered on or off), and the configuration of the push notification itself (e.g., priority level). Typically, notifications are received by the end user's device within a few seconds under optimal conditions.
According to a Stack Overflow discussion, push notifications are generally delivered in under a few seconds when the device is online. However, it's important to note that delivery times can vary, and in some cases, it may take up to half an hour for a notification to be delivered. There are also situations where a device may not receive push notifications at all, such as when it is turned off or when it is connected to a WiFi network that blocks the required ports for APNS connectivity. APNS will attempt to deliver the last notification it received for a device when it comes back online, but this is only for a limited time. If the attempt times out, the notification will be lost[2].
Another source mentions that typically, notifications are received by customers less than 5 seconds after an action card requiring a notification is ready. However, this is under the assumption that all conditions for successful delivery are met, including proper device configuration and connectivity[8].
It's crucial to understand that APNS operates on a "best effort" basis, meaning that while it strives to deliver notifications as quickly as possible, there is no absolute guarantee of immediate delivery or delivery at all. Factors such as device connectivity, APNS server load, and the configuration of the notification itself can all impact delivery times.
For critical applications, such as a fire alarm function mentioned in the Stack Overflow discussion, relying solely on push notifications may not be advisable due to their inherent unreliability and the potential for delays. It's recommended to consider alternative or supplementary methods of alerting users to ensure timely notification[2].
Citations: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns [2] https://stackoverflow.com/questions/9204767/how-much-delay-of-ios-push-notification [3] https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/viewing_the_status_of_push_notifications_using_metrics_and_apns [4] https://www.moengage.com/blog/track-ios-push-notification-delivery-rates/ [5] https://firebase.google.com/docs/cloud-messaging/understand-delivery [6] https://help.klaviyo.com/hc/en-us/articles/15594685536539 [7] https://www.infoq.com/news/2023/10/iOS-push-deliery-metrics/ [8] https://documentation.atomic.io/advanced/push-notification-delivery
Last updated