Skip to main content
Stay connected with your customers by utilizing push notifications to alert them of new chat messages, release notes, and news articles. This will deepen engagement and foster stronger relationships. Gleap supports Firebase Cloud Messaging to send push notifications to users.

Setup Firebase Cloud Messaging

To make use of Gleap Push Notifications you must add the Firebase Cloud Messaging service to your app or website. Learn how to get started with FCM here.

Getting your Firebase Cloud Messaging Token

Open your project in Firebase and open the project settings. Click on “Cloud Messaging” and, if it is not already enabled, activate the Firebase Cloud Messaging API (V1). Gleap Firebase Setup Proceed to the “Service Accounts” section and generate a new private key, which will automatically create a file named like serviceAccountKey.json. Gleap Firebase Setup Next, open the project settings in Gleap, select “Push Notifications”, and upload the serviceAccountKey.json file. Finally, save your configuration. Gleap Push Notifications Setup

Subscribe to the Gleap user topic

The last step to complete the push notification setup is to subscribe to the user topic, which Gleap will send the push notifications to. In order to do so, you will need to register the register & unregister push message topic callbacks.
Register both listeners before calling Gleap.initialize(), so the initial topic registration isn’t missed.
Gleap manages the topic lifecycle for you: identify() / clearIdentity() automatically emit unregisterPushMessageGroup for the previous topic and registerPushMessageGroup for the new one — you don’t need to unsubscribe manually on sign-out.

Push notification payload

Every push notification sent by Gleap carries a data payload with the following keys: Outbound push campaigns send type and actionId instead of id. The notification itself contains the sender’s name in the title and a short plain-text preview (truncated to 70 characters) of the message as the body.

Handle push-notification taps

When the user taps a Gleap notification, check for sender === 'GLEAP' and open the referenced content. When the app is launched from a killed state, wait for Gleap’s initialized event before routing — otherwise the SDK may not be ready to open the conversation yet:
That’s it - build and run your app 🚀