How to Configure a Firebase Cloud Messaging Key & Why You Should Use FCM API Key
Firebase Cloud Messaging (FCM) is the new version of GCM. It inherits the reliable and scalable GCM infrastructure, plus new features! Hence, we have updated the guide to show steps for getting FCM Key
Guide to Create Firebase Cloud Messaging Sender ID and Server API Key
We are a believer in Transparency, at PushEngage. We wrote an article about how to achieve full vendor portability with Web Push Notifications here. For Push Notification to work, it needs the GCM key.
In order for you to export your subscribers successfully and to use them through another API, you will need to configure PushEngage (or for that matter any provider) with your own Firebase Cloud Messaging Sender Id. We wrote about this in our FAQ as well. Google/Firebase Cloud Messaging is a service that enables developers to send push notification messages between the client browser and serve them.
Note: This is a critical setting, so please make sure you make this in an email account that you or your company owns.
Steps to Create a Firebase project and FCM sender ID
Guide updated:07-September-2017 [ We will try to keep this guide current]. Currently, we using Wapid Key.
- In the Firebase console, at https://console.firebase.google.com/ select Create New Project. Supply a project name and click Create Project.2. Select the gear icon next to your project name at top left, and select Project Settings.
3. Select the Cloud Messaging tab. You can find your sender ID in this page.
4. Copy these value in PushEngage Dashboard under Settings -> GCM/FCM Settings, and go live.
Here is the video to learn how to create and configure Firebase Cloud Messaging Sender ID and Server API Key:
If you are a HTTPS website, after updating the FCM key, you would need to download your manifest.json file again from Settings> Installation Settings > Step 2, and save it in the root folder.
For HTTP sites there is no extra step. However, do read our full portability guide for HTTP sites here.
That’s it you are done with the FCM configuration. This is a crucial setting to make sure to Verify the setting in PushEngage.
Using your own FCM key is very important when you want to migrate push notification subscribers from one push notification platform to other.
- How to Unsubscribe from Push Notifications in Chrome and Firefox
- How to Configure a Firebase Cloud Messaging Key & Why You Should Use FCM API Key
- Guide to Implementing Web Push Notifications, Without a Vendor Lock-in
- Drip Campaigns and Autoresponders For Web Push Notifications
- 7 Ways To Increase Your Web Push Subscription Rate In 2019
- How to Install PushEngage Browser Push Notification on Blogger Site?