Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GoogleFirebaseFcmDataV1beta1MessageOutcomePercents

import type { GoogleFirebaseFcmDataV1beta1MessageOutcomePercents } from "https://googleapis.deno.dev/v1/fcmdata:v1beta1.ts";

Percentage breakdown of message delivery outcomes. These categories are mutually exclusive. All percentages are calculated with countMessagesAccepted as the denominator. These categories may not account for all message outcomes.

interface GoogleFirebaseFcmDataV1beta1MessageOutcomePercents {
delivered?: number;
droppedAppForceStopped?: number;
droppedDeviceInactive?: number;
droppedTooManyPendingMessages?: number;
pending?: number;
}

§Properties

§
delivered?: number
[src]

The percentage of all accepted messages that were successfully delivered to the device.

§
droppedAppForceStopped?: number
[src]

The percentage of accepted messages that were dropped because the application was force stopped on the device at the time of delivery and retries were unsuccessful.

§
droppedDeviceInactive?: number
[src]

The percentage of accepted messages that were dropped because the target device is inactive. FCM will drop messages if the target device is deemed inactive by our servers. If a device does reconnect, we call OnDeletedMessages() in our SDK instead of delivering the messages.

§
droppedTooManyPendingMessages?: number
[src]

The percentage of accepted messages that were dropped due to too many undelivered non-collapsible messages. Specifically, each app instance can only have 100 pending messages stored on our servers for a device which is disconnected. When that device reconnects, those messages are delivered. When there are more than the maximum pending messages, we call OnDeletedMessages() in our SDK instead of delivering the messages.

§
pending?: number
[src]

The percentage of messages accepted on this day that were not dropped and not delivered, due to the device being disconnected (as of the end of the America/Los_Angeles day when the message was sent to FCM). A portion of these messages will be delivered the next day when the device connects but others may be destined to devices that ultimately never reconnect.