Docs

  • Channels Channels
  • Beams Beams
  • Developers
  • Support
  • Blog
  • Sign up
    • Search powered by Algolia
    • Sign in
    • Sign up
    • Channels
    • Beams
    • Getting started
      • Android
        • 1. Configure FCM
        • 2. Integrate SDK
        • 3. Initialize Beams
        • 4. Publish Notifications
      • iOS
        • 1. Configure APNS
        • 2. Integrate SDK
        • 3. Publish Notifications
      • Web
        • 1. SDK integration
        • 2. Safari configuration
      • Flutter
        • 1. Configure FCM and APNS
        • 2. Integrate SDK
        • 4. Publish Notifications
    • Concepts
      • Subscribers
      • Device interests
      • Authenticated users
      • Insights
      • Webhooks
    • Guides
      • Handle incoming notifications
        • Android
        • iOS
        • Web
        • Flutter
      • Publishing to multiple devices
      • Publish to specific user
        • Android
        • iOS
        • Web
        • Flutter
      • Web push guides
        • Using an existing service worker
        • Web notification permissions in Firefox
        • Handling Safari certificate expiration
    • Reference
      • Client SDKs
        • Android
        • iOS
        • Web
      • All Libraries
      • Server SDKs
        • Go
        • PHP
        • Node.js
        • Python
        • Java/Kotlin
        • Ruby
        • Swift
      • API
        • Publish API
        • Customer API
        • Device API
        • Reporting API
        • Webhooks
      • Platform Publish Formats
    • Pusher lab

    Configure FCM

    Pusher relies on Firebase Cloud Messaging (FCM) to deliver push notifications to Android application users on your behalf. When we deliver push notifications, we use your FCM credentials. This page guides you through the process of getting a FCM service account file and how to provide it to Pusher.

    Head over to the Pusher dashboard and create a new instance of Beams. After that, you can either follow the interactive quick start over there, or return here to follow the documentation steps.

    ∞ Open Firebase Console

    The first step is to go your Firebase console. Sign up if you haven‘t already.

    ∞ Create a new app

    If you are using a pre-existing Firebase app, you can jump ahead to Get Your Service Account JSON file. Otherwise you will create one now.

    Add a project if you haven’t already. Then create a new app, by clicking the Add app button.

    Screenshot of adding FCM app

    Click the Android icon.

    Screenshot of selecting Android

    Supply your app’s package name, then click the Register app button.

    Screenshot of firebase name

    ∞ Download the Firebase Configuration File

    Once the app is registered, you should click the button to download the google-services.json.

    Keep a note of the file‘s location, as eventually you will add it to your Android app‘s project on your computer.

    Screenshot of downloading config

    ∞ Get your FCM service account JSON file

    Go to your Firebase project‘s settings page, and then go to the Service Accounts tab.

    Then, you will need to generate a new private key by clicking Generate new private key.

    Screenshot of generating new private key

    This will download a service account JSON file.

    If you are following the quick start guide in the Pusher Beams dashboard, return to it now with your FCM service account file.

    This FCM service account file can be saved to your Pusher Beams instance in the dashboard.

    ∞ Where Next?

    Now that you have configured FCM you can
    integrate our Android SDK into your project.

    Contents

    • Open Firebase Console
    • Create a new app
    • Download the Firebase Configuration File
    • Get your FCM service account JSON file
    • Where Next?

    Spotted something that isn’t quite right? Create an issue on GitHub.

    Copyright © 2024 Pusher Ltd. All rights reserved.

    • Support,
    • Status
    • Follow Pusher on Twitter Twitter
    • Subscribe to Pusher’s channel on YouTube
    • Follow Pusher on LinkedIn
    • Follow Pusher on Github GitHub
    • Follow Pusher on Twitch Twitch
    • Follow Pusher on Discord Discord