Reading the Statistics
The “統計 (Statistics)” section of the app detail screen (/apps/:id) displays four numeric cards. If the statistics could not be retrieved, “統計を取得できませんでした (Failed to retrieve statistics)” is displayed.
What the 4 metrics mean
Section titled “What the 4 metrics mean”| Display in the dashboard | Meaning |
|---|---|
| アクティブ購読者 (Active subscribers) | The number of currently valid (non-revoked) Push subscriptions |
| 今月の配信成功 (Successful deliveries this month) | The number of notifications delivered successfully this month (UTC calendar month) |
| 今月の配信失敗 (Failed deliveries this month) | The number of notifications that failed delivery this month (UTC calendar month) |
| 通算 (Cumulative) | Successful and failed deliveries within the log retention period (Free: 7 days / Pro: 90 days). When failures exist and the breakdown matches the total, it is shown as “成功 N / 失敗 M（失効 E・その他 O）” (N successful / M failed: E expired and O other) |
”Successful deliveries this month” and the Free plan’s monthly limit
Section titled “”Successful deliveries this month” and the Free plan’s monthly limit”The Free plan’s monthly send limit is 30,000 notifications. When the current plan is Free, a usage bar for “今月の配信成功数 (Successful deliveries this month)” is also displayed at the top of the app list screen; when it reaches 80% of the limit it turns a warning color and shows an “Upgrade to Pro” call to action. Failed deliveries do not count toward this limit.
Once the limit is reached, subsequent send requests are rejected with a 429 (MONTHLY_LIMIT_EXCEEDED) and no notification is sent. The limit resets each UTC calendar month. For details, see Error Codes and Limits.
Typical causes of a rising failure count
Section titled “Typical causes of a rising failure count”The main cause of a rising “今月の配信失敗 (Failed deliveries this month)” or cumulative failure count is subscription expiration. When notifications are disabled on the browser side, or when a subscription expires on the Push service side, the Push service returns 410 Gone or 404 Not Found at delivery time, and that subscription is automatically deactivated. Deactivated subscriptions are excluded from subsequent send targets and from the subscriber count, so the “アクティブ購読者 (Active subscribers)” number decreases accordingly. This is a normal lifecycle event and does not necessarily indicate a system outage.
その他 (Other) covers delivery failures other than subscription expiration, such as temporary Push service errors or network errors. The same breakdown is available in notification history. Existing rows created before breakdown tracking was introduced have an unknown breakdown, so the parenthesized breakdown is omitted when it does not match the total failure count.
In addition, if a send payload exceeds the limit (3,072 bytes), or if the monthly send limit has been reached, the send itself is rejected (in these cases the request itself errors rather than incrementing the failure count). For detailed troubleshooting by symptom, see Troubleshooting.