1. Airship Support
  2. Community
  3. Engagement Platform - API

Does UA support Push message delivery report

Avatar
Nitin Kushalappa

Push messages are generally for push and forget  way of sending message, but in our app we need to get delivery status for those messages ,like failed or success so the we can try to resend the failed msgs, or does UA provide any way of achieving it .

Didn't find what you were looking for?

New post

Comments

3 comments

Sort by Date Votes
  • Avatar
    Aaron S.

    Hi Nitin,

    Thank you for writing in. We cannot provide direct delivery reports. This is because we do not get feedback from the platform service providers when a notification is delivered to a device. In most cases if there are direct reasons that a notification cannot be delivered (i.e. the app is uninstalled, we would get feedback.

    More information can be found in this support article:

    Tracking a push request to a device

    If there is anything else I can do, or if this didn't address your concerns please do not hesitate to write back.

    My Best,
    Aaron Schuman
    Technical Support Engineer, Portland

     

    Comment actions Permalink
    0
  • Avatar
    Nitin Kushalappa

    But is there an alternative method to achieve that which UA can provide, excluding real time comminication protocols

    Comment actions Permalink
    0
  • Avatar
    Joshua

    Hi Nitin,

    Reading your message, it appears that you're looking for this kind of functionality because you wish to retry sending your message to the individual device in the event of a failure. Urban Airship already has redundancy methods built-in to our core delivery networks in order to assure that all messages are handed off to each respective platform push service. Messages sent that do not result in the delivery to a particular device is typically due to one (or more) of the following reasons:

    1. The app is incorrectly configured or does not have the SDK correctly implemented (See Troubleshooting Push Delivery)
    2. Your segments are not being set properly (i.e. Tags or Named Users) or in the manner expected from your use case
    3. The user has opted-out from receiving push notifications (if the message is a notification alert)
    4. The user has uninstalled your app from the device

    So long as you have tested your app, segments, implementation, and use cases using a development app build, and your server is configured to retry sending your API requests upon receiving a 5XX error (see our Best Practices Guide for handling 5XX errors), or alternatively use our Message Composer, you will generally have nothing to worry about, and your push notifications will distribute properly.

    Please let me know if you have any more questions.

    Best Regards,

    -Joshua

    Urban Airship Technical Support

     

    Comment actions Permalink
    0

Please sign in to leave a comment.