|The more complex your API request is, the longer it will take for Urban Airship to resolve the request to actual device records and deliver the notifications to last-mile push providers (APNS, GCM, etc).|
Broadcast (all devices) and Unicast (single device) push requests will always be the lowest latency types of notification sends. This is because there is very little computation required to turn a single request in to successful notification send.
In normal conditions, we can fulfill a broadcast to millions of devices in under 5 seconds. However this behavior is not always applicable given more sophisticated customer use-cases.
- Using tags and aliases that are not registered to any devices.
- Including multiple NOTs in a single request.
- Including many (more than 10-15) tags or aliases in a single request.
See Example API Requests for tags.
|When combining location and tags in the same segment, being mindful of the complexity of your segment is the best bet for a low latency send.|
When using a segment created via the web Segment Composer or the Segment Creation API endpoint, the complexity included in the segment may be hidden. However, all of the above information is true of segments made via these methods as well as pushes requested directly with the audience selections explicitly included in the Push API JSON payload.
As always, if you have questions about your use case or need assistance in crafting a request that is optimized for low latency, please contact Urban Airship Technical Support or post in the Community Forums.