- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- AndroidDeliveryData
- Date
- Data
- MessageOutcomePercents
- DeliveryPerformancePercents
- MessageInsightPercents
- Try it!
List aggregate delivery data for the given Android application.
HTTP request
GET https://fcmdata.googleapis.com/v1beta1/{parent=projects/*/androidApps/*}/deliveryData
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. The application for which to list delivery data. Format: |
Query parameters
Parameters | |
---|---|
pageSize |
The maximum number of entries to return. The service may return fewer than this value. If unspecified, at most 1,000 entries will be returned. The maximum value is 10,000; values above 10,000 will be capped to 10,000. This default may change over time. |
pageToken |
A page token, received from a previous |
Request body
The request body must be empty.
Response body
If successful, the response body contains data with the following structure:
Response message for deliveryData.list.
JSON representation |
---|
{
"androidDeliveryData": [
{
object ( |
Fields | |
---|---|
androidDeliveryData[] |
The delivery data for the provided app. There will be one entry per combination of app, date, and analytics label. |
nextPageToken |
A token, which can be sent as |
Authorization Scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
AndroidDeliveryData
Message delivery data for a given date, app, and analytics label combination.
JSON representation |
---|
{ "appId": string, "date": { object ( |
Fields | |
---|---|
appId |
The app ID to which the messages were sent. |
date |
The date represented by this entry. |
analyticsLabel |
The analytics label associated with the messages sent. All messages sent without an analytics label will be grouped together in a single entry. |
data |
The data for the specified |
Date
Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following:
- A full date, with non-zero year, month, and day values.
- A month and day, with a zero year (for example, an anniversary).
- A year on its own, with a zero month and a zero day.
- A year and month, with a zero day (for example, a credit card expiration date).
Related types:
google.type.TimeOfDay
google.type.DateTime
google.protobuf.Timestamp
JSON representation |
---|
{ "year": integer, "month": integer, "day": integer } |
Fields | |
---|---|
year |
Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year. |
month |
Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day. |
day |
Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant. |
Data
Data detailing messaging delivery
JSON representation |
---|
{ "countMessagesAccepted": string, "messageOutcomePercents": { object ( |
Fields | |
---|---|
countMessagesAccepted |
Count of messages accepted by FCM intended to Android devices. The targeted device must have opted in to the collection of usage and diagnostic information. |
messageOutcomePercents |
Mutually exclusive breakdown of message delivery outcomes. |
deliveryPerformancePercents |
Additional information about delivery performance for messages that were successfully delivered. |
messageInsightPercents |
Additional general insights about message delivery. |
MessageOutcomePercents
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.
JSON representation |
---|
{ "delivered": number, "pending": number, "droppedTooManyPendingMessages": number, "droppedAppForceStopped": number, "droppedDeviceInactive": number } |
Fields | |
---|---|
delivered |
The percentage of all accepted messages that were successfully delivered to the device. |
pending |
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. |
droppedTooManyPendingMessages |
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. |
droppedAppForceStopped |
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 |
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. |
DeliveryPerformancePercents
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.
JSON representation |
---|
{ "deliveredNoDelay": number, "delayedDeviceOffline": number, "delayedDeviceDoze": number, "delayedMessageThrottled": number, "delayedUserStopped": number } |
Fields | |
---|---|
deliveredNoDelay |
The percentage of accepted messages that were delivered to the device without delay from the FCM system. |
delayedDeviceOffline |
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. |
delayedDeviceDoze |
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. |
delayedMessageThrottled |
The percentage of accepted messages that were delayed due to message throttling, such as collapsible message throttling or maximum message rate throttling. |
delayedUserStopped |
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. |
MessageInsightPercents
Additional information about message delivery. All percentages are calculated with countMessagesAccepted
as the denominator.
JSON representation |
---|
{ "priorityLowered": number } |
Fields | |
---|---|
priorityLowered |
The percentage of accepted messages that had their priority lowered from high to normal. See documentation for setting message priority. |