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

GoogleFirebaseFcmDataV1beta1DeliveryPerformancePercents

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

Overview of delivery performance for messages that were successfully delivered. All percentages are calculated with countMessagesAccepted as the denominator. These categories are not mutually exclusive; a message can be delayed for multiple reasons.

interface GoogleFirebaseFcmDataV1beta1DeliveryPerformancePercents {
delayedDeviceDoze?: number;
delayedDeviceOffline?: number;
delayedMessageThrottled?: number;
delayedUserStopped?: number;
deliveredNoDelay?: number;
}

§Properties

§
delayedDeviceDoze?: number
[src]

The percentage of accepted messages that were delayed because the device was in doze mode. Only normal priority messages should be delayed due to doze mode.

§
delayedDeviceOffline?: number
[src]

The percentage of accepted messages that were delayed because the target device was not connected at the time of sending. These messages were eventually delivered when the device reconnected.

§
delayedMessageThrottled?: number
[src]

The percentage of accepted messages that were delayed due to message throttling, such as collapsible message throttling or maximum message rate throttling.

§
delayedUserStopped?: number
[src]

The percentage of accepted messages that were delayed because the intended device user-profile was stopped on the target device at the time of the send. The messages were eventually delivered when the user-profile was started again.

§
deliveredNoDelay?: number
[src]

The percentage of accepted messages that were delivered to the device without delay from the FCM system.