Mobile Push Message queuing, retry and expiry mechanism

Message store, forward and retry mechanisms

Automatic queuing of concurrent messages with message queuing capability
Messages not received will be stored for future delivery until the end user become available
Message validity period variable and customizable (from 1 min to 48h): choose expiry time when you want the system to stop retrying to send your push message to an undeliverable recipient or an expired message

Full integration with Android FCM, HMS and Apple APNS as fallback if app is offline
Content can be retrieved from the server when not inserted in the push notification
Content is stored locally in the mobile app

Receive message delivery confirmation and real time statuses all the way back to your system via callback

Delivery report for each single push message status and related timestamp:
- Sent
- Delivered on the mobile terminal
- Open / Read
- If an error occurs type of delivery error (ex. number not valid)
Push notification delivery receipt report includes timestamp (date/hour) of each message status being notified
Programmatically adjust logic based on delivery success
Receive the report status (proof of delivery) for each message sent
- in real time via callback (HTTP) to your service (you can test the payload here)
- containing the messageId generated during sent, the identifier of the recipient, the new status and, eventually, the recipientRef that can optionally be set while creating the push message, the InReplyToMessageId with contains the message ID of the reply that can be sent from the SDK and the Channel set while sending the message
View and filter each message report status in real time then use that information in your system / CRM to react.
Tracking push delivery statuses has never been so easy as with Catapush!