Clear search
Close search
Google apps
Main menu

View Firebase Cloud Messaging statistics & issues

Firebase Cloud Messaging (FCM) helps you send messages across Android, iOS, and Chrome for free.

For example, a server can send messages directly to single devices, groups of devices, or devices subscribed to topics. The application on a device can also send messages directly to a server and to devices belonging to the same group.

Add Firebase Cloud Messaging

To add FCM to your app:

  1. Go to the Firebase console.
  2. Follow the instructions to add Firebase to your app.

View FCM statistics

To see FCM statistics on your Play Console, here's how to associate the FCM API key with your application:

  1. Sign in to your Play Console.
  2. Select an app.
  3. On the left menu, click Development tools > Services & APIs.
  4. Click the Link a sender ID button.
  5. Type your FCM API key.
  6. Click Link.

Once your app is published, you can view FCM statistics on your app's Statistics page.

  1. Sign in to your Play Console.
  2. Select an app.
  3. On the left menu, click Statistics.
  4. Next to "Statistics," click the drop-down and select FCM statistics.

FCM message status

  • Accepted: Arrived at FCM
  • Stored: Stored in FCM, pending redelivery, until the message is either expired or collapsed
  • Delivered: Sent to device
  • Acknowledged: Device has confirmed it received the message
  • Collapsed: Have a collapse key that has been replaced by other messages with the same collapse key
  • Expired: Reached their time-to-live (TTL) and expired
  • Invalid Request: Reached FCM and are invalid. FCM rejected them for any further processing. You can find details on these failures on our Firebase Cloud Messagingpage.
  • Sent after reconnect, with delay: Sent to the device after some delay upon reconnecting to the FCM servers
  • Sent on reconnect: Sent to device when device has reconnected to FCM
  • Accepted, sent to APNS: Arrived at FCM and sent to APNS for delivery to the iOS device
  • Failed by APNS: Arrived at FCM, but failed when forwarded to APNS for delivery to the iOS device

View FCM diagnostics

Using FCM Diagnostics, you can troubleshoot messages sent through FCM. You can look up the message(s) by registration token or message ID. 

FCM Diagnostics data for iOS apps will only be available through your Play Console if the iOS app has the same bundle ID as the corresponding Android app's package name.

To get to your FCM Diagnostics page:

  1. Sign in to your Play Console.
  2. Select an app that uses FCM.
  3. On the left menu, click Development tools > FCM diagnostics​.

You can look up messages sent through Firebase Cloud Messaging with a registration token or message ID.

Registration token

The registration token is the FCM identity of the client app on the device. You can find the device registration token when your client app registers with FCM. This is also the identity that you'll use to send an FCM message to a device.

You should only look up one registration token at a time.

Message ID
The unique FCM message identifier. You can find it in the response message that FCM sends to the client server when FCM confirms that it has received the message.
  • You can look up multiple message IDs at a time, but they should all be related to the same registration token.
  • To learn about the different message statuses, refer to the FCM message status section.

Collapsed messages overview

If a message is sent with the option collapse_key, and it hasn't been delivered to the device when another message with the same collapse_key arrives, the original message will have a "Collapsed" status.

The Collapsed messages overview shows sequence of messages with the same collapse key until the last message of the sequence has reached a non-collapsed status (Example: Delivered, Acknowledged, Stored, Expired)

You can find the collapse_key API references and examples on our Firebase Cloud Messaging page.

Changes to FCM data

June 12, 2016: XMPP messages added

We're now including XMPP messages on your FCM Statistics page. This means if you're sending XMPP messages, you'll see an increase in your FCM data.

XMPP messages will be categorized in the same way as HTTP messages and won't appear as a separate category in your reports.

Was this article helpful?
How can we improve it?