Over the past few days, PushAll has implemented the functionality of tracking the status of a notification and receiving a feed of a channel that you own.

What does this give us? Now, if your website has SMS notifications, you can do this:

1. Send Push
2. After 30-50 seconds we check if the user received a notification, did he respond to it
3. If it does not come, send him a SMS, call, send a mail, etc.

Thus, it is possible to reduce the number of SMS alerts sent at times, saving it a lot of money.

Under the cat a little documentation on the use and several other changes.

Web Based Monitoring

This tracking method has been available for a long time. It allows you to track the status of broadcast-feeds in the tape.

From the innovations can be identified that now shows not only the number of devices, but also the number of users.
')

Getting data through the Showlist API

This is a new feature designed to obtain data about the tape and statistics.
To work, you must send a GET or POST request to
pushall.ru/api.php
With parameters:
"type" => "showlist",
"id" => "ID ",
"key" => " "

This will allow you to get the last 200 entries of your tape. You can pass the limit parameter and set the number of records for output yourself.

To obtain data on a specific notification, we first need to report one news.
Now all types of mailing lists on the output give a JSON response like:
{"Success": 2, "unfilt": 1, "all": 1, "lid": 21074}
"Success" - the number of devices that should receive notification
"Unfilt" - the number of devices on which the shipment was made.
"All" - all possible devices.
“Lid” - LogId is the identification number of the notification; it is through it that it will be possible to receive data on statistics.

success and unfilt are distinguished by the fact that unfilt is a number before dispatch, and success is the quantity to which it was actually sent. It may be different if, when sending, it was revealed that a device was removed and no longer responding.

When receiving the entire tape, the server’s response will be sent as JSON and look something like this:

 { "data": [{ "id": 21074, "title": " PushAll", "text": "", "url": "", "icon": "https:\/\/pushall.ru\/upimg\/sub24.jpg", "hidden": 0, "success": 2, "unfilt": 1, "all": 1, "poststat": { "waiting": 0, "waitingu": 0, "accepted": 2, "acceptedu": 1, "opened": 0, "openedu": 0, "deleted": 0, "deletedu": 0 } }, { "id": 13219, "title": 123, "text": "", "url": "http:\/\/habr.ru", "icon": "https:\/\/pushall.ru\/upimg\/sub24.jpg", "hidden": 0, "success": 2, "unfilt": 1, "all": 1, "poststat": { "waiting": 0, "waitingu": 0, "accepted": 4, "acceptedu": 1, "opened": 2, "openedu": 1, "deleted": 0, "deletedu": 0 } }, { "id": 10734, "title": 1234, "text": "", "url": "", "icon": "https:\/\/pushall.ru\/upimg\/sub24.jpg", "hidden": 0, "success": 4, "unfilt": 1, "all": 1, "poststat": { "waiting": 0, "waitingu": 0, "accepted": 4, "acceptedu": 1, "opened": 1, "openedu": 1, "deleted": 2, "deletedu": 0 } ... ... 

You will be given all the notification data in the data array. At the same time you get access to the additional field “poststat”
This is the very statistics. Description of fields:

• Waiting: devices waiting
• "Waitingu": waiting users
• "Accepted": devices that have accepted the notification
• "Accepted": users who have accepted the notification
• "Opened": devices that opened the notification
• "Openedu": users who opened the notification
• "Deleted": devices that opened the notification
• "Deletedu": users who deleted the notification

You also need to take into account a small fact: these numbers are the minimum, not the exact information. The fact is that the notification can be squeezed through even the most unstable communication channel. In this case, confirmation of delivery or opening may no longer reach the server. Approximately 44 more people have not yet updated the application to the latest version with support for statistics.

To request a single notification, or a notification sent via unicast api, you must pass the lid parameter with the notification ID.
I described the work of unicast and integration with third-party services in a previous article.

Other minor changes

Finally, you can hide-open a particular channel after its creation. Now you can test the work and publish the channel after it is configured.



The design of the main page has been updated, now more beautiful buttons, the text of the main page has been updated and clarifying images have been inserted.


Many minor API bugs fixed.

Ps. Forgot to say about RSS. Now the bot is multithreaded, due to this it reduced the update time by 2 times. That is, with 500 subscribers, the update time is now 30 seconds minimum.