Understanding Notification Delivery

Web push notifications are delivered to a subscriber’s browser. To deliver notifications Chrome, Firefox, Opera and Edge use Voluntary Application Server Identification for Web Push (VAPID) protocol, while Safari uses Apple Push Notification Service.

Notifications that are pushed via iZooto can be viewed under Campaign Reports.

Audience Reach

This shows the audience count at that particular time when the campaign was pushed.

For recurring campaigns, this would be a cumulative count of all the runs so far.


When a user sends a notification, iZooto server pushes it to the endpoints in case of Chrome, Firefox, Opera and Edge and APN servers in case of Safari. The browser server then accepts to push notifications to the active subscribers. This defines the "Sent" count for iZooto.

Let's take an example, let’s assume that a notification was pushed to an audience of 100 and the browser server replies back saying that the actual count (at that precise time) is 98, the ‘Sent’ column in the notification report would show 98.

Sent notifications don't indicate the count of viewed the notifications.

For recurring campaigns, this would be a cumulative count of all the runs so far.


CTR (Click Through Rate) is the number of clicks received on a notification divided by the notifications delivered. This is usually the metrics marketers use to analyze the effectiveness of any campaign. CTRs also depend on various factors - Content, timing, audience, and frequency of notifications sent. The clicks and CTR keep getting updated on the report.

Notifications are delivered to the subscriber even when he/she is not on the website. Here is where they get delivered/stacked:

  • Windows - right above the taskbar
  • Mac - Mac OS notification center
  • Linux - top right section of the browser
  • Android - notification tray

Updated 3 months ago

Understanding Notification Delivery

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.