Skip to content

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.

Display in the dashboardMeaning
アクティブ購読者 (Active subscribers)The number of currently valid (non-revoked) Push subscriptions
通算送信成功 (Total sent successfully)The cumulative number of notifications successfully sent since the app was created
通算送信失敗 (Total sent failures)The cumulative number of notifications that failed to send since the app was created
今月の送信数 (Sends this month)The number of notifications attempted this month (calendar month)

”Sends this month” and the Free plan’s monthly limit

Section titled “”Sends 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 “今月の送信数 (Sends 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.

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 calendar month. For details, see Error Codes and Limits.

The main cause of a rising “通算送信失敗 (Total sent failures)” 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.

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.