Tracking a push request to a device

After a push request is made to Urban Airship and processed through our systems, we hand the notification to the push platform providers (APNS, FCM, ADM, or HMS) who then delivers it to devices.

For basic push notifications, while we cannot track the push all the way to the end users' individual devices, we can track if we successfully handed a notification to a push provider for delivery to devices. For rich notifications and landing pages, we can provide receipt verification with our mobile engagement data streaming service, Airship Real-Time Data Stream.

Notification Delivery Path:

  1. A request to send a push notification is made to Airship from the API or Dashboard.
  2. If sent via the Push API, the request is checked for valid JSON and required authentication keys. A 202 response is returned if the request is properly formatted and no syntax errors are detected.
  3. Airship processes the push request and determines which active devices that the notification should be sent to.
  4. Airship passes requests to the appropriate service provider (FCM, APNS, etc) as individual push messages addressed to each device.
  5. The service provider performs the delivery of the push notification to actual devices.
  6. This notification passes over the Internet to arrive on the device usually over WIFI or a cellular data network.
  7. The client app on the device handles the message as appropriate for the platform, context, and message type.

Once we have handed off the message, we have no visibility into the path of the push through third-party networks and services. If you believe that there are discrepancies with push sends, please contact Airship support or post in the Community Forums.

Related Content:

Was this article helpful?
0 out of 0 found this helpful
Submit a request